On Friday 07 September 2007 16:10:23 Rick Macdougall wrote:
> Actually, if the primary MX does not respond, qmail will try the higher
> MX.  If the primary MX responds but temp fails the message, qmail will
> try the same MX again later.

I have some installations where qmail does not contact the next MX server for 
delivery.

This is a (real) example:

$ nslookup -query=mx praxi.com
Server:         192.168.103.100
Address:        192.168.103.100#53

Non-authoritative answer:
praxi.com       mail exchanger = 20 smtp.praxi.com.
praxi.com       mail exchanger = 30 relay2.fastweb.it.
praxi.com       mail exchanger = 10 alfa.praxi.com.

The first (alfa.praxi.com 213.156.48.132) MX is a fake.

# echo to:[EMAIL PROTECTED] | /var/qmail/bin/qmail-inject

From /var/log/qmail/current

@4000000046e435fb365581fc info msg 2077092: bytes 200 from <[EMAIL PROTECTED]> 
qp 
10975 uid 0
@4000000046e435fb3b591f74 starting delivery 1: msg 2077092 to remote 
[EMAIL PROTECTED]
@4000000046e435fb3b593acc status: local 0/10 remote 1/20
[...]
@4000000046e436b837ff26d4 delivery 1: deferral: 
Connected_to_213.156.48.132_but_connection_died._(#4.4.2)/
@4000000046e436b837ff55b4 status: local 0/10 remote 0/20
[...]
@4000000046e4378c1ad61054 starting delivery 8: msg 2077092 to remote 
[EMAIL PROTECTED]
@4000000046e4378c1ad6337c status: local 0/10 remote 1/20
[...]
@4000000046e4384917733644 delivery 8: deferral: 
Connected_to_213.156.48.132_but_connection_died._(#4.4.2)/
@4000000046e438491773613c status: local 0/10 remote 0/20

An old installation of qmail-toaster:

@4000000046e43ad62d48d3ac starting delivery 404392: msg 715993 to remote 
[EMAIL PROTECTED]
@4000000046e43ad62d48fea4 status: local 0/10 remote 1/20
@4000000046e43b122d4cac0c delivery 404392: deferral: 
Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/
@4000000046e43b122d4d484c status: local 0/10 remote 0/20

until the error message from mailer-daemon " this message has been in the 
queue too long".



On an other qmail server (with the same shupp toaster installation) the mail 
is delivery with success, but to the second MX, in a short time:

@4000000046e43731266e1ca4 new msg 1778912
@4000000046e43731266e285c info msg 1778912: bytes 205 from <[EMAIL PROTECTED]> 
qp 17207 uid 0
@4000000046e437312703d4c4 starting delivery 9706: msg 1778912 to remote 
[EMAIL PROTECTED]
@4000000046e437312703e07c status: local 0/10 remote 1/20
@4000000046e4376e23fbd86c delivery 9706: success: 
213.156.48.133_accepted_message./Remote_host_said:_250_Requested_mail_action_okay,_completed./
@4000000046e4376e23fbebf4 status: local 0/10 remote 0/20
@4000000046e4376e23fbf3c4 end msg 1778912

Where is the difference?
Thanks
-- 
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> Presidente, http://www.prato.linux.it

Reply via email to