On 18/04/14 17:24, Brian E Carpenter wrote:> oops wait - I mean if the
*sender* has a yahoo address and
the recipient's mail system checks the DMARC
On 18/04/2014 17:21, Brian E Carpenter wrote:
> Yahoo's recent DMARC policy change would seem likely to give you
> problems too, if any of your users have *(a)yahoo.com as their
> regular address.
Yep, that looks like a very similar issue.
On 18/04/14 18:00, Mark Foster wrote:
In my experience, your options are
1) Don't allow forwarding through to any platform that enforces SPF, or
2) Don't allow forwarding at all, or
3) Require your forwarding system to also rewrite the envelope-sender.
The following may be of interest:
based on a cursory google search,
I'd found the first link but not the second. It occurred to me
afterwards that remailing need not be as intrusive as I'd thought - just
rewriting the envelope sender, and possibly adding a Sender header
should be enough; the From and Reply-to headers should be ok as they
I'm slightly unclear as to what SPF is asserting - is it just the
Anyway, it seems like the plan is to use the option I said I preferred
anyway - put an IMAP/POP/Webmail server within the organisation, which
probably means outgoing mail will go through it as well, which is a good