Ġ: SMTP Response: 250 2.6.March 24, 2001, was a banner day for Mac users. Here's the SMTP log from one of the tries:Ġ: SMTP Response: 334 VXNlcm5hbWU6Ġ: Logging suppressed for this command (it probably contained authentication information)Ġ: SMTP Response: 334 UGFzc3dvcmQ6Ġ: SMTP Response: 235 2.7.0 Authentication successful.Ġ: SMTP Send: MAIL FROM: SIZE=1105Ġ: SMTP Response: 250 2.1.5 SMTP entering state: 7Ġ: SMTP Response: 354 Start mail input end with. Please verify that your SMTP server setting is correct and try again, or else contact your network administrator") The server may be unavailable or is refusing SMTP connections. The SMTP-log looks fine, the e-mail is delivered, but it I still get "Send Message Error" ("The message could not be sent because connecting to SMTP server failed. I am seeing the same problem with an Exchange IMAP server. A spurious timeout at this point would be very wasteful and would typically result in delivery of multiple copies of the message, since it has been successfully sent and the server has accepted responsibility for delivery. When the receiver gets the final period terminating the message data, it typically performs processing to deliver the message to a user mailbox. Waiting only for 1 minute for a reply to "." is wrong and is in serious violation of the relevant RFC's.īefore this RFC-mandated limit, it can give out a "warning" that it thinks the server is too slow, but giving an error is wrong. Thunderbird should wait until the RFC-mandated 10 (TEN) minute timeout limit before giving an "error". Please verify that your SMTP server setting is correct and try again, or else contact your network administrator. The message could not be sent because connecting to SMTP server (name of server) failed. Thunderbird will deliver the mail successfully but displays the following spurious and misleading error message after a mere 1 (ONE) minute: If possible, make sure that the box hosting the MTA is having a high system load, to make sure the scan will take a long time Compose a message that will take a long time for scan for viruses/spamģ. Find or configure an SMTP server which will take a long time to check for spam or virusesĢ. But it should not issue an error unless it is more sure that what it says is correct (#2 above) in any case part of what it says is very obviously false (#1 above).ġ. Thunderbird can issue a warning if it thinks that the server is slow. So Thunderbird's behaviour is arguably in serious violation of these RFC's. In fact in both RFC's there is no timeout less than 2 minutes. However, both RFC 1123 (5.3.2) and RFC 2821 (4.5.3.2) states that the sender should wait 10 (TEN) minutes after the final "." before deducing that the MTA has stopped responding. The "problem" is essentially a slow reply to the "." command during the DATA phase. The error message is stating a possibility which is essentially ruled out and is factually false.Ģ. Thunderbird's EHLO greeting is acknowledged, so are the MAIL FROM, RCPT TO, and DATA commands so there is absolutely no problem "connecting" to the server at all, and the server is obviously accepting SMTP connections. This is problematic for a number of reasons:ġ.
(The error message is given below in "Actual Results".) This will result in the user resend the message, which ultimately will result in a string of duplicate messages being sent.
OS X MAIL NUMBER OF MESSAGES TOO HIGH MAC OS X
User-Agent: Mozilla/5.0 (Macintosh U Intel Mac OS X en-US rv:1.8.1) Gecko/20061010 Firefox/2.0īuild Identifier: Mozilla Thunderbird version 1.5.0.2 (20060308)Īfter hitting the "Send button", if the configured MTA takes too much time to check for spam, the mail will be *delivered successfully* but Thunderbird will display a misleading error message that connection to the server failed.
0 kommentar(er)
