Probably the "right" way of doing this is to have SA create a multi-part MIME message and insert a new part which is the report. That way users can still see the original message unharmed, they can read the report, etc. etc.
C on 1/29/02 9:56 AM, Dallas Engelken at [EMAIL PROTECTED] wrote: > ----- Original Message ----- > From: "Michael Geier" <[EMAIL PROTECTED]> > To: "[sa-talk] mailing List" <[EMAIL PROTECTED]> > Sent: Tuesday, January 29, 2002 11:42 AM > Subject: RE: [SAtalk] question regarding report-template and HTML email > > >> ok... I got this response twice... >> >> I had the report in the headers before, but I wanted my users >> to actually see why the message was getting tagged. And, if I >> put the report in the headers, (l)users will be asking me how >> to view their email headers constantly (as I am currently >> delivering to default mailbox with rewrite_subject=1) >> > > What is easier, having users read email headers or reading an email in HTML > source code??? > IMHO, the spam report gets annoying as hell, so I like to keep mine in the > headers. > >> hmmm...guess I'll keep looking at the code. >> Thanks for the suggestions. >> > > > > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > > > _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
