On Sat, Mar 28, 2015 at 2:42 AM, Rob
Kendrick <rjek@rjek.com>
wrote:
> On Fri, Mar 27, 2015 at 10:06:29PM -0700,
Coda Highland wrote:
>> On Fri, Mar 27, 2015 at 10:03 PM,
Jonathan Goble <jcgoble3@gmail.com>
wrote:
>> > I'm getting that also.
>> >
>> > The messages from Yahoo going to
spam is the result of a deliberate action
>> > by Yahoo itself, Google "Yahoo
DMARC reject policy" for more info. I'm not
>> > sure if the list can do anything
to prevent it.
>> >
>> > The "violation of recommended
sender guidelines" seems to happen primarily
>> > on messages from corporate
domains.
>>
>> It is actually possible but it comes
at the cost of making the list
>> messages come from the list itself
instead of retaining the original
>> From: field. There's some ick
involved in modifying the e-mail headers
>> (since you lose sender information
with no good way to put it back)
>> but it would fix the delivery
problem.
>
> It's a problem with all mailing lists
that DKIM signatures get
> corrupted, because the headers are
altered. DMARC and SPF don't help,
> either.
>
> However, the From: header is never
changed. (The MAIL FROM: at SMTP
> time is set to an address belonging to
the list so the mailing list
> software can process bounces: otherwise
the poster would get all the
> bounces.)
>
> GMail are a law unto themselves when it
comes to interacting with other
> mail systems. My advice is generally to
just avoid using them, but this
> sadly isn't always possible.
>
> Perhaps if everybody fishes them out of
their spam folder GMail's insane
> spam filter will figure it out.
>
> B.
>
No, I mean, I know that, I'm saying if we DID just
craft an entirely
new set of headers for the outgoing messages, it
would avoid the
spambox problem... at the cost of losing sender
data.
