Andrew Hodgson a écrit le 18/04/2020 à 12:51 :
Gilles Filippini wrote:
Andrew Hodgson a écrit le 18/04/2020 à 12:26 :
[...]
In my situation I noticed the directories weren't created very quickly as my Exim config looks for the list directories to identify whether that address exists. I don't know how Postfix does the aliasing but for my case it would make sense to get the directories created as soon as possible, not sure if the digest handler would be soon enough or not.
There is no need for these directories on the Exim side actually. You can safely drop the related checks from the Exim configuration [1].
Interesting, if you drop these checks does the mail get rejected at SMTP time or does Exim need to generate a bounce after it tries to deliver the message via LMTP?
As I understand it from the logs, Exim forwards the LMTP bounce to the sender.
What happens if the Mailman LMTP is unavailable at the point when the message comes in? In the current environment it gets queued, but that happens because Exim knows the list exists.
No, Exim doesn't know the list exists. It just knows that it is allowed to go through the mailman transport. Then I guess this is the same behavior when the checks are disabled, except that in this case junk email is queued as well, provided it targets one of your lists domain.
Reducing backscatter is quite a high priority for me as I get a lot of email to junk aliases at the lists domain which currently get rejected at the envelope stage.
Then this setting might no be what you want. I set it up because my services are dockerized and I'd prefer not to mount the mailman-core volume into the Exim container.
_g.