| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
version, which sits in the pythonlib subdirectory anyway.
|
| |
|
|
| |
scott
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
can be instructed to send delivery-status-notices only when the
delivery fails, not for intermediate warnings.
This is modelled after the patches dan ohnesorg submitted quite a
while back - but they really were pretty fouled up, particularly when
the receiving hosts doesn't support dsn, so it's really rewritten.
(And only around 15 lines total change, mostly different than the
original patch.)
Once we get bounce handling more able to adapt to various formats, we
might want to reenable warnings to help track unreachability status.
Until then they are a nuisance. And we should have shifted over to
the python-distribution smtplib.py well before then - as of 1.5.2 it
(will/does) have esmtp support of a sort - and we shouldn't be
dabbling in this garbage.
And yes, somebody slap my hand for adding a new feature - it'll hurt
so good if it means eliminating the goddamn warning notices, the
plague of large list administrators... (I really wanted to get this
working before midnight - when passwords go out, to hundreds of
python.org mailman maillist subscribers!)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
recognized as bad and refused immediately (rather than being queued
up, as happens for any offsite recipients). In particular, had to
detect whether all recipients in the batch failed, and then just
return - otherwise the DATA command would fail (no valid recipients),
and raise a disruptive exception.
It's worth noting that no bounce is generated for invalid local
recipients, which means now way to disable or even notice that they're
bad. This should be rectified at some point, but offhand i'm not sure
the right way, other than by special casing local deliveries. Anyway,
i left an XXX note to sorta this effect in the code.
And finally - it looks like the "official" python smtplib already does
the right kinds of thing regarding bad recipients, which makes me
feel good about merging with it.
|
| |
|
|
| |
the time.
|
| |
|
|
|
|
| |
return - despite the fact that lastresp is not apparently used
anywhere, i'm not ready to just yank it, and so it might as well be in
the right place.
|
| |
|
|
|
| |
we're specifying the recipients. This way, one bad one in a batch
will not clobber the whole send...
|
| |
|
|
| |
RCPT and MAIL commands).
|
| |
|
|
| |
recipients could be a string or a list of strings...
|
| | |
|
| |
|
|
|
|
|
| |
do so.
Added a copy of the GNU GPL.
Added information about mailman-users in README, and reworded some text in there (made the credits less verbose... perhaps they should move to a credits file?)
|
|
|
whatever mail delivery agent is there.
|