Linux -Blue forest free software | Return to home page | Site Map | Search WWW | Contact Us |
Your current position : Homepage > Free Software > Technological exchanges >Network Communication


    

Blue Forest http://www.lslnet.com at 12:08 on July 28, 2006


Sent the wrong, who can help me find what causes this?

Reason : unable to deliver this message after 14 hours


Delivery attempt history for your mail :

Fri, 4 Jul 2003 12:34:07 +0800 (CST)
; Initial status response expected

Fri, 4 Jul 2003 10:13:54 +0800 (CST)
Error reading SMTP packet response to dot-stuffed message expected

Error reading SMTP packet response to dot-stuffed message expected

Sent the wrong, who can help me find what causes this?

SMTP connection, set up, the delivery of letters a mistake.

It could also be the other server errors.

Sent the wrong, who can help me find what causes this?

Dual also think there might be other issues, but also not the problem lies with the users. I see the other side of the server is doing the handbook, I was iplanet message server, I found on the Internet on the wrong section (below), but is qmail not know which prawn opportunity not encountered a similar situation, how to solve that, help out
FROM : Daniel KelleyDATE : 04/16/2002 19:03:29SUBJECT : RE : [Qmail-scanner-general]SMTP timeouts I have been struggling with for awhile now trying to determine why both
"; Qmail servers are timing out of my incoming SMTP connections. It is a
"; New install of 1.03 NaC1 qmail-scanner 1.10, running through tcpserver.
"; 1 is a relay for an iPlanet Server messaging server and handles/scans
"; All outgoing mail, and has an MX weight of 8 for incoming mail. Server 2
"; Handles incoming mail only for relay to the iPlanet server and has an MX
"; Weight of 0. They are both configured identically, and the timeouts are
"; Shared proportionally between them.
>;
"; 1 is a server Blade100 NaC1 1152M ram and Solaris8 03/02
"; 2 is a server 280R NaC1 4095M ram and Solaris8 03/02
>;
"; Both are set for :
"; Concurrencyincoming = 30
"; Timeoutconnect = 75
"; Timeoutremote = 1200
"; Timeoutsmtpd = 1200
>;
"; /var/qmail/supervise/qmail-smtpd/run :
>;
"; #!/bin/sh
"; QMAILDUID=`/usr/xpg4/bin/id u qmaild`
"; NOFILESGID=`/usr/xpg4/bin/id g qmaild`
"; MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
"; QMAILQUEUE= "/var/qmail/bin/qmail-scanner-queue.pl"
"; Export QMAILQUEUE
"; Echo $QMAILQUEUE "; /tmp/qmail.var
"; M \ 256 million exec /usr/local/bin/softlimit
"; /usr/local/bin/tcpserver-V H-C-P-R-l 0-x /etc/tcp.smtp.cdb
"; "$MAXSMTPD" \
"; U "$QMAILDUID" g "$NOFILESGID" 0 SMTP
"; /var/qmail/bin/qmail-smtpd 2>;&1
>;
"; I set up two days ago with some noticable improvement dnscache.
>;
"; Outside users are generally getting messages that report, "Deferred :
"; Connection timed out with [host]. " I get about 100 messages deferral
"; Qmail in the daily logs (about 3-400 before I installed dnscache), which
"; Are either "Unable_to_establish_an_SMTP_connection" or
"; "Connected_to_[host]_but_connection_died." Many of my users report
"; Getting hundreds of the same email, and one administrator from a site
"; Repeat sending the email said I was timing out on his server while it
"; Was waiting for a confirmation packet, so his mail package (I have no
"; Idea what it was) would send the mail again (one user even got 503
"; Copies of the same message over a few days until it killed that admin
"; From his queue).
>;
"; While the interface in Networks, and then I can see SMTP sessions begin
"; Just stop, but not with an error, it just stops. This seems to happen a
"; Lot with incoming Hotmail addresses. I also had a Comcast user send me
"; His bounce message which said, "Error reading SMTP packet response to
"; Dot-stuffed message expected "
>;
"; Both servers are connected to a brand new 2924 going to a Cisco PIX.
"; Router, then ISP, and have no other servers in this connection DMZ
"; Problems, so I am pretty certain there is no physical problem.

PIX-bingo. I had the same symptoms - repeat emails, deferrals, dead
Connections. If you run the PIX with SMTP fixup enabled, the PIX rewrites
Qmail 's "message queued" response such that some foreign clients do not
Understand that the message has actually been queued, despite the fact
That it has. Remote MTAs just keep waiting for a response, and eventually
Timeout. Qmail has already queued the mail, but the remote servers just
Keep trying - that 's why you' Ampere seeing so many duplicates.

If you trust the security of qmail (reasonably safe assumption), just
Disable SMTP fixup on the PIX, and your problem should disappear entirely.

Dan

>;
"; Thanks.
"; Scott
>;
>;
>; _______________________________________________
"; Qmail-scanner-general mailing list
"; "EMAIL : PROTECTED>;
"; Https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
>;

Sent the wrong, who can help me find what causes this?

Perhaps the reason you. It is because of the firewall, smtp协议 mistakes in the process.

No problem as long as you go to other places, they should be the other reasons



 Privacy Policy  Copyright © 1999-2000 LSLNET.COM. All rights reserved. Blue Forest website owners. E-mail : Webmaster@lslnet.com