On 29/05/17 11:33 AM, Wols Lists wrote:
I have several mail aliases, controlled by mysql. So (for Patrick)) fetchmail was configured to pull mail from the internet and fire it at postfix to deliver. With mysql broken, postfix can't resolve user-ids and deliver the mail.
Postfix doesn't *NEED* MySQL to do this. it can do it entirely with regular files. Having MySQL makes sense for service providers or large organizations where there are thousands or email accounts, perhaps served from a a single domain.[1] I don't think it makes sense for one person, one family, the "personal" rather than the Big Business context. Back when, I had this set-up with not just the many accounts I did have, but the permutations of my name and initials, expansions, with and without periods, with had without under-bar rather than period. I also had the lists that I subscribe to. I used fetchmail, procmail and Spamassassin as front-end and Postfix to deal with IDs. I had perhaps 160 IDs and perhaps another 20 or so list IDs. For the most part Postfix "filed". It was more flexible as a filing agent than Procmail :-) All of this was done with fixed files that were created and maintained with VI. Was it fast enough> For my (then) three domains and the less than 200IDs it had to deal with, rotating rust, cable speeds (topped out around 600 kilobytes/sec), yes it was fast enough. The limiting feature was never my machines, it was always the remote machines, be it for POP, IMAP fetches or for delivery with SMTP. I'm sure that speed differential is that my end is just me. It's not as if my machine, my file server, my mail server (then) ran a heavy load. Heck the way it was, was a old ClosetofAnzieties 800Mhz machine 1G Ram, 350G IDE drive, an MS XP generation machine that had to be junked 'cost it couldn't run whatever came next; but it could still run opsenSUSE 12.whatever. (But can't run Leap :-( ) No, you can run postfix quite well without a SQL database if your needs are modest, single user or just family sized. [1] Think, for example. of the @IBM.com or @HP.com addresses. The DNS/MX may give various servers, but the service has to be idempotent, that is it results in the same routing regardless of the mail host. And for the thousands, perhaps millions of employees. Yes, James.knott@IBM.com may be resolved to, re-routed to james.knott@toronto.ibm.com, but the only way to make sure that happens regardless of the server is to have the same 'database' on all of them. And this needs to be uncoupled from any /etc/passwrd file. A SQL database offers the replication/mirroring and the fast lookup. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org