Whatever it is you are suggesting -- it's a bad idea. Some systems use '^From ' as the message delimiter for mboxes.
Other systems don't need, or even -break-, if a '^From ' line is there. A line with '^\tFrom ' is worse than useless - it will continue to confuse some mail software, and won't help the ones that need '^From '. Justin has already completely proven that '^From ' is a PITA ... (I think every possible way to handle it has been tried ...) and the command-line switch is the best (and easiest) solution by far. It Just Works. On Sat, 19 Jan 2002, [EMAIL PROTECTED] wrote: > > > Having the from line is no problem, just having a <TAB> in front of it fixes > the problem.. Maybe you could try this behavior, and see if it works for > everyone. > > > -----Original Message----- > From: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Sent: 1/18/02 10:35 PM > Subject: Re: [SAtalk] Bug in NoMailAudit.pm for Spamassassin 2.0 > > > [EMAIL PROTECTED] said: > > > This is on a spamd/spamc setup using qmail and qmail scanner, which > then > > forwards the mail to a mirapoint virus scanning server, which if it > finds a > > "From" header at the beginning of the line, will MANGLE the header. > > OK -- we have several people using spamc/spamd who REQUIRE the From > line, and several people using spamc/spamd who require that it > NOT be present. > > I'm going to turn it on by default (ie back to 3 days ago's behaviour), > and add command-line flags to allow admins to override this. it's > safest. > > --j. > -- Charlie Watts [EMAIL PROTECTED] Frontier Internet, Inc. http://www.frontier.net/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
