Current time: 11-27-2024, 09:00 AM Hello There, Guest! (LoginRegister)


Thread Closed 
incoming email blocked.
Author Message
kilburn Offline
Development Team
*****
Dev Team

Posts: 2,182
Joined: Feb 2007
Reputation: 34
Post: #2
RE: incoming email blocked.
Code:
Mar 28 19:24:26 sosaria postfix/policyd-weight[2769]: weighted check: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_NE_HELO=1.5 RESOLVED_IP_IS_NOT_HELO=1.5 (check from: .eurocasa. - helo: .ecsrv8.pyreurocasa. - helo-domain: .pyreurocasa.) FROM_NOT_FAILED_HELO(DOMAIN)=3; <client=88.2.127.72> <helo=ecsrv8.pyreurocasa.local> <from=exposanjuan@problemcustomer.com>

To see the actual error, we have to check the actual name of the client's IP:
Code:
72.127.2.88.in-addr.arpa domain name pointer 72.Red-88-2-127.staticIP.rima-tde.net.

So, the problem is threefold:

1) CL_IP_NE_HELO: The client identifies itself as "ecsrv8.pyreurocasa.local", but his IP resolves to another hostname "72.Red-88-2-127.staticIP.rima-tde.net"

2) RESOLVED_IP_IS_NOT_HELO: "csrv8.pyreurocasa.local" obviously doesn't resolve to the client's IP (because it's a .local domain)

3) FROM_NOT_FAILED_HELO(DOMAIN): On top of that, the domain part of the FROM field of the e-mail (problemcustomer.com) does not match the domain given in the helo command (pyreurocasa.local).

Now, the solution is pretty simple: tell your customer to setup his e-mail server so that it identifies himself (HELO) as "72.Red-88-2-127.staticIP.rima-tde.net", and he will get through without any problems.

Make sure to explain to him that this is *good* because he will have less chances of being flagged as spammer by other mail servers too.
04-01-2011 05:59 PM
Visit this user's website Find all posts by this user
Thread Closed 


Messages In This Thread
incoming email blocked. - robbo007 - 03-30-2011, 05:22 PM
RE: incoming email blocked. - kilburn - 04-01-2011 05:59 PM
RE: incoming email blocked. - robbo007 - 04-02-2011, 07:52 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)