-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
json support #53
Comments
Hello. What exactly do you mean? |
When report is with .json.gz extension logging error
From: Aleksey Andreev ***@***.***>
Sent: Tuesday, February 14, 2023 6:34 PM
To: liuch/dmarc-srg ***@***.***>
Cc: shushulin76 ***@***.***>; Author ***@***.***>
Subject: Re: [liuch/dmarc-srg] json support (Issue #53)
Hello. What exactly do you mean?
—
Reply to this email directly, view it on GitHub <#53 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A54UHF4NSOA2HMLDEMKXZFTWXOXXBANCNFSM6AAAAAAU3YUSP4> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/A54UHFYMV3YOJNBRFL535Q3WXOXXBA5CNFSM6AAAAAAU3YUSP6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSVHSTAY.gif> Message ID: ***@***.*** ***@***.***> >
|
I have not come across such files as a report, and RFC 7489 does not mention this either. Could you give me a link to learn this? |
Oh. Do you mean SMTP TLS Reporting (RFC 8460)? |
Ou yes my mistake, because reports came in the same inbox excuse me.
Best Regards
From: Aleksey Andreev ***@***.***>
Sent: Tuesday, February 14, 2023 6:58 PM
To: liuch/dmarc-srg ***@***.***>
Cc: shushulin76 ***@***.***>; Author ***@***.***>
Subject: Re: [liuch/dmarc-srg] json support (Issue #53)
Oh. Did you mean SMTP TLS Reporting (RFC 8460)?
—
Reply to this email directly, view it on GitHub <#53 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A54UHF75XUTNVPLWAZT4G5LWXO2QHANCNFSM6AAAAAAU3YUSP4> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/A54UHFYXIHH46KJBI66QAFTWXO2QHA5CNFSM6AAAAAAU3YUSP6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSVHUVUI.gif> Message ID: ***@***.*** ***@***.***> >
|
I just receive this error but it is working
PHP Notice: Unknown: Kerberos error: No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_0) (try running kinit) for mail.domain.com (errflg=1) in Unknown on line 0
From: Aleksey Andreev ***@***.***>
Sent: Tuesday, February 14, 2023 6:58 PM
To: liuch/dmarc-srg ***@***.***>
Cc: shushulin76 ***@***.***>; Author ***@***.***>
Subject: Re: [liuch/dmarc-srg] json support (Issue #53)
Oh. Did you mean SMTP TLS Reporting (RFC 8460)?
—
Reply to this email directly, view it on GitHub <#53 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/A54UHF75XUTNVPLWAZT4G5LWXO2QHANCNFSM6AAAAAAU3YUSP4> .
You are receiving this because you authored the thread. <https://github.com/notifications/beacon/A54UHFYXIHH46KJBI66QAFTWXO2QHA5CNFSM6AAAAAAU3YUSP6WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSVHUVUI.gif> Message ID: ***@***.*** ***@***.***> >
|
What did you do when it happened? And where (in the Web UI or in the console)? |
When i run php script for import to database manually
…On Feb 14, 2023, 8:05 PM, at 8:05 PM, Aleksey Andreev ***@***.***> wrote:
What did you do when it happened? And where (in the Web UI or in the
console)?
--
Reply to this email directly or view it on GitHub:
#53 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
utils/fetch_reports.php This one? Thanks. |
Yes, and mail server is Microsoft exchange.
Thanks
Best Regards
…On Feb 14, 2023, 8:28 PM, at 8:28 PM, Aleksey Andreev ***@***.***> wrote:
utils/fetch_reports.php This one? Thanks.
--
Reply to this email directly or view it on GitHub:
#53 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
Can you provide example reports here ? |
That has been fixed. The details are here: #65 |
Is it possible to support .json files?
Best Regards
The text was updated successfully, but these errors were encountered: