*snip* > > It sounds like you should be using spamass-milter or > mime_defang. These > tie SA into the MTA before delivery. That way, if a return receipt is > requested, it can be generated with the original sender, since their > address will still be in the envelope from.
I keep hearing more and more about mime_defang. I'm going to check it out. But for now, I just turned off these in the exchange server. :) > > Of course, you'll end up scanning outgoing messages this way if you > don't take other steps to prevent it. Yeah, I definetly didn't want the overhead of that. > > Is there a way to stop this envelope change, or should I > try to stop returns > > from the internal exchange server? I realise this isn't exactly RFC > > compliant :( > > IIRC, there's no requirement to honor return receipts. I > think you can > throw them all away and still meet RFCs. > I don't think we have to either. I just killed them. I'm thinking that the envelope sender changing is no big deal. It's only for incoming in the company. Not like I'm doing it as an ISP. So for now everything is cool :) Custom procmail rules soon. After giving it more thought anyway, I relised this receipt problem was a sendmail question and not SA. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
