Bugzilla

(In reply to bgz from comment #14)
> I sent you the full IMAP log as an email attachment. 
> I can see Thunderbird announcing it's version number but no version information coming back.

>@gene smith were you able to decipher this from @bgz 's log?

I can't find the imap log sent via email from reporter bgz. I did find a message dated 2019-03-02 from bgz but it was empty. Anyhow, not sure how helpful the imap log would be anyhow.  bgz, if you still have the imap log you sent, it is probably better to just attach it using the link above on this bugzilla page.

I did work on this some back in late Feb and early March but other thing came up and haven't gotten back to it. I will mark this as "need info" from myself as a reminder.  I do have the sample emails from bgz that have the problem.

I suspect that the problem is due to email lines not ending in the required /r/n. However, tb should probably be more tolerant of malformed emails when trying to send/forward them.

(In reply to bgz from comment #14)
> I sent you the full IMAP log as an email attachment. 
> I can see Thunderbird announcing it's version number but no version information coming back.

>@gene smith were you able to decipher this from @bgz 's log?

I can't find the imap log sent via email from reporter bgz. I did find a message dated 2019-03-02 from bgz but it was empty (edit the next day: now see it, must have been a network problem.). Anyhow, not sure how helpful the imap log would be anyhow.  bgz, if you still have the imap log you sent, it is probably better to just attach it using the link above on this bugzilla page.

I did work on this some back in late Feb and early March but other thing came up and haven't gotten back to it. I will mark this as "need info" from myself as a reminder.  I do have the sample emails from bgz that have the problem.

I suspect that the problem is due to email lines not ending in the required /r/n. However, tb should probably be more tolerant of malformed emails when trying to send/forward them.