Re: [dmarc-discuss] Use of in DMARC aggregate reports

2021-12-20 Thread Juri Haberland via dmarc-discuss
On 02.12.21 13:34, Maarten Oelering via dmarc-discuss wrote: > Hi list members, > > We see many aggregate reports where is a subdomain > which does not publish a DMARC record. The DMARC record is on the > organisation domain. > It’s so widespread it looks like some DMARC reporting software is

Re: [dmarc-discuss] newbie question about Source-IP

2019-03-02 Thread Juri Haberland via dmarc-discuss
On 01/03/2019 03:09, Roland Turner via dmarc-discuss wrote: > You've posted to dmarc-discuss, a list for discussion of the DMARC > protocol and broad interoperability issues, however your question > relates to the OpenDMARC implementation of DMARC. You're looking for the > OpenDMARC forum

Re: [dmarc-discuss] Aggregate report 'loop'

2018-10-09 Thread Juri Haberland via dmarc-discuss
On 09/10/18 12:00, Paul Smith via dmarc-discuss wrote: [...] > Several days ago, we received a marketing email from 'johnlewis.co.uk'. > Our server dutifully sent a DMARC aggregate report back to them as their > 'rua' record says. > > Then, the next day, we get an aggregate report back from

Re: [dmarc-discuss] my agg. reports

2018-04-19 Thread Juri Haberland via dmarc-discuss
On 19.04.2018 18:38, A. Schulze via dmarc-discuss wrote: > Am 19.04.2018 um 08:30 schrieb Juri Haberland via dmarc-discuss: >> [btw. the SPF result seems wrong: "none" instead of "pass" for a mail from >> the opendmarc-users ML] > > RFC5321.MailFrom f

Re: [dmarc-discuss] my agg. reports

2018-04-19 Thread Juri Haberland via dmarc-discuss
On 19.04.2018 12:32, Alessandro Vesely via dmarc-discuss wrote: > On Thu 19/Apr/2018 08:30:04 +0200 Juri Haberland via dmarc-discuss wrote: >> This is what I found: >> - wrong MIME type: expected: text/xml (.xml); found: application/xml (.xml) > I found text/xml as required Ri

Re: [dmarc-discuss] my agg. reports

2018-04-19 Thread Juri Haberland via dmarc-discuss
On 2018-04-19 07:55, A. Schulze via dmarc-discuss wrote: Hello @all, Hello Andreas, since some days aggregated reports we generate using an other software: rspamd These reports are invisible at dmarcian.com. I would like to ask the group to review my reports if they are syntactical valid.

Re: [dmarc-discuss] OOF failed DMARC verification by linkedin

2017-06-05 Thread Juri Haberland via dmarc-discuss
On 05.06.2017 05:09, Yeo via dmarc-discuss wrote: > Hi all, > > We just recently enabled DMARC for our outgoing mails. We noticed our out of > office (OOF) messages to internet so far ok e.g gmail.com. > But when OOF messages send to linkedin.com we will get DMARC verification > failed due to

Re: [dmarc-discuss] I Need help to get everything to 100% - Microsoft and dmarctest.org fails

2017-04-24 Thread Juri Haberland via dmarc-discuss
Marko Nix via dmarc-discuss wrote: > I am running a CentOS server, with configured Postfix / Dovecot setup. What DMARC software do you use? I assume it is OpenDMARC - if so, the opendmarc-users ML might be better suited than this generic DMARC mailing list. > My other problem is that every

Re: [dmarc-discuss] New to DMARC need help

2017-03-22 Thread Juri Haberland via dmarc-discuss
On 22.03.2017 13:49, Don Buchanan via dmarc-discuss wrote: > Trying to implement a DMARC record for reporting purposes to start. I had a > simple TXT record put in place, but I am not getting reports, and believe the > record is not working as a DMARC record. > for mail domain :

Re: [dmarc-discuss] opendkim-atpszone reproducibility and examples

2017-02-01 Thread Juri Haberland via dmarc-discuss
SheridanJ West via dmarc-discuss wrote: > I only have the mismatch problem with opendmarc-reports and thats using > most of the command line options. > > Normal email (port 587) is matched with spf,dkim and dmarc.Please do > not consider our email servers as mentally retarded in regard to

Re: [dmarc-discuss] opendkim-atpszone reproducibility and examples

2017-02-01 Thread Juri Haberland via dmarc-discuss
SheridanJ West via dmarc-discuss wrote: > i appear to need atps records for google this is with atps dns text records > and probably others > > opendmarc-reports: sent report for gmail.com to mailauth-repo...@google.com > (2.0.0 Ok: queued as x1) > > without atps [results i got from last week] > >

Re: [dmarc-discuss] opendkim-atpszone reproducibility and examples

2017-01-31 Thread Juri Haberland via dmarc-discuss
SheridanJ West via dmarc-discuss wrote: > I encountered a opendmarc bug that required adsp records as well to send > dmarc reports and i had a fun time trying to reproduce the output for i do > not know how long the url i mention will last. > Is nearly the same but I am confused - is the web

Re: [dmarc-discuss] DMARC forensic reporting options

2016-12-23 Thread Juri Haberland via dmarc-discuss
On 23.12.2016 17:10, John Comfort via dmarc-discuss wrote: > I would be perfectly fine with limiting the information if people are > really that paranoid about header information. For example: date, > receiving server information, originating smtp server sender, and subject > line. This would

Re: [dmarc-discuss] FBL via DMARC?

2016-11-30 Thread Juri Haberland via dmarc-discuss
On 29.11.2016 19:06, John Levine via dmarc-discuss wrote: > But see https://datatracker.ietf.org/doc/draft-levine-herkula-oneclick/ > > This is likely to be an RFC soon, and is apparently already > implemented at some large webmail providers. You can put a new header > in your message which

Re: [dmarc-discuss] mkdb.mysql or schema.mysql?

2016-10-26 Thread Juri Haberland via dmarc-discuss
On 26.10.2016 21:29, Niklaas Baudet von Gersdorff via dmarc-discuss wrote: > OpenDMARC, as distributed by FreeBSD, comes with two files for > creating a database for reporting: mkdb.mysql and schema.mysql. > Which one should I use? > > I think about using the former because it seems to be newer >

Re: [dmarc-discuss] Beware of the size limit in DMARC URIs

2016-10-14 Thread Juri Haberland via dmarc-discuss
On 2016-10-13 20:06, Matt Simerson via dmarc-discuss wrote: This thread has been hijacked by the lack of reading comprehension. Nobody (in this thread) has complained of DMARC reports being too large. Right. The problem in this thread is an issue with some DMARC report senders failing to

Re: [dmarc-discuss] Beware of the size limit in DMARC URIs

2016-10-14 Thread Juri Haberland via dmarc-discuss
On 2016-10-14 00:26, Brandon Long wrote: Actually, from the code, I'm surprised we handle a single address with ! correctly. I'll file a bug. Thanks, Brandon! Juri ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org

Re: [dmarc-discuss] Beware of the size limit in DMARC URIs

2016-10-12 Thread Juri Haberland via dmarc-discuss
On 12.10.2016 12:17, Steven M Jones via dmarc-discuss wrote: > On 10/12/16 01:32, Juri Haberland via dmarc-discuss wrote: >> Btw: Did anyone notice that AOL sends DMARC reports with two To: headers? > > Looking at the last few reports I received from them for this domain, I >

Re: [dmarc-discuss] Beware of the size limit in DMARC URIs

2016-10-12 Thread Juri Haberland via dmarc-discuss
Haberland via dmarc-discuss wrote: Hi, while writing a patch for OpenDMARC, I stumbled accross problems with the size limit in DMARC URIs that some of the big players have. Microsoft cannot cope at all with an URI like "rep...@example.org!10m" - you won't receive a single repo

Re: [dmarc-discuss] dmarc.org breaks dkim & dmarc

2016-10-04 Thread Juri Haberland via dmarc-discuss
On 04.10.2016 20:27, Benny Pedersen via dmarc-discuss wrote: > what will happend if opendmarc skips last signer if multiple signed ?, > imho opendmarc should really be more dnssec strict, and make all dkim > keys pass before it does dmarc pass, my msgs do pass on dmarc.org > mailserveres, but

Re: [dmarc-discuss] dmarc fail for linkedin

2016-10-04 Thread Juri Haberland via dmarc-discuss
On 04.10.2016 17:35, DurgaPrasad - DatasoftComnet via dmarc-discuss wrote: > I have done a stock dmarc implementation on centos 7. > > We use MailScanner and spamassassin with decent success since many years. I > would prefer a milter anyday so that I can influence my scores. > > My concerns