This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lcatucci
Recipients giampaolo.rodola, lcatucci, vstinner
Date 2008-12-01.23:50:34
SpamBayes Score 2.9151934e-05
Marked as misclassified No
Message-id <1228175436.27.0.454493262242.issue4473@psf.upfronthosting.co.za>
In-reply-to
Content
I understand the need to keep things simple, but this time the split
seemed a bit overkill. If needed, I'll redo the patch into a small
series. Thinking of it... I was unsure if it really made sense to split
out smtp/pop/imap patches instead of sending them all at once... :-)

As for the shutdown before close, it's needed to let the server know
we are leaving, instead of waiting until socket timeout. This is the
reason I need to keep the reference to the wrapped socket.

You don't usually configure maildrop servers to limit the number/rate of
connects as you do on smtp servers; still, you could get into problems
with stateful forewalls or the like.
History
Date User Action Args
2008-12-01 23:50:36lcatuccisetrecipients: + lcatucci, vstinner, giampaolo.rodola
2008-12-01 23:50:36lcatuccisetmessageid: <1228175436.27.0.454493262242.issue4473@psf.upfronthosting.co.za>
2008-12-01 23:50:35lcatuccilinkissue4473 messages
2008-12-01 23:50:35lcatuccicreate