Mark Sapiro added the comment:
> parsing 'merwok'
> expected ('merwok', '')
> got ('', 'merwok')
I think ('', 'merwok') is the correct result. I think most if not all MUAs/MTAs
will interpret an address wit
Mark Sapiro added the comment:
I'm not completely sure about this, but here's my thoughts. In the
scenarios I've seen, the 421 reply/disconnect only occurs in response to
a RCPT which has an invalid address and follows several prior refused
RCPTs. In this case, I think the prop
New submission from Mark Sapiro :
The Mailman GUI contains a few links to the python.org documentation
which are now broken. These links and the current equivalents are:
http://www.python.org/doc/
works, but could map to http://docs.python.org/
http://www.python.org/doc/current/
works
Mark Sapiro added the comment:
This problem also occurs when building the 2.6.1 parser module on Cygwin
1.5.25. It did not occur with Python 2.6 or 2.5.x.
The error from 'make' is
building 'parser' extension
gcc -shared -Wl,--enable-auto-image-base
build/temp.cygwin-1.5.25
Changes by Mark Sapiro :
--
nosy: +msapiro
___
Python tracker
<http://bugs.python.org/issue4288>
___
___
Python-bugs-list mailing list
Unsubscribe:
Mark Sapiro added the comment:
Thank you for adding the redirects, and for getting them right in spite
of my garbling some of them in the original report.
I have updated the links for the next Mailman release.
___
Python tracker
<http://bugs.python.
New submission from Mark Sapiro :
The message method get_params() and the related get_param() and
get_filename() do not properly decode an RFC 2231 encoded parameter such
as the following:
Content-Disposition: inline;
filename*0="Re: [Mailman-Users] Messages shunted with \"
New submission from Mark Sapiro :
RFC821 upon which smtplib was originally based does not define a 421
status code and implies the server should only disconnect in response to
a QUIT command.
Subsequent extensions in RFC2821 (and now RFC5321) define situations
under which the server may return
