Search the Community
Showing results for tags 'header'.
Found 2 results
I have attempted to purchase Fuel but am unable to do so as https://payments.verisign.com/payflowlinkis reporting an expired certificate and I am unwilling to continue with the transaction while the cert is in this state. I wondered if you were aware of the issue. I appreciate this is probably not a Spamcop issue directly as these servers (or domain at least) belong to Verisign but hope, as you have a relationship with them, that you are well placed to bring this to their attention. Many Thanks
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/220.127.116.11-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.