-
Notifications
You must be signed in to change notification settings - Fork 65
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
Problem parsing google abuse reports #235
Comments
perhaps some kind of information like error logs might help. for me it works fine |
Error seems to be as follows in framework.log:
Which appears to refer to the following in Google.php: $xml = simplexml_load_string($this->parsedMail->getMessageBody()); Which is strange? |
Made it a bit more readable
|
I am setting this to a duplicate of #217 Its not a problem in the parser, but within the handler's core. Can you confirm you are using a non english type system or email body? |
All the failed emails are English on UK English systems, I'll get an example of the failed emails up with all the IPs/URLs changed (unless they're non-english characters): |
|
I checked for non-ascii characters using vim as well :set hlsearch
/[^\x00-\x7F]
Pattern not found: [^\x00-\x7F] |
right, you have the human readable version of the google report. You must use the XML type reporting, that will work a lot better ;) |
Have a look at the sample dir, it hold the google sample too: Thats the format you need, its a XML setting the de SBR in the portal |
Aaaaaah, I see, it's blindingly obvious now hahaha. Thank you so much for your help Bart! |
It should not stack trace like that we nee to groacefully exit it |
validation added in version 1.3.8 |
https://github.com/AbuseIO/parser-google
Hi everyone,
Just wondering if anyone else has the same problem as I do, constant failing google abuse reports (SBR) failing to be parsed.
I'm doing some troubleshooting now but I think there may be a few possible source:
If anyone's experienced this previously or has any ideas I'd love some input!
Dank je 😄
The text was updated successfully, but these errors were encountered: