Peter N. M. Hansteen wrote:
Girish Venkatachalam <[EMAIL PROTECTED]> writes:
You must be aware that google and other such popular mail services like
yahoo!, hotmail etc. blatantly flout RFC2821 and retry mails from a bank
of mail servers.
A large part of the problem is that while RFC2821 states that the
sender MUST retry, it does not actually say that the new delivery
attempts are required to come from the same IP address (at least as
far as I can remember).
Silly, but there it is. Some of us lazy sysadmins have ended up
whitelisting the IP addresses the domains in question state via SPF
records or similar are their valid outgoing SMTP servers. Fortunately
valid email senders that do not grok greylisting are getting rarer by
the minute.
BTW, anybody else interested in running something like the Name and
Shame Robot (<http://www.bsdly.net/~peter/nameandshame.html>)? Or for
that matter being a guinea pig for a spamd related experiment? Let me
know off-list if you're feeling adventurous.
What about using the sync built inside spamd with -y and -Y. I use that
in between a few servers, witch works well. I do not know how well, or
bad it might work for large scale setup?
Not sure what changed in the last two to three months, but there is more
spam coming in then before. Not by any mean as much as without spamd for
sure, but still, the level does increase.
I also run greylisting as well and Bob list too.
My servers are front end for customers that want no spam and I run an
ISP as well, so I gets lots of incoming obviously.
Any experience on a much bigger setup using the sync feature of spamd in
operation somewhere?
Obviously the real problem is the trust of the source use for sync in
the setup.
