Re: [dmarc-discuss] Need documents to achieve DMARC alignment

2020-09-25 Thread John Levine via dmarc-discuss
In article  
you write:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>On Thu, Sep 24, 2020 at 11:44 PM Blason R via dmarc-discuss <
>dmarc-discuss@dmarc.org> wrote:
>
>> Thanks that makes sense! Assuming they do not have a DKIM facility
>> aligning messages with SPF should suffice my need, right? ...

>My question to you is why, in 2020, you would use a 3rd party vendor that
>does not properly support DKIM signing and apparently doesn't understand
>how DMARC works? A knowledgeable vendor should be able to provide you with
>a 1 or 2 page PDF to guide you in how to best implement SPF/DKIM/DMARC.
>Just saying.

Mike is too polite to say that any mail provider that doesn't already
understand DKIM, SPF, and DMARC, has shown that it is astonishingly
unfamiliar with the way that mail works and is unlikely to be able to
provide adequate service.

R's,
John

___
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
http://www.dmarc.org/mailman/listinfo/dmarc-discuss

NOTE: Participating in this list means you agree to the DMARC Note Well terms 
(http://www.dmarc.org/note_well.html)


Re: [dmarc-discuss] Need documents to achieve DMARC alignment

2020-09-25 Thread Dotzero via dmarc-discuss
On Thu, Sep 24, 2020 at 11:44 PM Blason R via dmarc-discuss <
dmarc-discuss@dmarc.org> wrote:

> Thanks that makes sense! Assuming they do not have a DKIM facility
> aligning messages with SPF should suffice my need, right?
>

You will need to monitor the feedback reports to determine whether SPF
alone is sufficient for your needs. Only you can decide how much "breakage"
is acceptable to you. While mailing lists might not be a pain point for
your mail flow, other intermediaries (vanity accounts, forwarding from one
recipient account to other accounts of theirs, etc.) may be.

My question to you is why, in 2020, you would use a 3rd party vendor that
does not properly support DKIM signing and apparently doesn't understand
how DMARC works? A knowledgeable vendor should be able to provide you with
a 1 or 2 page PDF to guide you in how to best implement SPF/DKIM/DMARC.
Just saying.

Michael Hammer
___
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
http://www.dmarc.org/mailman/listinfo/dmarc-discuss

NOTE: Participating in this list means you agree to the DMARC Note Well terms 
(http://www.dmarc.org/note_well.html)

Re: [dmarc-discuss] Need documents to achieve DMARC alignment

2020-09-24 Thread Blason R via dmarc-discuss
Thanks that makes sense! Assuming they do not have a DKIM facility aligning
messages with SPF should suffice my need, right?

On Tue, Sep 22, 2020 at 8:04 PM Faisal Misle 
wrote:

> Hi there,
>
> You'd have to get the email partner to use a "custom return-path" (eg:
> bounces.example.com). That way you achieve SPF alignment. For DKIM
> alignment, the key has to be signed with your domain, not theirs.
>
> Postmark has a great article on it here:
> https://postmarkapp.com/blog/how-dmarc-and-a-custom-return-path-work-together
>
> Hope this helps!
>
> *Faisal Misle*
> Customer Success Engineer | Red Sift
>
>
> On Mon, Sep 21, 2020 at 11:15 PM Blason R via dmarc-discuss <
> dmarc-discuss@dmarc.org> wrote:
>
>> Hi Team,
>>
>> I have domain example.com and have proper spf, dkim set for the mail's
>> going out. However my other email partner will soon sending mails on behalf
>> of example.com assuming emailpartner.com they even have SPF and dkim
>> facility available.
>>
>> Can someone pls guide me or documents to achieve dmarc alignment in this
>> case when the mail's go out from emailpartner.com
>> ___
>> dmarc-discuss mailing list
>> dmarc-discuss@dmarc.org
>> http://www.dmarc.org/mailman/listinfo/dmarc-discuss
>>
>> NOTE: Participating in this list means you agree to the DMARC Note Well
>> terms (http://www.dmarc.org/note_well.html)
>
>
> Red Sift is the power behind OnDMARC and OnINBOX.
>
> You can find us at 21A Noel Street, 4th Floor, London, W1F 8GR.
>
>
> Red Sift is a limited company registered in England and Wales. Registered
> number: 09240956. Registered office: Kemp House, 152 City Road, London,
> EC1V 2NX.
>
___
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
http://www.dmarc.org/mailman/listinfo/dmarc-discuss

NOTE: Participating in this list means you agree to the DMARC Note Well terms 
(http://www.dmarc.org/note_well.html)

Re: [dmarc-discuss] Need documents to achieve DMARC alignment

2020-09-22 Thread Faisal Misle via dmarc-discuss
Hi there,

You'd have to get the email partner to use a "custom return-path" (eg:
bounces.example.com). That way you achieve SPF alignment. For DKIM
alignment, the key has to be signed with your domain, not theirs.

Postmark has a great article on it here:
https://postmarkapp.com/blog/how-dmarc-and-a-custom-return-path-work-together

Hope this helps!

*Faisal Misle*
Customer Success Engineer | Red Sift


On Mon, Sep 21, 2020 at 11:15 PM Blason R via dmarc-discuss <
dmarc-discuss@dmarc.org> wrote:

> Hi Team,
>
> I have domain example.com and have proper spf, dkim set for the mail's
> going out. However my other email partner will soon sending mails on behalf
> of example.com assuming emailpartner.com they even have SPF and dkim
> facility available.
>
> Can someone pls guide me or documents to achieve dmarc alignment in this
> case when the mail's go out from emailpartner.com
> ___
> dmarc-discuss mailing list
> dmarc-discuss@dmarc.org
> http://www.dmarc.org/mailman/listinfo/dmarc-discuss
>
> NOTE: Participating in this list means you agree to the DMARC Note Well
> terms (http://www.dmarc.org/note_well.html)

-- 


Red Sift is the power behind OnDMARC and OnINBOX.

You can find us at 21A 
Noel Street, 4th Floor, London, W1F 8GR.




Red Sift is a limited company 
registered in England and Wales. Registered number: 09240956. Registered 
office: Kemp House, 152 City Road, London, EC1V 2NX.

___
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
http://www.dmarc.org/mailman/listinfo/dmarc-discuss

NOTE: Participating in this list means you agree to the DMARC Note Well terms 
(http://www.dmarc.org/note_well.html)