Jake Di Toro wrote: > Oliver Fromme wrote: > > > Just a small question: Is there a way to disable the > > auto-whitelisting for certain IP addresses? I.e. I want > > mails from IP 12.34.56.78 (example) to always be delayed > > (i.e. greylisted), no matter if the ip/sender/recipient > > triple is known or not. In other words, that IP address > > should never appear in the auto-whitelist. > > It seems to me you might be missing something in what your asking. If > it doesn't auto-whitelist you won't recive your mail afterwords. > Perhaps what you relaly want is a 1 time whitelist. Where after your > delay the address is whitelisted, then once a message is recived from > that tupple the entry is removed. I see. You're right. I forgot the fact that milter- greylist is not able to identify mails, and that different mails with the same tuple could arrive in and interleaved fashion (without milter-greylist noticing). > I could see this scenario happining: > > 0 Message A recives the tempfail for 5 minutes, sending server queues > +6min Message B from same tupple is seen and sccepted What header would be added to message B? If this one: X-Greylist: Delayed for 00:06:00 by milter-greylist-... then it would be lying (or at least very confusing), because the text implies that _this_ email was delayed for 6 minutes, but it really wasn't delayed at all. Afterwards, if message A is resent and not delayed (because it's auto-whitelisted), it would get this header: X-Greylist: ... auto-whitelisted, not delayed ... but this email really _was_ delayed (for at least 6 minutes). I think that's a bug that needs to be fixed. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way.
Message
Re: [milter-greylist] Re: Disable auto-whitelisting for certain IPs?
2006-07-17 by Oliver Fromme
Attachments
- No local attachments were found for this message.