On 24 Nov 2019, at 12:34, Matus UHLAR - fantomas wrote:

On 24/11/2019 15:57, Matus UHLAR - fantomas wrote:
I have explained that this was caused by receiving mail for "admin" thus spamass-milter provider username admin. Since the admin doesn't exist locally (apparently alias or remote user), spamd falled back to nobody.

On 24.11.19 16:05, Linkcheck wrote:
Then how can I get it to use the correct user each time? Obviously there can be a lot of them.

the recipient user is the correct on, his settings are used. That's why it
is called per-user settings. This feature is built into sa-milter.

However, looking at its docs, the '-u' user is only used when multiple
recipients, otherwise the recipient's username is used.

so, using this opion with spamass-milter is fine. using this with spamd
disables per-user configs which may not be what ou want.

The solution to confMILTER is: ignore it. That particular feature was designed for sendmail and postfix cannot support it.

according to sendmail docs, it's the queue ID. It's fine for logging.

Also: setting "smtpd_delay_open_until_valid_rcpt = no" should make it available. By default, postfix does not commit a file descriptor and queue ID to a message until it has an accepted recipient. Setting that option to "no" causes it to open the file and assign a queue ID at connect time, which also enhances the logging by postfix itsef, since every entry for a particular SMTP session has a common queue ID in it. There are minor performance & resource issues with that setting, so if you're handling more than a few score messages per second you may want to test if you can use that setting without causing trouble.

--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)

Reply via email to