also sprach Santiago Vila <sanvila@unex.es> [2005.05.07.1403 +0200]: > Why are you so much worried about the envelope sender, when it is > usually forged? You are not trying to bounce messages that you > didn't want to receive back to the sender, are you? (that would be > bounce-spam). Well, sure. The point is that right now, my server rejects a lot of spam, so the bounces end up in my regular mailbox. I am effectively boune-spamming myself. So I'd rather have the bounce generated by master go elsewhere. > I'm more worried about "! my@address.net" rewriting the message body, You mean the payload? It rewrites the 822 header, but not the message body. > so I usually do something like "formail -R Sender: X-Master-Sender:" > in master and then "formail -I Sender: -R X-Master-Sender: Sender:" on > the machine where I actually receive the message. okay, that's also an interesting solution, but it won't solve my problem: if the final recipient server rejects the message which procmail forwarded, I get the bounce. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <madduck@debian.org> : :' : proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! "sobald man über niveau spricht ist man längst darüber hinweg." -- thomas krafft
Attachment:
signature.asc
Description: Digital signature