[CentOS] Not To James B. Byrne

Les Mikesell lesmikesell at gmail.com
Wed Nov 12 21:11:58 UTC 2014


On Wed, Nov 12, 2014 at 2:50 PM, g <geleem at bellsouth.net> wrote:
>
>> Authentication-Results: mx.google.com; spf=neutral (google.com:
>> centos-bounces at centos.org does not designate permitted sender hosts)
>> smtp.mail=centos-bounces at centos.org; dkim=neutral (body hash did not
>> verify) header.i=@; dmarc=fail (p=QUARANTINE dis=NONE)
>> header.from=harte-lyne.ca
>
> Les,
>
> i believe problems are on your end, and not with server for James.
>
> i do not see "dmarc=fail" or "p=QUARANTINE" in *any* of his email
> headers.

They are not 'in' his headers.  They are the settings in his domain's
DNS dmarc record.

Do:
nslookup -type=txt _dmarc.harte-lyne.ca
to see the record, and you'll see the 'p=quarantine' which says that
mail with 'From: ' addresses claiming to be someone at harte-lyne.ca that
is not sent from their approved hosts should be quarantined.

> therefore, i suggest that it is problem that _you_need_to_correct_.
>
> because you are pulling emails from your server and if your email
> client is thunderbird, simply create a filter for James where the
> actions is;
>
>    Set Junk Status to   Not Junk

I'm not pulling emails from a server, I'm using gmail's web interface
because it is much more convenient to use from multiple systems.  And
even if I used imap to sync, I think it would already appear in the
spam folder.

>
> then you can stop loading this list with needless *junk* rants
> about *your* problem.

It's not my problem, it is what his domain says should be done with
mail claiming to be from there but isn't..  Your mail system may
simply ignore the request, but that doesn't mean it always will or
that it is the right thing to do.   And on a more practical note,
shouldn't be left as each recipient's problem.   And particularly
since it affects mail from yahoo.com and aol.com senders, the long
term fix will have to be in the list software (and already is, in the
current version).   Meanwhile, the workaround is to not send with a
From: address where the domain requests that it not be forwarded.

-- 
      Les Mikesell
         lesmikesell at gmail.com



More information about the CentOS mailing list