Re: [Mailman-Users] FW: Spamassassin content preview ending up posted to list

On 11/05/2014 08:15 PM, Mark Sapiro wrote: > > OK. I poked around and found the archived message at > . > > Something seemed to think that the line between 'Greg Roberts? [...]' > and 'Content analysis details:'

Re: [Mailman-Users] FW: Spamassassin content preview ending up posted to list

On 11/05/2014 05:50 PM, Peter Shute wrote: ... > X-Ham-Report: Spam detection software, running on the system > "cloud3.emwd.com", has identified this incoming email as possible spam. The > original message has been attached to this so you can view it (if it isn't > spam) or label similar fu

[Mailman-Users] FW: Spamassassin content preview ending up posted to list

Sorry, I forgot to Cc the list. -Original Message- From: Peter Shute Sent: Thursday, 6 November 2014 12:49 PM To: 'Mark Sapiro' Subject: RE: [Mailman-Users] Spamassassin content preview ending up posted to list The dot was missing in the X-Ham-Report header but not in the message body

Re: [Mailman-Users] Spamassassin content preview ending up posted to list

On 11/05/2014 01:03 PM, Peter Shute wrote: > > Looking at the original message in the moderation alert email, it looks ok to > me, but I can see that the dot has been dropped in the content preview in the > X-Ham-Report header which I think spamassassin has inserted. This header has > multiple

[Mailman-Users] Spamassassin content preview ending up posted to list

I had a complaint yesterday that a URL in a posting to our list had become corrupted - one of the dots in the domain name had been dropped. Looking at the original message in the moderation alert email, it looks ok to me, but I can see that the dot has been dropped in the content preview in the

Re: [Mailman-Users] Archive not woring on Debian install

Thank you. >> I am new to mailman (as a site admin) and I cannot find out how to get >> the archive running on my debian/postfix/mailman installation. >> >> The list works fine, but it seems that no crontab is working. > > Your cron jobs are probably mailing their error output to 'mailman' > which