[Exim] exim bounces a mail before trying to deliver it

Due to mail.netaxs.com being apparently broken and refusing to issue an
prompt for at least 2mn if it doesn't get an answer to the ident request it
sends (even a valid ICMP unreachable, which they probably throw away :-( ),
our exim hints know that the host isn't taking Email from us.

kenny:~# exinext thyrsus.com
Deliver: mail.netaxs.com [207.8.186.26] error 110: Connection timed out
first failed: 28-Jan-2001 22:27:15
last tried: 08-Feb-2001 10:46:30
next try at: 08-Feb-2001 18:46:30
past final cutoff time

However, is it valid for exim to not even try to deliver or spool a mail?
Here it bounces it right away

kenny:~$ Mail -v bouncetest@???
Subject: test

test
.
Cc:
LOG: 0 MAIN
<= merlin@??? U=merlin P=local S=335 T="test"
kenny:~$ Exim version 3.22 debug level 1 uid=8 gid=8
Berkeley DB: Sleepycat Software: DB 2.4.14: (6/2/98)
delivering message 14QwIf-0006Dp-00
LOG: 0 MAIN
** bouncetest@??? R=lookuphost T=remote_smtp: retry time not reached for any host after a long failure period
Exim version 3.22 debug level 1 uid=8 gid=8
Berkeley DB: Sleepycat Software: DB 2.4.14: (6/2/98)
LOG: 0 MAIN
<= <> R=14QwIf-0006Dp-00 U=mail P=local S=1177 T="Mail delivery failed: returning message to sender"
LOG: 5 MAIN
Error message sent to merlin@???
LOG: 0 MAIN
Completed
Exim version 3.22 debug level 1 uid=8 gid=8
Berkeley DB: Sleepycat Software: DB 2.4.14: (6/2/98)
delivering message 14QwIf-0006Dr-00
LOG: 0 MAIN
=> merlin <merlin@???> D=procmail T=procmail_pipe
LOG: 0 MAIN
Completed


kenny:~# exim_fixdb /var/spool/exim retry
> T:mqueue.netaxs.com:207.8.186.27

0 error number: 110 Connection timed out
1 extra data:   77
2 first failed: 19-Dec-2000 11:03:41
3 last try:     23-Dec-2000 11:08:11
4 next try:     23-Dec-2000 19:08:11
5 expired:      yes

> d T:mqueue.netaxs.com:207.8.186.27
field number or d expected
> T:mqueue.netaxs.com:207.8.186.27 d
deleted
> T:mail.netaxs.com:207.8.186.26

0 error number: 110 Connection timed out
1 extra data:   77
2 first failed: 28-Jan-2001 22:27:15
3 last try:     08-Feb-2001 10:46:30
4 next try:     08-Feb-2001 18:46:30
5 expired:      yes

> T:mail.netaxs.com:207.8.186.26 d
deleted


After that (and accepting ident request on our mail server to please the
remote mail server), mail went through just fine.


Is the initial bounce expected behavior?

Thanks,
Marc
-- 
Microsoft is to operating systems & security ....
                                      .... what McDonalds is to gourmet cooking

Home page: http://marc.merlins.org/ | Finger marc_f@??? for PGP key