The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

retry timeout exceeded

Discussion in 'E-mail Discussions' started by heavypredator, Nov 27, 2007.

  1. heavypredator

    heavypredator Well-Known Member

    Joined:
    May 2, 2003
    Messages:
    93
    Likes Received:
    1
    Trophy Points:
    8
    My exim is not following standard retry rules - it is often failing email when remote host uses graylisting.

    07-11-26 06:27:11 1IwWUw-00041S-VP <= myuser@myhostname.com U=myuser P=local S=1055 id=c64c44c5a4b67fe708f9106d9a4c859b@mydomain.pl T="Wszystkiego najlepszego z okazji twoich 16 urodzin!!!"
    2007-11-26 06:27:11 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1IwWUw-00041S-VP
    2007-11-26 06:27:11 1IwWUw-00041S-VP == +++++@op.pl R=lookuphost T=remote_smtp defer (-44): SMTP error from remote mail server after RCPT TO:<+++++@op.pl>: host mx.poczta.onet.pl [213.180.130.86]: 450 4.7.1 W chwili obecnej nie mozesz wyslac listu do: <+++++@op.pl>, sprobuj za chwile [0400.-1] / At the moment you cannot sen a message to <+++++@op.pl>, try again later [0400.-1]
    2007-11-26 06:27:11 1IwWUw-00041S-VP ** +++++@op.pl: retry timeout exceeded


    As you see exim gets 450 and is immidietially failing email instead of trying later.

    Im running exim 4.68 with assp.
     
  2. Amit Deshmukh

    Amit Deshmukh Well-Known Member

    Joined:
    Jul 1, 2007
    Messages:
    83
    Likes Received:
    0
    Trophy Points:
    6
    Exim

    You need check following rules :-

    One common problem people have is an incorrectly setup mail system. Here is a list of rules that must be followed:

    1) hostname must not match any domain that is being used on the system. Example, if you have a domain called domain.com and you want to recieve mail on user@domain.com, you must *not* set your hostname to domain.com. We recommend using server.domain.com instead. You must make sure that you add the A record for server.domain.com so that it resolves.

    2) The hostname must be in the /etc/virtual/domains file.

    3) The hostname must *not* be in the /etc/virtual/domainowners file.

    4) The hostname must resolve. If not, add the required A records to the dns zone such that it does.

    5) The directory /etc/virtual/hostname must exist.. (eg: /etc/virtual/server.domain.com). It must not contain any files.

    6) Any domains that you want to use for email (eg: domain.com) must be in both the /etc/virtual/domains file and the /etc/virtual/domainowners file. The directory /etc/virtual/domain.com must exist and the files /etc/virtual/domain.com/passwd and /etc/virtual/domain.com/aliases exist.

    7) File permissions for virtual pop inboxes should be:

    /var/spool/virtual/domain.com 770 username:mail
    /var/spool/virtual/domain.com/* 660 username:mail

    If you've made any changes to you /etc/exim.conf file and require a fresh copy, you can retrieve one with this guide:
    http://help.directadmin.com/item.php?id=51

    8) Ensure your hostname does not contain any upper case letters.

    9) Make sure that your main server IP has a reverse lookup on it.


    =====================
    I am not sure what exactly causing the problem. So go ahead and recheck the rules.

    Regards,
    Amit
     
  3. heavypredator

    heavypredator Well-Known Member

    Joined:
    May 2, 2003
    Messages:
    93
    Likes Received:
    1
    Trophy Points:
    8
    I found out that there may be something wrong with hints database
    running:
    # exinext address@domain.com

    Route: address@domain.com:<from@domain.com> error -44: SMTP error from remote mail server after RCPT TO:<address@domain.com>: host mx5.go2.pl [193.17.41.45]: 450 Please try later
    first failed: 20-Nov-2007 12:53:20
    last tried: 29-Nov-2007 15:55:55
    next try at: 29-Nov-2007 23:55:55
    past final cutoff time

    As you can see it sees NEW email as first failed 9 days before - probably same email but database was not cleaned after the message was delivered or finally failed before.

    Im now looking into exim_tidydb and i notified cp support about this problem.
     
Loading...

Share This Page