On Sat, Apr 11, 2015 at 12:12:05PM +0200, Peter N. M. Hansteen wrote: > Joerg Jung <m...@umaxx.net> writes: > > > I also know about spamd, but that is not really an option for now as the > > server speaks v6 and STARTTLS, moreover I have legacy users which AUTH > > on port 25 as well. This does not play well with spamd. > > spamd doesn't even attempt smtp auth, but then once the sender is > whitelisted (as a valid sender should be), the problem would go away.
>From my understanding, the user connects on port 25 (using STARTTLS and SMTP AUTH), is blocked by spamd (451 temporarily greylisted for 25 min), but usually MUAs try again some seconds later... so I do not see how these senders become valid and whitelisted? Besides, spamd does not (yet) support IPv6 or STARTTLS. > Your regular and valid correspondents would not see spamd at all -- > after all spamd is supposed to simply slow down the obvious spambots. > > In your scenario (as in most others) it's likely useful to explore the > nospamd option, as in maintain a table of IP addresses or ranges that > are simply never redirected to spamd. It's even in the spamd man page > (first pf.conf ruleset example). With legacy users using SMTP AUTH I meant users from (global) dialup connections with (often) changing IP(v6) client addresses. I see no chance how I could whitelist them. Regards, Joerg -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
