Jeffrey Stedfast

The way that [MimeKit](https://github.com/jstedfast/MimeKit) handles this is to: 1. avoid the use of int.Parse() and instead use int.TryParse(): https://github.com/jstedfast/MimeKit/blob/master/MimeKit/Utils/CharsetUtils.cs#L218 2. if that fails (in this case, it would), then it...

The correct Content-Type should be `application/x-gzip`, but I guess whatever software comcast is using is broken. The way that [MailKit](https://github.com/jstedfast/MailKit) (my own mail library) handles this is that it treats...

The only way to truly solve issues like this is to write a parser that doesn't require the message data to be converted into a unicode string first. In other...

Looks like you guys seriously need to use [MimeKit](https://github.com/jstedfast/MimeKit) to solve this problem.

The only way you'll ever get your address parser to work reliably is if you switch to using a tokenizer. String.Split() and IndexOf() approaches will only become completely unmaintainable and...

Not all MIME parts are guaranteed to have a Content-Disposition header. MIME parts don't even necessarily need to have _any_ headers at all. This is all explained in the rfcs...

According to the IMAP specification, every command may have any number of untagged responses (i.e. lines beginning with "*"). It's not just the APPEND command that needs to support this,...

The proper way to format this command: command ="xm008 UID STORE 126 127 128 FLAGS.SILENT (\Seen)" is like this: command ="xm008 UID STORE 126-128 FLAGS.SILENT (\Seen)"

IMAP uses a modified UTF-7 charset encoding for international mailbox names (i.e. anything outside of the US-ASCII range).

It's perfectly valid for messages to have duplicate headers, especially for headers such as "Received:", "To:", and "Cc:". I would highly recommend replacing the MIME parser in AENetMail with [MimeKit](https://github.com/jstedfast/MimeKit)...