[Exim] strange problem with mail staying on queue longer tha…

Pàgina inicial
Delete this message
Reply to this message
Autor: Gary Palmer
Data:  
A: exim-users
Assumpte: [Exim] strange problem with mail staying on queue longer than retry time
I have some mails on my queues that are sticking around longer than
the retry time indicates they should. They are all getting frozen
because some remote admin has set their MX record to 127.0.0.1.

A sample message with -d9 -Mc 13H648-0000gT-00 shows (with some info
snipped for privacy concerns)

Exim version 3.15 debug level 9 uid=0 gid=1
Berkeley DB: Sleepycat Software: Berkeley DB 2.7.5: (04/18/99)
Actual local interface address is 127.0.0.1
Actual local interface address is 207.172.4.60
Actual local interface address is <snipped<
Caller is an admin user
Caller is a trusted user
set_process_info: 16830 3.15 delivering specified messages
delivering message 13H648-0000gT-00
set_process_info: 16830 3.15 delivering 13H648-0000gT-00
Opened spool file 13H648-0000gT-00-H
user=root uid=0 gid=1 sender=<snipped>
sender_fullhost = <snipped>
sender_rcvhost = <snipped>
sender_local=0 resent=no ident=unset
Non-recipients:
<snipped>
---- End of tree ----
recipients_count=3
body_linecount=61 message_linecount=17
LOG: 0 MAIN
Unfrozen by auto-thaw
running system filter as uid=0 gid=1 euid=0 egid=1
Filter: start of processing
Filter: end of processing
Delivery address list:
someone@???
locked /local/exim/smtp/spool/db/retry.lockfile
opened DB file /local/exim/smtp/spool/db/retry: flags=0
>>>>>>>>>>>>>>>>>>>>>>>>

Considering: someone@???
medianone.net in local_domains? no (end of list)
unique = someone@???
dbfn_read: key=R:medianone.net
dbfn_read: key=R:someone@???
someone@???: queued for routing
>>>>>>>>>>>>>>>>>>>>>>>>

After directing:
  Local addresses:
  Remote addresses:
  Failed addresses:
  Addresses to be routed:
    someone@???
  Deferred addresses:

>>>>>>>>>>>>>>>>>>>>>>>>

routing someone@???, domain medianone.net
selecteddomains router called for someone@???
route_domain = medianone.net
after handling route_lists items, matched = 0
selecteddomains router: cdb key=medianone.net
file="/shared/exim/mailroutes.smtp.cdb"
search_open: cdb "/shared/exim/mailroutes.smtp.cdb"
search_find: file="/shared/exim/mailroutes.smtp.cdb"
key="medianone.net" partial=2
LRU list:
0/shared/exim/mailroutes.smtp.cdb
End
internal_search_find: file="/shared/exim/mailroutes.smtp.cdb"
type=cdb key="medianone.net"
file lookup required for medianone.net
in /shared/exim/mailroutes.smtp.cdb
lookup failed
trying partial match *.medianone.net
internal_search_find: file="/shared/exim/mailroutes.smtp.cdb"
type=cdb key="*.medianone.net"
file lookup required for *.medianone.net
in /shared/exim/mailroutes.smtp.cdb
lookup failed
search_find failed:
selecteddomains router declined
cn_backdoor router called for someone@???
route_domain = medianone.net
routelist_item = <snipped>
after handling route_lists items, matched = 0
cn_backdoor router declined
lookuphost router called for someone@???
dns lookup: route_domain = medianone.net
DNS lookup of medianone.net (MX) succeeded
Actual local interface address is 127.0.0.1
Actual local interface address is 207.172.4.60
Actual local interface address is 10.255.4.60
local host has lowest MX
fully qualified name = medianone.net
host_find_bydns yield = HOST_FOUND_LOCAL (3); returned hosts:
smtp.medianone.net 127.0.0.1 10 1049
LOG: 0 MAIN
lowest numbered MX record points to local host: medianone.net
lookuphost router: error for medianone.net
message: lowest numbered MX record points to local host
post-process someone@???
LOG: 0 MAIN
== someone@??? R=lookuphost defer (-1): lowest numbered MX record points to local host
search_tidyup called
set_process_info: 16830 3.15 tidying up after delivering 13H648-0000gT-00
Processing retry items
Succeeded addresses:
Failed addresses:
Deferred addresses:
someone@???: no retry items
end of retry processing
time on queue = 2w6h52m29s
warning counts: required 4 done 4

It then goes on to send out a warning message to postmaster, etc.

My question is how can I prevent these mails from sticking around
longer than 5 days? I want them to bounce back to the user like
normal after 5 days and no delivery. This is a new behaviour with
3.15, the old 2.12 version didn't do this.

Any ideas? Thanks,

Gary