"Urban Hillebrand" writes:
> (3) I found several hints in the archives that some people believed to
Some variants of broken smtp configurations will choke on greylisting,
and spamd doesn't really have much in the way of smtp smarts beyond
what it needs in order to waste spammers' time. If somebody important
is unable to deal with greyliting, you will probably need to whitelist
them. And yes, those toy relay checkers that do not check if the
message gets delivered do tend to think spamd is an open relay. That
and some spammers' tricks will swell your greylist a bit from time to
time, but I don't really see that as much of a problem in real life.
- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
| Greg Kroah-Hartman | [PATCH 008/196] Chinese: add translation of volatile-considered-harmful.txt |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Herbert Xu | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Rémi Denis-Courmont | [PATCH 01/14] Phonet global definitions |
