On Sat, Aug 30, 2008 at 04:56:03PM +0530, Girish Venkatachalam wrote: | On 16:44:19 Aug 30, Girish Venkatachalam wrote: | > > I couldn't find this mentioned in RFC2821, could you point out the | > > section number which talks about this? | > > | > > In any event, it's definitely not all that unusual... | > > | > | > Obviously then I must be wrong. | > | > Mail servers are supposed to retry from the same IP address as per the | > RFCs. That is what I know/think. | > | > Let me head to ietf.org and get back. :) | > | | Stuart, | | I got this from RFC2821. | | +----------------------------------------------------------------------+
<SNIP part of RFC 2821 section 3.7> | +----------------------------------------------------------------------+ | | Does the last sentence of the first paragraph above suggest this? The section you quoted refers to receiving, not sending mail (more specifically, to source routing e-mail). | And I find several places in the RFC where this idea is strongly | suggested. Can you point these out ? I've read the RFC and couldn't find any such "strong suggestions" you speak of. | Going by common sense however only those who don't comply with SMTP | standards would do such a silly thing. Why is it a silly thing ? Why would only those who don't comply with SMTP standards do it ? It's not in violation of 2821 (not that I could find nor you have provided evidence for, at least). | It is still possible to use a bank of MTAs but allocate the job of | retrials to come from the same IP address. But this is not how the gmails of this internet currently work. At this point in time, that means either whitelisting those senders you deem a) trustworthy enough to not send you spam and b) important enough to whitelist in the first place. Otherwise you risk missing some mail because they're not retried from the same IP. I have a `getwhite` script that updates my personal whitelist on a daily basis. Since I consider GMail important enough to receive (that is, some people send me e-mail I consider important from gmail) and I think this party is trustworthy enough to not spam me, I have whitelisted the Google SPF records in my script. I use the following snippet (for those curious about my script, it's available at http://www.weirdnet.nl/openbsd/cronjobs/getwhite) : host -t TXT _netblocks.google.com | tr ' ' \\n | grep ^ip4 | \ cut -f2 -d':' >> $WHITELIST.new I don't believe there is a clean solution to this at the moment. I love spamd, as it prevents *A LOT* of spam from reaching my MX in the first place but it can be detrimental in certain cases such as these. The easy way is blame the sender and ignore the rest of the problem. Unfortunately, that doens't always work all that well, so finding a workaround is sometimes necessary. Cheers, Paul 'WEiRD' de Weerd -- >++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+ +++++++++++>-]<.>++[<------------>-]<+.--------------.[-] http://www.weirdnet.nl/

