> The problem is that the script that you're using with > Communigate *assumes* that the X-Envelope headers will remain > intact, most likely because that script was written before SA > 2.50 when report_safe was introduced. > > Most mailserver configurations don't rely on message headers > to know where to deliver the message to after filtering and > therefore don't have this problem. As I mentioned in my > previous message, doing so is technically > *wrong* anyway.
So what is the proper way to do this? How do other mail servers handle it? If the resubmitted message doesn't have any envelope-to headers, how does the mailserver know who *really* to deliver it to? Do they just keep track of the message ID and don't rely on headers at all? Or should my post-processing script re-add those headers after it's been scanned? > > Until someone comes up with a better integration script for > SA + Communigate, you'll have to use report_safe 0 mode.... Sounds like it. But report_safe 1 is so much cooler... Sad not to be able to use it. And I agree, typically you wouldn't want a mailserver just blindly delivering to the to: and cc: addresses from the headers, but hey, that's what Communigate Pro does, but of course only via messages submitted via the PIPE interface. SMTP submitted messages of course go through all the normal checks, but PIPE must assume you've correctly formatted your message and doesn't do any anti-relay checking or the like. ------------------------------------------------------- This SF.net email is sponsored by: Etnus, makers of TotalView, The best thread debugger on the planet. Designed with thread debugging features you've never dreamed of, try TotalView 6 free at www.etnus.com. _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
