Hi Ralph! Thanks for your reply! On 4/20/20 12:19 PM, Ralph Seichter wrote:> I suggest you don't use Sieve for this, but simply configure Postfix > to reject messages to @old.domain.com with the desired message. MTA > rejections signal clearly that the message has not been delivered, and > you can also include an URL pointing to a web page with more detailed > information.However, this means those emails are not actually delivered anymore. For now, I would like them to *be* delivered, so we still have them in case something important comes in. Your postfix suggestion would be my next step, in a couple of months perhaps. Hopefully someone has a suggestion for my sieve script. Thanks again, MJ
* mj:> this means those emails are not actually delivered anymore.Sure. That's how I interpreted your notification text "This message is sent automatically, and your message has NOT been read nor forwarded." If the message is not being read, why accept it in the first place?> For now, I would like them to *be* delivered, so we still have them in > case something important comes in.Speaking for myself: If I send email to a business partner, that email can be a) rejected, so I know I'll have to find another way to reach the intended recipient, or it can be b) accepted, in which case I expect it to be read/processed. What you describe seems to be neither fish nor flesh to me. Using MTA rejects leaves no doubt that the *sender* has to become active. As I understand it, that is you goal, is it not? -Ralph
Well, I do not use postfix, but qmail. I would however, create an autorepond telling them the new address and then fwd the old address to the new one. But nothing to do with sieve, it?s at the SMTP level. Remo> On Apr 20, 2020, at 08:40, Ralph Seichter <abbot at monksofcool.net> wrote: > > * mj: > >> this means those emails are not actually delivered anymore. > > Sure. That's how I interpreted your notification text "This message is > sent automatically, and your message has NOT been read nor forwarded." > If the message is not being read, why accept it in the first place? > >> For now, I would like them to *be* delivered, so we still have them in >> case something important comes in. > > Speaking for myself: If I send email to a business partner, that email > can be a) rejected, so I know I'll have to find another way to reach the > intended recipient, or it can be b) accepted, in which case I expect it > to be read/processed. > > What you describe seems to be neither fish nor flesh to me. Using MTA > rejects leaves no doubt that the *sender* has to become active. As I > understand it, that is you goal, is it not? > > -Ralph
> On 20 Apr 2020, at 04:27, mj <lists at merit.unu.edu> wrote: > > Hi Ralph! > > Thanks for your reply! > > On 4/20/20 12:19 PM, Ralph Seichter wrote: >> I suggest you don't use Sieve for this, but simply configure Postfix >> to reject messages to @old.domain.com with the desired message. MTA >> rejections signal clearly that the message has not been delivered, and >> you can also include an URL pointing to a web page with more detailed >> information. > > However, this means those emails are not actually delivered anymore.Yes, with a rejection message that informs why the message was not delivered. This is the best thing you can do as it will force people to actually change the email. If you delay this by doing something temporary, all you are doing is delaying it. Once you cut off the old email you?ll be in the exact same situation you are in right now, as very few people will update email addresses. If all you do now is autrespond with an automated message, most people will never see that message. And if your auto-responder is paying the message is not read or forwarded, what are you gaining? It is much better for the sender to get an actual error which they are much more likely to see. The other thing you can do is NOMX the old domain. -- in the long run there's still time to change the road you're on
I do agree with that. It depends on what he wants to do and how to handle the old domain stuff. Remo> On Apr 20, 2020, at 18:13, @lbutlr <kremels at kreme.com> wrote: > > > >> On 20 Apr 2020, at 04:27, mj <lists at merit.unu.edu> wrote: >> >> Hi Ralph! >> >> Thanks for your reply! >> >> On 4/20/20 12:19 PM, Ralph Seichter wrote: >>> I suggest you don't use Sieve for this, but simply configure Postfix >>> to reject messages to @old.domain.com with the desired message. MTA >>> rejections signal clearly that the message has not been delivered, and >>> you can also include an URL pointing to a web page with more detailed >>> information. >> >> However, this means those emails are not actually delivered anymore. > > Yes, with a rejection message that informs why the message was not delivered. This is the best thing you can do as it will force people to actually change the email. > > If you delay this by doing something temporary, all you are doing is delaying it. Once you cut off the old email you?ll be in the exact same situation you are in right now, as very few people will update email addresses. > > If all you do now is autrespond with an automated message, most people will never see that message. And if your auto-responder is paying the message is not read or forwarded, what are you gaining? It is much better for the sender to get an actual error which they are much more likely to see. > > The other thing you can do is NOMX the old domain. > > > > -- > in the long run there's still time to change the road you're on-------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20200420/9e5b69e6/attachment.html>