Allan Hansen writes:
> 69,74d68
> <
> < # Added to deal with DMARC issuej
> < name, addrs = parseaddr(msg.get('from'))
> < addrs += '.invalid'
This is known to be a bad idea, as it increases the spam score at many
sites (because the author's mail domain doesn't resolve). Su
Stephen,
Much appreciated.
Checking for aol.com and yahoo.com here alone will not work. I have a bunch of
other subscribers that have
accounts with providers that are owned by Yahoo (mostly) and AOL, but whose
addresses are not of this form.
I would have to do this for all addresses, to be safe
Allan Hansen wrote:
>Stephen,
>Much appreciated.
>Checking for aol.com and yahoo.com here alone will not work. I have a bunch of
>other subscribers that have accounts with providers that are owned by Yahoo
>(mostly) and AOL, but whose addresses are not of this form.
>I would have to do this fo
Hi Stephen,
Yes, there is a good reason. I’m using Mailman as it came with the OS X Server
and am not prepared to replace it. Also, Mailman no longer comes pre-installed
on the Apple platform, so I’m basically stuck. This is why I tried the simplest
hack I could find. I have 44 busy lists and I
Allan Hansen writes:
> Checking for aol.com and yahoo.com here alone will not work. I have
> a bunch of other subscribers that have accounts with providers
> that are owned by Yahoo (mostly) and AOL, but whose addresses are
> not of this form.
Oddly enough, it turns out that they only use DM
I wonder why then I got a bunch of issues with btopenworld.com, which
apparently is Yahoo based.
I just checked btopenworld.com with the ‘host’ command and as you say, it has
no ‘reject’:
$ host -t TXT _dmarc.btopenworld.com
_dmarc.btopenworld.com descriptive text "v=DMARC1\; p=none\; fo=1\;
ru
On 05/24/2015 03:19 PM, Allan Hansen wrote:
>
> $ host -t TXT _dmarc.btopenworld.com
> _dmarc.btopenworld.com descriptive text "v=DMARC1\; p=none\; fo=1\;
> rua=mailto:dmarc...@btinternet.com, mailto:dmarc_...@auth.returnpath.net\;";
The domain publishes DMARC p=none. Thus, no ISP should treat
