This is a frustrating one. I _did_ manage to trigger this morning, using more or less the steps in Comment #7. I couldn't get it to happen by delivering just a single matching message - I had to get a few messages onto the server for pop3 pickup, a mix of matching and non-matching ones. But I definitely saw screwed-up messages - looking at the raw message data on disk, they were blank except for the extra POP3 headers (`X-Account-Key:` and `X-UIDL:`) and `X-Mozilla-`* headers that get added. This was on Linux, using a tame local pop3 server, and I'm _pretty_ sure (like 90% sure) I managed to get it to happen when running on mbox too... Then I went to dig into it deeper this afternoon, and for the life of me I couldn't get it to happen again! Doing those same steps over and over, but no dice. It just kept working and was utterly frustrating. I'll try again with a remote POP3 server (timing could potentially be an issue) and failing that I'll try and dig up a windows setup to try out (although I don't see anything in the symptoms or the code which screams "platform-specific" to me). I'd like to find out: 1. does this also happen with mbox? (@EarlGreyTea - have you tried the same steps on mbox?) 2. does it only happen on windows? Wayne: are there some people you could ask to run through the steps in Comment #7 (on any platform, and on both mbox and maildir)? It'd be nice to get some more people to try it out.
Bug 1767190 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This is a frustrating one. I _did_ manage to trigger this morning, using more or less the steps in Comment #7. I couldn't get it to happen by delivering just a single matching message - I had to get a few messages onto the server for pop3 pickup, a mix of matching and non-matching ones. But I definitely saw screwed-up messages - looking at the raw message data on disk, they were blank except for the extra POP3 headers (`X-Account-Key:` and `X-UIDL:`) and `X-Mozilla-`* headers that get added. This was on Linux, using a tame local pop3 server, and I'm _pretty_ sure (like 90% sure) I managed to get it to happen when running on mbox too... Then I went to dig into it deeper this afternoon, and for the life of me I couldn't get it to happen again! Doing those same steps over and over, but no dice. It just kept working and was utterly frustrating. I'll try again with a remote POP3 server (timing could potentially be an issue) and failing that I'll try and dig up a windows setup to try out (although I don't see anything in the symptoms or the code which screams "platform-specific" to me). I'd like to find out: 1. does this also happen with mbox? (@EarlGreyTea - have you tried the same steps on mbox?) 2. does it only happen on windows? Wayne: are there some people you could ask to run through the steps in Comment #7 (on any platform, and on both mbox and maildir)? It'd be nice to get some more people to try and replicate this.