masqmail
view tpl/warnmsg.tpl @ 246:4cff8638dd9b
SMTP client: tries EHLO now always first
Changed the behavior of the SMTP client. Now always an EHLO greeting
is sent, no matter what kind of greeting text the server had sent. If
the EHLO failed, an HELO greeting is tried as fall back. This is the
behavior RFC 2821 requires (section 3.2).
This change will fix setups that were not possible to sent to a
server because that requires AUTH but hadn't said ``ESMTP'' in its
greeting message.
See also: Debian bug #349211
Thanks to Steffen (inne)
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Thu, 28 Oct 2010 16:40:02 -0300 |
parents | |
children |
line source
1 Subject: Warning: could not yet send message
2 From: MAILER-DAEMON@${host_name}
3 To: ${return_path}
4 MIME-Version: 1.0
5 Content-Type: multipart/mixed;
6 boundary="${uid}/${host_name}"
8 This is a MIME-encapsulated message.
10 --${uid}/${host_name}
11 Content-Description: Notification
12 Content-Type: text/plain
14 This message was sent to you by the mailer daemon (${package} ${version})
15 at ${host_name}.
17 Sorry, but your mail could not yet be delivered to all recipients.
18 Delivery to the following recipients has been defered:
20 @failed_rcpts
22 Delivery will be tried again, until it is either successful or a
23 timeout has been reached. If the latter happens, you will get a
24 delivery failure notice.
27 This error message may give you a hint about what caused the
28 delay:
30 ${err_msg}
32 If you need help, write to <postmaster@${host_name}>.
34 The headers of your message follow attached:
36 --${uid}/${host_name}
37 Content-Description: Undelivered Message Headers
38 Content-Type: message/rfc822
40 @msg_headers
42 --${uid}/${host_name}--