On Feb 9, 2017 01:36, "Roland Turner via dmarc-discuss" <
dmarc-discuss@dmarc.org> wrote:
On 02/08/2017 10:45 PM, John Levine via dmarc-discuss wrote (after Jim
Popovitch wrote):
They have an obligation, to everyone, to get it right, irregardless of
>> sender preferences.
>>
> I have to say that
On Wed, Feb 8, 2017 at 5:01 AM, Sistemisti Posta via dmarc-discuss
wrote:
> Hello,
>
> how do you manage DMARC in multidomain environment?
>
> Renew the DKIM keys, deal with all DNS record... is not easy.
You could always use CNAMEs back to a few rotated keys.
-Jim P.
On Fri, Feb 3, 2017 at 1:50 AM, Roland Turner via dmarc-discuss
wrote:
> Jim Popovitch wrote:
>
>
>>> You should definitely disregard reports that aren't useful to you.
>>
>> I'd actually prefer to work with the sender in order to fully
>> understand the differences
On Thu, Feb 2, 2017 at 1:58 AM, Roland Turner via dmarc-discuss
wrote:
> Jim Popovitch wrote:
>
>
>> The difficulty I have is exactly as you described. I received a
>> DMARC report that says there is a DKIM failure, but what is not clear
>> is whether or not the email
On Wed, Feb 1, 2017 at 5:31 PM, A. Schulze via dmarc-discuss
<dmarc-discuss@dmarc.org> wrote:
>
>
> Am 01.02.2017 um 15:11 schrieb Jim Popovitch via dmarc-discuss:
>> I'm running postfix and AFAIK it's only sending 7bit.
>>
>> postfix postscreen
>>
On Wed, Feb 1, 2017 at 6:50 AM, A. Schulze via dmarc-discuss
<dmarc-discuss@dmarc.org> wrote:
>
> Jim Popovitch via dmarc-discuss:
>
>> I'd bet a few beers that the DKIM failures are due to those companies
>> injecting inbound msg headers before processing DMARC ch
On Tue, Jan 31, 2017 at 11:14 PM, Roland Turner via dmarc-discuss
wrote:
> Jim Popovitch wrote:
>
>
>> I rolled out additional DMARC support for Mailman (outbound alignment)
>> recently, and to be honest I'm not yet convinced that all receivers
>> have a clue when
On Tue, Jan 31, 2017 at 5:24 PM, Peter Gonzalez via dmarc-discuss
wrote:
> On 2017 Jan 31, 05:59, Jim Popovitch wrote:
>> On Sat, Jan 28, 2017 at 1:49 AM, Dave Warren wrote:
>> > On Fri, Jan 27, 2017, at 04:23, Jim Popovitch wrote:
>> >
>> >> But what can you do about it?
On Sat, Jan 28, 2017 at 1:49 AM, Dave Warren via dmarc-discuss
<dmarc-discuss@dmarc.org> wrote:
> On Fri, Jan 27, 2017, at 04:23, Jim Popovitch via dmarc-discuss wrote:
>> On Thu, Jan 26, 2017 at 11:13 PM, John Levine via dmarc-discuss
>> <dmarc-discuss@dmarc.org> wrote
On Thu, Jan 26, 2017 at 10:33 PM, Roland Turner via dmarc-discuss
wrote:
> Bear in mind that all reporting is at the good graces of receivers; the
> options to fine-tune what is sent may, or may not, actually be implemented by
> any given receiver.
Great point. I do
On Thu, Jan 26, 2017 at 5:50 PM, John Levine wrote:
> In article
> you
> write:
>>Hello,
>>
>>I'm trying to limit RUA/RUFs to legitimate emails that need eyeballs.
>>
>>To that end, I'm scratching my head as
On Thu, Jan 5, 2017 at 10:05 PM, Steven M Jones <s...@crash.com> wrote:
> On 01/05/2017 17:32, Jim Popovitch via dmarc-discuss wrote:
>> I've been trying, albeit slowly, to determine why I haven't seen any
>> RUF reports since Sept 2016.
>>
>> Shouldn't this RUA re
Hello,
I've been trying, albeit slowly, to determine why I haven't seen any
RUF reports since Sept 2016.
Shouldn't this RUA report also produce a corresponding RUF?
http://domainmail.org/dmarc-reports/126.com%21inug.org%211483574400%211483660799.xml
-Jim P.
13 matches
Mail list logo