On Thu, 29 Aug 2002, Ganeshh wrote:
> Please let me know where is the problem? I dont have problem
> any other domains sending mails to my mail server.
well ... it is not conformant the the RFC which defines in
part the protocol compliant mail exchange in this circumstance
> MX=[mail.ns.net] {61.11.74.7}
> Attempting SMTP connection to [61.11.74.7 : 25]
> Waiting for socket connection...
> Socket connection established
> Waiting for protocol initiation...
> 30 second wait for protocol timeout exceeded.
ummm, RFC 2821 suggests 5 minutes at section 4.5.3.2
http://asg.web.cmu.edu/rfc/rfc2821.html#sec-4.5.3.2
although the first delivery pass some MTA use a faster
fall-back
> Attempting MX: P=020 D=ns.net TTL=(1385) MX=[mail.symonds.net]
> {63.194.20.32}
> Attempting SMTP connection to [63.194.20.32 : 25]
> Waiting for socket connection...
> Socket connection established
> Waiting for protocol initiation...
> 30 second wait for protocol timeout exceeded.
> This message is 62 minutes old; it has 0 minutes left in this queue
> Primary queue lifetime exceeded; message placed in retry queue*
I cannot see any excuse for a fast timeout when using a
secondary MX host. Which MTA are you using with this
behaviour? The RFC explains the 'why' of timings much better
than I can summarize here.
-- Russ Herrold
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
