On 11 January 2018 at 03:24, li...@lazygranch.com wrote:
> On Wed, 10 Jan 2018 21:59:26 -0500
>> On 1/10/2018 9:53 PM, li...@lazygranch.com wrote:
> I help with a few people I know that set up their own email to pass
> SPF and DKIM, but realistically no major corporation is
On Wed, 10 Jan 2018 21:59:26 -0500
"Kevin A. McGrail" wrote:
> On 1/10/2018 9:53 PM, li...@lazygranch.com wrote:
> > RTFMing, I see that both opendkim and python-policyd-spf have
> > whitelisting capabilities (especially python-policyd-spf). But for
> > the most part, my
On January 11, 2018 2:53:10 AM UTC, "li...@lazygranch.com"
wrote:
>RTFMing, I see that both opendkim and python-policyd-spf have
>whitelisting capabilities (especially python-policyd-spf). But for the
>most part, my legitimate incoming email passes DKIM or SPF, but often
On 1/10/2018 9:53 PM, li...@lazygranch.com wrote:
RTFMing, I see that both opendkim and python-policyd-spf have
whitelisting capabilities (especially python-policyd-spf). But for the
most part, my legitimate incoming email passes DKIM or SPF, but often
not both. What I would like to do is accept
RTFMing, I see that both opendkim and python-policyd-spf have
whitelisting capabilities (especially python-policyd-spf). But for the
most part, my legitimate incoming email passes DKIM or SPF, but often
not both. What I would like to do is accept email that passes either
DKIM or SPF, but the