This is a document copied from https://www.tornevalls.se/2019/08/12/the-postfix-maildir-guide/
...
Having a lot of domains and services to take care of may make only one file with all virtual users a bit junky. For my own current solution, this has been splitted up in parts and the postmap scripts are checking via cronjobs if the files has been changed. This is being made so files can be automatically transferred (if necessary) to the server, and so the server then can reproduce new data tables for the virtual users.
| Code Block | ||||
|---|---|---|---|---|
| ||||
virtual_alias_maps =
hash:/etc/postfix/virtual/virtual_users_tornevall.net
hash:/etc/postfix/virtual/virtual_users_tornevall.se
hash:/etc/postfix/virtual/virtual_users_fraudbl.org
hash:/etc/postfix/virtual/virtual_users_tornevall.org
hash:/etc/postfix/virtual/virtual_users_small_domains
hash:/etc/postfix/virtual/virtual_users
regexp:/etc/postfix/virtual/virtual_users_regex
|
...
Clients that does not support SMTP authentication via imap or pop
This text is written in october 2020 after ripping my hair of my head off for a while. What I did not think of, during the first round of installation, was that there will be non standard clients that won't do a pop/smtp-auth before entering the SMTP out. For example, Postfix, straight out of the box - where you want to relay from postfix to postfix via an authenticated user. With the solution above, there might happen things that you do not want. The error message below for example, is quite common but very much unanswered in different kinds of forums. Most of the posts are relating their problems to dovecot, cyrus and different kind of solutions that in the end seem to be database driven. This is not bad, it's just a little bit stupid since you suddenly rely your systems on yet another point of failure: The database. And the more crap you implement, the harder it will be to find the failing point.
| No Format |
|---|
warning: SASL authentication failure: unable to canonify user and get auxprops |
...