Email Messages Triggering Spam Filter [WAS: Re: How to configure the budget report to put a zero or space in bgt & diff columns]

[ktm at rice.edu]

On Wed, Jul 23, 2014 at 09:28:39AM -0500, Tommy Trussell wrote:
> On Wed, Jul 23, 2014 at 5:18 AM, Dave Koelmeyer <
> dave.koelmeyer at davekoelmeyer.co.nz> wrote:
> 
> >
> > On 22/07/14 06:58, Steve Nospam wrote:
> >
> >> Hmmm, you are correct.  I'm not sure why I had a problem before but I'm
> >> really happy that I can work with the exported file as it is!  Thanks.
> >>
> >
> > Off-topic: apparently by virtue of your rather unique surname, every
> > single email from you is being dumped straight into my junk email folder.
> > You might want to think about changing this as other recipients may be
> > missing mail from you.
> >
> >
> Actually I believe it ISN'T the user's name causing Steve Nospam's email to
> get trapped. It's more likely due to a change in Yahoo domain registrations
> (effective April 2014 if I recall correctly) intended to reduce email
> abuse, but also causes all yahoo messages to be flagged as spam when
> re-directed through certain email lists (such as GnuCash's). I believe this
> has been mentioned on this list a couple of times in the past month.
> 
> Technically, yahoo's domain setting indicates that only yahoo's official
> servers are allowed to handle email from their domains. Email lists that
> modify email headers so that the messages appear to come from the list
> server will still work OK.
> 
> I believe this change affects yahoo.com email as well as many of the
> domains they manage email for -- ymail.com, att.com, sbcglobal.net, etc.
> 
> One workaround would be for those affected to choose another provider for
> your email list messages. Another workaround is to add a spam exception to
> your filters for the GnuCash list. (This is what I did in my Gmail account.
> Gmail still indicates the messages that WOULD have been trapped as spam.)
> 
> Alternatively the GnuCash lists could start modifying email headers, a
> change to long-standing policy.

It looks like the GnuCash mailing list is using Mailman 2.1.18. I believe
that there is a patch available to address this issue. We have that problem
here and will be patching our system soon. A quick fix is to use the
mailing list address as the sender instead of the address of the message
submitter. It is a per-list configuration setting.

Regards,
Ken