rvaessen posted a topic in Routing / Report Address IssuesI recently received (received on the 21st of Jan, 2015) a spam message from 'AOL' it was sent using an email app for iOS (WebMailUI). Reference the following header line: X-Mailer: JAS AolApp/22.214.171.124-Mac OS X (iPhone) The date reported in the first/origination header was "2015-Jan-21 06:55:27". When I attempted to report this spam via SpamCop, the following error was noted: "Can't parse date of spam for age detection: 2015-Jan-21 06:55:27" I edited the header to change the date so it read "21-Jan-2015", and SpamCop parsed the email appropriately. Ref my successful report: <https://www.spamcop.net/sc?id=z6047372922z1b4bbe7b5f3b2dedf8b5992521e89d89z>. Can the SpamCop admins modify the header parsing algorithms to allow this particular date string? YYYY-MMM-DD This is the second time I've received spam sent via AOL that uses this particular type of date format.
I see the same errors as of 1645MDT on the 9th of June, 2014. "500 Internal Server Error" and "An error occurred while processing this directive" I'm using Safari (Version 7.0.4 (9537.76.4)) on my iMac running Mac OS X (Version 10.9.3, Build 13D65). FYI: No problems noted this morning (appx 0315MDT, 9th of June, 2014).