Date parsing error

[saxx]

I stumble over this exception a few times a day:

System.ArgumentException: Could not parse date: The added or subtracted value results in an un-representable DateTime.
Parameter name: value. Input was: "from 213.30.242.172:51773 by cmpweb05.aul.t-online.de with HTTP/1.1" ---> System.ArgumentOutOfRangeException: The added or subtracted value results in an un-representable DateTime.
Parameter name: value
   at System.DateTime.AddTicks(Int64 value)
   at OpenPop.Mime.Decode.Rfc2822DateTime.AdjustTimezone(DateTime dateTime, String dateInput)
   at OpenPop.Mime.Decode.Rfc2822DateTime.StringToDate(String inputDate)
   --- End of inner exception stack trace ---
   at OpenPop.Mime.Decode.Rfc2822DateTime.StringToDate(String inputDate)
   at OpenPop.Mime.Header.Received..ctor(String headerValue)
   at OpenPop.Mime.Header.MessageHeader.ParseHeader(String headerName, String headerValue)
   at OpenPop.Mime.Header.MessageHeader.ParseHeaders(NameValueCollection headers)
   at OpenPop.Mime.Message..ctor(Byte[] rawMessageContent, Boolean parseBody)
[... my stuff ...]

I'm not entirely sure, but I think most of the time it's because of some t-online.de e-mail, so I guess they use some kind of corrupted header format? It's always a similar exception, with an IP-address where the date should be.

Is there anything that can be done on the side of OpenPOP or do I have to continue ignoring these corrupted e-mails? Thanks!

[foens]

You can look into the raw email source and see if you can spot a problem, or you could paste the relevant header section here for us to inspect. We need more context in this case, since it seems to parse a wrong header.

[saxx]

Thanks a lot for your reply - sorry I haven't figured that out myself.

It will take me a few days to add the necessary error-catching logic to our product, but I will get back to you as soon as I can.

[saxx]

It took me a while until I realized that the problem only happens on a certain client installation of our product. Unfortunately one where I don't have access to the mail inbox or the raw mail.

I implemented a much better error routine to get more details about the mails in question. Unfortunately it will take a few months until the client will update to this new, improved version. So for now there's nothing I can do to deliver more information.

I will close that issue for now and will open a new one as soon as I have more details - sorry for the inconvenience.

[foens]

Fair enough. Thanks for looking into the issue 👍