[issue19679] smtpd.py (SMTPChannel): implement enhanced status codes

[Barry A. Warsaw]

Barry A. Warsaw  added the comment:

I'm closing this as won't fix since smtpd.py is deprecated and will likely not 
get any future development.  Please see aiosmtpd as a much better third party 
replacement.

--
resolution:  -> wont fix
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19679] smtpd.py (SMTPChannel): implement enhanced status codes

[Leslie P. Polzer]

Leslie P. Polzer added the comment:

Sounds reasonable, I will propose a patch soon. Thanks!

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19679
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19679] smtpd.py (SMTPChannel): implement enhanced status codes

[Leslie P. Polzer]

Leslie P. Polzer added the comment:

Sorry for the confusion, the second comment (#msg203622) should actually have 
been a separate ticket.

Since you'd like to preserve conn I will just change the title of this ticket.

--
title: smtpd.py (SMTPChannel): get rid of conn attribute - smtpd.py 
(SMTPChannel): implement enhanced status codes

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19679
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19679] smtpd.py (SMTPChannel): implement enhanced status codes

[Leslie P. Polzer]

Leslie P. Polzer added the comment:

I am indeed referring to the enhanced status codes proposed in RFC 3463. This 
would just entail adding information to the status codes, converting them from 
the format simple status code human-readable string to simple status 
code enhanced status code human-readable string.

In this it doesn't seem necessary to differentiate by HELO/EHLO; neither is it 
demanded by the standard nor does it result in an incompatible form of 
traditional HELO status messages. HELO clients should just interpret the first 
three digits and regard the rest as part of the human readable informal section.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19679
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19679] smtpd.py (SMTPChannel): implement enhanced status codes

[R. David Murray]

R. David Murray added the comment:

Should and do are different, though.  I wouldn't be at all surprised to 
find legacy code that did look at the text string part of the message.  
Particularly test code, which is a place that smtpd gets used commonly.

Which probably means that what we really need is a keyword argument to the 
SMTPServer constructor (analogous to data_size_limit) that indicates whether or 
not enhanced status codes are enabled, and have it be off by default.  If 
desired, we could then issue a warning that enhanced status codes will be 
enabled by default in 3.6.  That kind of process is our usual 
backward-compatibility dance.  In this particular instance we could go one step 
farther and add a deprecation warning in 3.6 that the ability to set enhanced 
status codes off will go away in 3.7.  If anybody remembers to carry through on 
it :)

--
versions: +Python 3.5 -Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19679
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com