Hi, wondering if this is happening to anyone.  Last couple of weeks I been having users complaining about Yahoo emails not getting through.  I have narrowed it down to SFDC, if I disable it(0) Yahoo emails will get through just fine.  But once enabled(5), it will allow some but will block most emails from Yahoo.  I am running registered version 4.2.4.844, and prior version 4.2.4834.  Let me know, thanks.

Roberto, it's actually any emails from Yahoo.  A simple plain text test message would be blocked.  I am away from the office for the next couple of days, I will get them to you when I get back.  BTW, is there a way to reset SFDC on the spamfilter?  Thanks for the reply.

Roberto, let me corret myself.  Not all messages from Yahoo are getting blocked.  All Yahoo messages are taking a long time to receive tho, it takes about an hour before it's delivered.  Gmail, after the greylisting period will deliver instantly.  I did forwarded you a email with subject(RE: Failure Notice) for you to exam.  Thank you.

I am having a similar problem the larger ISPs and have started a new topic about greylistin (which I think could be the problem)

Hi Roberto

Yesterday I did a test and sent a email over Yahoo. Today I got this "unable to deliver" report back from them.

This also after we implemented all the whitelisted Yahoo IP's you suggested. How do you create this Yahoo IP list?

Is there a way to find out which IP Yahoo used to deliver this email? Is this "mailer-deamon" comming always from the same mailserver from which they tried to deliver the Email? So in this header it was the 77.238.189.231 and the 212.82.108.238 or the 192.168.2.100 server?

Thx

Wayne

--------------------------------------------------------

Von: "MAILER-DAEMON@yahoo.com" <MAILER-DAEMON@yahoo.com>
An: myYahooAdr@ymail.com
Gesendet: 0:45 Dienstag, 18.Oktober 2011
Betreff: Failure Notice

Sorry, we were unable to deliver your message to the following address.

<myCompanyAdr@mydomain.ch>:
Message expired for domain mydomain.ch

--- Below this line is a copy of the message.

Received: from [77.238.189.231] by nm21.bullet.mail.ird.yahoo.com with NNFMP; 16 Oct 2011 22:45:02 -0000
Received: from [212.82.108.238] by tm12.bullet.mail.ird.yahoo.com with NNFMP; 16 Oct 2011 22:45:02 -0000
Received: from [127.0.0.1] by omp1003.mail.ird.yahoo.com with NNFMP; 16 Oct 2011 22:45:02 -0000
X-Yahoo-Newman-Id: 750173.3769.bm@omp1003.mail.ird.yahoo.com
Received: (qmail 5364 invoked from network); 16 Oct 2011 22:45:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1318805102; bh=MItZ2JRTSpzQQhgoqf0Y4OROfVUofqA7FKqQsAbwLtQ=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Subject:From:Content-Type:X-Mailer:Message-Id:Date:To:Content-Transfer-Encoding:Mime-Version; b=SMak9NiKxm22Gntxun+m1z0w3eX/eeHbz79XL1mVQQDaQSSRldrdXn0ImJjrZrmEJXEbNAZtRLa8rHNP4ChHCVe5QYM/uTyIKJ+KLevZqOGU3YF4DV+2+MLsowPQ3rLjKUk0ZGz6i+PaLSHRh8G9ZFJfpMtxFbeL/6VvK4NMfP8=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: WWQ8t1oVM1lTvvGr5Bo6pdycj39n.ECEd1M4i_IBg09fwvo
gruSPG1vyc730gvtb_ddSugeGnncKPXeApq8zns.xVy5LKBUZ3gBjwJF4FlJ
tivoyQ.rE0W3fTnV6b6pwCxmAjtpIIr73L7emsgM8kRZ4LnjprnNewv9zMVz
NZ_rWor5Yl54M76PwWDF6yUPdUY48H29pCoVfKpLNjUM7EQ7BK1kMKBRLh3r
e2sbSbHgygCnW9T4pDPW8eY3IvwsupIP4xWzOrUr.kvB49wNIcgCuyeO87S7
TeUrK85qsjliCIb.5CkBb42S0W2dtmGQdysgG6ELJ9FGC6U0KVJ51heS2sh_
F6h_DxwxyGArOl93YqXbLZyH.mZFIhg--
X-Yahoo-SMTP: 34zSj3CswBC2PerM55x7s63vQlq8A59ctQLvCxgOL.Zm
Received: from [192.168.2.100] (myYahooAdr@178.82.191.237 with xymcookie)
        by smtp101-mob.biz.mail.ird.yahoo.com with SMTP; 16 Oct 2011 22:45:02 +0000 GMT
Subject: Belkin Aircast
From: Wayne <myYahooAdr@ymail.com>
Content-Type: multipart/alternative;
    boundary=Apple-Mail-1--951999251
X-Mailer: iPhone Mail (8G4)
Message-Id: <179E4653-1A91-4252-B624-15637B6AAAF6@ymail.com>
Date: Mon, 17 Oct 2011 00:44:59 +0200
To: Wayne <myCompanyAdr@mydomain.ch>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (iPhone Mail 8G4)


--Apple-Mail-1--951999251
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
    charset=us-ascii

Belkin Aircast

--Apple-Mail-1--951999251
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
    charset=utf-8

<html><body bgcolor="#FFFFFF"><span class="Apple-style-span" style="font-family: verdana, geneva, lucida, 'lucida grande', arial, helvetica, sans-serif; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); font-size: 22px; ">Belkin Aircast</span><div></div></body></html>
--Apple-Mail-1--951999251--


Edited by Wayne - 18 October 2011 at 3:23am

Roberto

Yes I checked the IP and the log already, there is not one connection from this IP.
I'm also in the Yahoo Postmaster group where they publish periodically the current outgoing mail server address list and any planned changes in the list for whitelisting, but yeah, as in the current example, often it's not actual enough.

Hmmm, just another idea to improve our beloved Spamfilter application. Don't be offended please ;)

If some big providers use a pool of mail servers with a shared mail queue, can't you teach then SF to check the PTR and trim this resolved name instead to use just the IP of the SMTP?

As example with the Yahoo sender site like:

nm21.bullet.mail.ird.yahoo.com
nm18.bullet.mail.ird.yahoo.com
out5.bullet.mail.ird.yahoo.com
out35.bullet.mail.ird.yahoo.com

Using the original grey-list key set, the first time the sending site connects, SF will record:

212.82.108.136, fromaddress@yahoo.com, myaddress@mydomain.ch

Second try they use another server from their pool:

212.82.195.250, fromaddress@yahoo.com, myaddress@mydomain.ch

And so on, so that's why they never came through, agree so far?

If you would be able to check the PTR and trim the first word and whitelisting this trimmed PTR information, in this example:

bullet.mail.ird.yahoo.com, fromaddress@yahoo.com, myaddress@mydomain.ch

Wouldn't we have eliminated then all this problems?




Edited by Wayne - 19 October 2011 at 6:08am

Roberto

I checked the 15th/16th and 17th  But I sent you the logs now as well, looks like you don't trust me 

Oh and btw, I blamed Yahoo now many times coz I thought they are really violating the RFC 2821 and how you also wrote in your thread here.

The greylist filter is a great tool that can be used to fight spam, as long as SMTP server follow the RFC guidelines. Per RFC, if an SMTP server is unable to deliver an email because the receiving SMTP server rejects the connection attempt with a 4xx error code (which indicates a temporary unavailability), they are supposed to retry the delivery after a few minutes.

I spent yesterday a lot of time to read through all the SMTP relevant RFC documents to find where such providers are violating the RFC, but honestly, nowhere I could find something where is written, that it has to be the same SMTP server who retries to send the mail again after a 4xx.

Anyway, I consider the greylisting is an abuse of SMTP standards. The server isn't really busy at all so sending a 4xx status code isn't the way the protocol was really designed.

But yeah, that's a matter of opinion

Thx for your help


Edited by Wayne - 20 October 2011 at 8:20am

Hi Wayne,

Unfortunately I think the IP was the right one. Your logs show:

Based on what Wayne had originally reported above, yes, it's very possible. Just as I asked Wayne, could you please zip and email us (support at logsat dot com) your SpamFilter.ini and your GreyListAllowed.txt files so we can have a look?

Zippped up the files and sent them this morning. Thanks

The problem can occur intermittently when the GreyListAllowed.txt file contains an entry with a wildcard, followed by one or more entries that contain an IP within the above subnet. For example with this sequence:

Any news on this update, I started using the list provided so I will be impacted by this bug and am awaiting the fix.  I don't see the update in the download area.

Installed and testing now 

Thx for the fast fix, hope our YM problems are gone now.