Please Help, EXIM 550 550-Verification failed

P

pathosting

New member
Joined
Feb 1, 2011
Messages
4
My server can't receive e-mail from ALL sources.

It will reject with this message.
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550-Verification failed for <[email protected]>
550-Unrouteable address
550 Sender verify failed (state 14).
Click to expand...

Now I skip "require verify = sender" in /etc/exim.conf for temporary. :(

I test some exim command with sender address, It look fine and this is a result.
[root@example custombuild]# exim -v -bv [email protected]
[email protected]
router = lookuphost, transport = remote_smtp
host gmail-smtp-in.l.google.com [74.125.53.27] MX=5
host gmail-smtp-in.l.google.com [74.125.155.27] MX=5
host gmail-smtp-in.l.google.com [74.125.127.27] MX=5
host alt1.gmail-smtp-in.l.google.com [74.125.95.27] MX=10
host alt1.gmail-smtp-in.l.google.com [209.85.225.27] MX=10
host alt1.gmail-smtp-in.l.google.com [74.125.65.27] MX=10
host alt2.gmail-smtp-in.l.google.com [74.125.47.27] MX=20
host alt2.gmail-smtp-in.l.google.com [74.125.157.27] MX=20
host alt2.gmail-smtp-in.l.google.com [74.125.45.27] MX=20
host alt2.gmail-smtp-in.l.google.com [74.125.159.27] MX=20
host alt3.gmail-smtp-in.l.google.com [74.125.93.27] MX=30
host alt3.gmail-smtp-in.l.google.com [74.125.115.27] MX=30
host alt3.gmail-smtp-in.l.google.com [74.125.91.27] MX=30
host alt4.gmail-smtp-in.l.google.com [209.85.143.27] MX=40
host alt4.gmail-smtp-in.l.google.com [74.125.77.27] MX=40
host alt4.gmail-smtp-in.l.google.com [209.85.227.27] MX=40
Click to expand...

and this,

[root@example custombuild]# exim -bvs [email protected]
[email protected] verified
Click to expand...

These are my installed software's versions.
Installed version of DirectAdmin: 1.37.0
Installed version of Apache: 2.2.17
Installed version of autoconf: 2.67
Installed version of automake: 1.11.1
Installed version of PCRE: 8.10
Installed version of curl: 7.21.3
Installed version of FreeType: 2.4.4
Installed version of dovecot: 2.0.9
Installed version of PHP (CLI): 5.2.17
Click to expand...

Please advice me, :)
 
More information...

My exim detail
Exim version 4.74 #1 built 25-Feb-2011 21:42:00
Copyright (c) University of Cambridge, 1995 - 2007
Berkeley DB: Sleepycat Software: Berkeley DB 4.3.29: (July 12, 2010)
Support for: crypteq IPv6 Perl OpenSSL move_frozen_messages Content_Scanning DKIM Old_Demime
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Size of off_t: 8
OpenSSL compile-time version: OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
OpenSSL runtime version: OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
Configuration file is /etc/exim.conf
Click to expand...
 
having the same problem with exim spam blocker v4 and latest exim.pl provided but directadmin staff.

Still didnt understand what the problem come from.

Never had this error since i use exim spam blocker v4, started today that ive updated exim.pl for the per-user email limitation.

Interested on solution aswell.

Regards
 
me too...

SeLLeRoNe said:
having the same problem with exim spam blocker v4 and latest exim.pl provided but directadmin staff.

Still didnt understand what the problem come from.

Never had this error since i use exim spam blocker v4, started today that ive updated exim.pl for the per-user email limitation.

Interested on solution aswell.

Regards
Click to expand...

I found the problem after update exim.pl too.:eek:
 
Can you resolve the problem by temporarily going to back to the exim.pl file on my site (nobaloney.net)?

Jeff
 
tryed and work perfectly with old exim.pl from your website.

Seems that last version that implement limite-per-user (that is not working at all) have other things that may have conflict with the option verify = sender
 
Hello,

Might this be related?
http://help.directadmin.com/item.php?id=67

#3.

If the limit set in the /etc/virtual/limit or /etc/virtual/limit_user has been hit (/etc/virtual/usage/user), then the way exim blocks the sends is by making the lookup fail... thus the emails never leave.

Going back in time with the exim.pl would then default to the /etc/virtual/limit, which is likely a different number.

Using the new exim.p, try deleting the /etc/virtual/usage/username file to see if the problem goes away. Note that it's normal to get the Unrouteable error once the limit is hit, this is out the block works.

John
 
More to that, the sender_verify is likely doing a fake email test... thus the lookuphost router may be failing too.

Check:
/var/log/exim/mainlog and paniclog to see what username is showing up in:
Code: 
You ([b]$name[/b]) have reached your daily email limit of $email_limit emails
If it's the same as the User.. then that would then make sense, since the User isn't allowed to send email, and the verify_sender is "fake" sending an email. Desired.. not so much.. we'd would have to sort out what variables would tell us it's a sender verify, as opposed to a real email send (I'm not sure of that at this moment)

If the user is always "unknown", that might make it easier, although, we'd have to add "unknown" to the list of dis-allowed DA usernames so that people don't bypass it with that username.


Note, our default exim.conf does not have the
Code: 
require verify = sender
enabled by default, while the spamblocker v4 does, which would likely be why it's showing up for these cases. I would say that the verify should still work when the limit is hit, to allow the receiving of email, even at the limit.. but again, we'd need to know what exactly what we can check in the perl check_limits script that will tell us it's a sender verify, and not a client send (I'll poke at this, but if someone already knows, do tell).

John
 
Downloaded again directadmin's latest exim.pl file and enabled verify = sender

For now seem is working the verify sender (no change was made on server) so i cant explain why now is working...

Regarding the limit per user i will reply as soon as ive news.

Regards
 
Something new in paniclog from restart of exim with latest exim.pl

Code: 
2011-03-01 09:25:50 failed to expand condition "${perl{check_limits}}" for lookuphost router: Undefined subroutine &main::check_limits called.

2011-03-01 09:25:52 failed to expand condition "${perl{save_virtual_user}}" for virtual_user router: Undefined subroutine &main::save_virtual_user called.

May this be useful?
 
should be a reverse dns problem from who send the origin of sender verify fail?

I mean, looking at this line:

Code: 
2011-03-01 09:03:52 H=89-97-218-94.ip19.fastwebnet.it (vitesse.crazynetwork.it) [89.97.218.94] F=<[email protected]> rejected RCPT <[email protected]>: Sender verify failed

This is another of my server but the rDNS is not proper setup so ping vitesse.crazynetwork.it give 89.97.218.94 and tracert 89.97.218.94 resolve in 89-97-218-94.ip19.fastwebnet.i

This is a valid reason for sender verify fail?

Regards
 
I hope not. But you might want to Google or ask on the exim-users list.

Jeff
 
You must log in or register to reply here.
Back
Top