Hmm, thats true... But in this case it doesn't accept it for delivery, and
the sender doesn't get to know that either.
I realized that in most cases it's not a problem, since mostly MailHost is
used to send mailforms to a specific set of recipients, and then you don't
want to tell the website visitor that one address didn't work, as long as
another one did.
So maybe it's not much of a problem. I still don't like it though, which is
why I'd like the option of selecting the behaviour. :-)
----- Original Message -----
From: "Andreas Jung" <[EMAIL PROTECTED]>
To: "Lennart Regebro" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, November 15, 2001 1:08 PM
Subject: Re: [Zope-dev] What to do when one mail recipient fails out of
> This approach makes no sense. Email uses the store-and-forward principle.
> This means your local mailserver could accept the delivery but it can
> never guarantee you that the mail is really delivered to the recipients.
> It can only confirm that it accepts the email for delivery and nothing
> ----- Original Message -----
> From: "Lennart Regebro" <[EMAIL PROTECTED]>
> > My thought about how to solve this is to make an addition to
> > smtplib.SMTP.sendmail(), an new parameter "stopOnRcptErr" or something,
> > that defaults to "False", which gives todays functionality. MailHost
> > could then call smtplib.SMTP.sendmail with stopOnRcptErr=True, which
> > would then raise a SMTPSenderRefused error if any of the recipients
> > fail.
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -