Re: [MlMt] IMAP Problem for Account
Ok, I am a bit further now... I re-added the account direct access to exchange IMAP/s. Now it works, so it might be related to DavMail. Although I am not sure, how... hope it is fixed now. On 7 Dec 2023, at 22:29, Stephan Bösebeck wrote: > I was too early with my assumption. It is not working, just got the same > Error Message for the Drafts- and the Sent-Folder. When looking at it, one > message seems to be added 100s of times, until Mailmate detects its error. > > Any Ideas what might have caused this? Exchange is a bitch, yes, but I doubt > that it is just now coming out of nowhere... > > > > On 7 Dec 2023, at 21:03, Stephan Bösebeck wrote: > >> Thanks a lot for the detailed answer. >> >> But after gotting completely rid of the account and re-adding it, the error >> now is gone. My guess is that was something local with MailMate. >> >> The server related is an Exchange server but I access it via `DavMail` - >> which works astonishingly good. >> >> But I had issues with that account, when I wanted to test accessing the >> imap-port of the exchange directly. I added a _new_ account, different name, >> but same email. That made MailMate freak out a bit. It mixed up those >> accounts, although I disabled one. I deleted the direct Imap access and >> everything went back to normal. This might have caused the strange behaviour >> (although this is months ago). (btw: the direct imap access never worked, >> the firewall was prohibiting it). >> >> Right now, it works... Thanks for your help. >> >> >> >> >> >> On 7 Dec 2023, at 19:22, Bill Cole wrote: >> >>> On 2023-12-07 at 11:36:07 UTC-0500 (Thu, 07 Dec 2023 17:36:07 +0100) >>> Stephan Bösebeck >>> is rumored to have said: >>> Then, after staring MailMate again, it was downloading everything and it was _then_ fine... Until I sent an email. I got the UIDVALIDITY-Message more or less directly after sending. >>> >>> That is a clue that it probably was specifically and solely related to your >>> "Sent" IMAP folder at that point. >>> >>> The UIDVALIDITY value is an integer set by the IMAP server for each IMAP >>> folder and included in the server response to an IMAP client selecting a >>> folder. It is changed only when there is a change in mapping of messages to >>> UID values, which are unique and notionally permanent ID numbers for each >>> message for as long as it is in the folder. That can be made necessary by >>> catastrophic server failure and restoration from backup or by anything >>> mimicking such an event, e.g. serious sysadmin error, total re-indexing of >>> mailboxes, etc. If it happens to an account, it will likely strike every >>> folder in an account (and possibly every account on a server) at the same >>> time, and MailMate may alert for each folder as it is selected for routine >>> sync. It should absolutely NOT be a frequent event, because it forces a >>> full resync of all message data and metadata in the folder. >>> >>> One thing that could cause an apparent single-folder UIDVALIDITY change is >>> if one were to delete and re-create an IMAP folder of the same name with >>> one IMAP client, while other IMAP clients are offline. Hence, it is >>> *possible* for such a change to indicate account compromise and an attempt >>> to obfuscate the apparent history of a mail folder. >>> I removed the account in total again, this time it worked... so I try to add it once more... I will see, if that helps. >>> >>> If it recurs, particularly for multiple IMAP folders on that account, it >>> would most likely be a recurrent problem with your IMAP server. If it >>> recurs for just one folder, you may have a quiet account hijacking in >>> progress. It is extremely unlikely that MailMate could have a client-side >>> issue with tracking UIDVALIDITY at this point in its history, as it is >>> logically quite simple to do correctly. >>> >>> -- >>> Bill Cole >>> b...@scconsult.com or billc...@apache.org >>> (AKA @grumpybozo and many *@billmail.scconsult.com addresses) >>> Not Currently Available For Hire >>> ___ >>> mailmate mailing list >>> mailmate@lists.freron.com >>> https://lists.freron.com/listinfo/mailmate___ >> mailmate mailing list >> mailmate@lists.freron.com >> https://lists.freron.com/listinfo/mailmate___ > mailmate mailing list > mailmate@lists.freron.com > https://lists.freron.com/listinfo/mailmate signature.asc Description: OpenPGP digital signature ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] IMAP Problem for Account
I was too early with my assumption. It is not working, just got the same Error Message for the Drafts- and the Sent-Folder. When looking at it, one message seems to be added 100s of times, until Mailmate detects its error. Any Ideas what might have caused this? Exchange is a bitch, yes, but I doubt that it is just now coming out of nowhere... On 7 Dec 2023, at 21:03, Stephan Bösebeck wrote: > Thanks a lot for the detailed answer. > > But after gotting completely rid of the account and re-adding it, the error > now is gone. My guess is that was something local with MailMate. > > The server related is an Exchange server but I access it via `DavMail` - > which works astonishingly good. > > But I had issues with that account, when I wanted to test accessing the > imap-port of the exchange directly. I added a _new_ account, different name, > but same email. That made MailMate freak out a bit. It mixed up those > accounts, although I disabled one. I deleted the direct Imap access and > everything went back to normal. This might have caused the strange behaviour > (although this is months ago). (btw: the direct imap access never worked, the > firewall was prohibiting it). > > Right now, it works... Thanks for your help. > > > > > > On 7 Dec 2023, at 19:22, Bill Cole wrote: > >> On 2023-12-07 at 11:36:07 UTC-0500 (Thu, 07 Dec 2023 17:36:07 +0100) >> Stephan Bösebeck >> is rumored to have said: >> >>> Then, after staring MailMate again, it was downloading everything and it >>> was _then_ fine... >>> >>> Until I sent an email. I got the UIDVALIDITY-Message more or less directly >>> after sending. >> >> That is a clue that it probably was specifically and solely related to your >> "Sent" IMAP folder at that point. >> >> The UIDVALIDITY value is an integer set by the IMAP server for each IMAP >> folder and included in the server response to an IMAP client selecting a >> folder. It is changed only when there is a change in mapping of messages to >> UID values, which are unique and notionally permanent ID numbers for each >> message for as long as it is in the folder. That can be made necessary by >> catastrophic server failure and restoration from backup or by anything >> mimicking such an event, e.g. serious sysadmin error, total re-indexing of >> mailboxes, etc. If it happens to an account, it will likely strike every >> folder in an account (and possibly every account on a server) at the same >> time, and MailMate may alert for each folder as it is selected for routine >> sync. It should absolutely NOT be a frequent event, because it forces a full >> resync of all message data and metadata in the folder. >> >> One thing that could cause an apparent single-folder UIDVALIDITY change is >> if one were to delete and re-create an IMAP folder of the same name with one >> IMAP client, while other IMAP clients are offline. Hence, it is *possible* >> for such a change to indicate account compromise and an attempt to obfuscate >> the apparent history of a mail folder. >> >>> I removed the account in total again, this time it worked... so I try to >>> add it once more... >>> >>> I will see, if that helps. >> >> If it recurs, particularly for multiple IMAP folders on that account, it >> would most likely be a recurrent problem with your IMAP server. If it >> recurs for just one folder, you may have a quiet account hijacking in >> progress. It is extremely unlikely that MailMate could have a client-side >> issue with tracking UIDVALIDITY at this point in its history, as it is >> logically quite simple to do correctly. >> >> -- >> Bill Cole >> b...@scconsult.com or billc...@apache.org >> (AKA @grumpybozo and many *@billmail.scconsult.com addresses) >> Not Currently Available For Hire >> ___ >> mailmate mailing list >> mailmate@lists.freron.com >> https://lists.freron.com/listinfo/mailmate___ > mailmate mailing list > mailmate@lists.freron.com > https://lists.freron.com/listinfo/mailmate signature.asc Description: OpenPGP digital signature ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] IMAP Problem for Account
Thanks a lot for the detailed answer. But after gotting completely rid of the account and re-adding it, the error now is gone. My guess is that was something local with MailMate. The server related is an Exchange server but I access it via `DavMail` - which works astonishingly good. But I had issues with that account, when I wanted to test accessing the imap-port of the exchange directly. I added a _new_ account, different name, but same email. That made MailMate freak out a bit. It mixed up those accounts, although I disabled one. I deleted the direct Imap access and everything went back to normal. This might have caused the strange behaviour (although this is months ago). (btw: the direct imap access never worked, the firewall was prohibiting it). Right now, it works... Thanks for your help. On 7 Dec 2023, at 19:22, Bill Cole wrote: > On 2023-12-07 at 11:36:07 UTC-0500 (Thu, 07 Dec 2023 17:36:07 +0100) > Stephan Bösebeck > is rumored to have said: > >> Then, after staring MailMate again, it was downloading everything and it was >> _then_ fine... >> >> Until I sent an email. I got the UIDVALIDITY-Message more or less directly >> after sending. > > That is a clue that it probably was specifically and solely related to your > "Sent" IMAP folder at that point. > > The UIDVALIDITY value is an integer set by the IMAP server for each IMAP > folder and included in the server response to an IMAP client selecting a > folder. It is changed only when there is a change in mapping of messages to > UID values, which are unique and notionally permanent ID numbers for each > message for as long as it is in the folder. That can be made necessary by > catastrophic server failure and restoration from backup or by anything > mimicking such an event, e.g. serious sysadmin error, total re-indexing of > mailboxes, etc. If it happens to an account, it will likely strike every > folder in an account (and possibly every account on a server) at the same > time, and MailMate may alert for each folder as it is selected for routine > sync. It should absolutely NOT be a frequent event, because it forces a full > resync of all message data and metadata in the folder. > > One thing that could cause an apparent single-folder UIDVALIDITY change is if > one were to delete and re-create an IMAP folder of the same name with one > IMAP client, while other IMAP clients are offline. Hence, it is *possible* > for such a change to indicate account compromise and an attempt to obfuscate > the apparent history of a mail folder. > >> I removed the account in total again, this time it worked... so I try to add >> it once more... >> >> I will see, if that helps. > > If it recurs, particularly for multiple IMAP folders on that account, it > would most likely be a recurrent problem with your IMAP server. If it recurs > for just one folder, you may have a quiet account hijacking in progress. It > is extremely unlikely that MailMate could have a client-side issue with > tracking UIDVALIDITY at this point in its history, as it is logically quite > simple to do correctly. > > -- > Bill Cole > b...@scconsult.com or billc...@apache.org > (AKA @grumpybozo and many *@billmail.scconsult.com addresses) > Not Currently Available For Hire > ___ > mailmate mailing list > mailmate@lists.freron.com > https://lists.freron.com/listinfo/mailmate signature.asc Description: OpenPGP digital signature ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] IMAP Problem for Account
On 2023-12-07 at 11:36:07 UTC-0500 (Thu, 07 Dec 2023 17:36:07 +0100) Stephan Bösebeck is rumored to have said: Then, after staring MailMate again, it was downloading everything and it was _then_ fine... Until I sent an email. I got the UIDVALIDITY-Message more or less directly after sending. That is a clue that it probably was specifically and solely related to your "Sent" IMAP folder at that point. The UIDVALIDITY value is an integer set by the IMAP server for each IMAP folder and included in the server response to an IMAP client selecting a folder. It is changed only when there is a change in mapping of messages to UID values, which are unique and notionally permanent ID numbers for each message for as long as it is in the folder. That can be made necessary by catastrophic server failure and restoration from backup or by anything mimicking such an event, e.g. serious sysadmin error, total re-indexing of mailboxes, etc. If it happens to an account, it will likely strike every folder in an account (and possibly every account on a server) at the same time, and MailMate may alert for each folder as it is selected for routine sync. It should absolutely NOT be a frequent event, because it forces a full resync of all message data and metadata in the folder. One thing that could cause an apparent single-folder UIDVALIDITY change is if one were to delete and re-create an IMAP folder of the same name with one IMAP client, while other IMAP clients are offline. Hence, it is *possible* for such a change to indicate account compromise and an attempt to obfuscate the apparent history of a mail folder. I removed the account in total again, this time it worked... so I try to add it once more... I will see, if that helps. If it recurs, particularly for multiple IMAP folders on that account, it would most likely be a recurrent problem with your IMAP server. If it recurs for just one folder, you may have a quiet account hijacking in progress. It is extremely unlikely that MailMate could have a client-side issue with tracking UIDVALIDITY at this point in its history, as it is logically quite simple to do correctly. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] IMAP Problem for Account
Stephan, Suggest you send feedback on all the problems via the Feedback option on the app. Also sending copy to the developer Benny Nielsen). My version seems stable on 10 accounts. Sorry can’t help further. Henry- -Please excuse the tttapping errors... Sent from my iPhoneC/T (954) 253-4125Henry M. SeidenTechworks ProOn Dec 7, 2023, at 11:37, Stephan Bösebeck wrote: Unfortunately this did not work. I tried also installing an older version (5937) - same issue. It ended up being so bad, that I could not use Mailmate anymore. So I removed the source... that caused errors, that Mailmate could not delete some emails. Then things went sideways. When trying to force delete, MailMate crashed. When keeping them, it also kept the account. So I deleted them via commandline - the whole account that is. Then, after staring MailMate again, it was downloading everything and it was then fine... Until I sent an email. I got the UIDVALIDITY-Message more or less directly after sending. I removed the account in total again, this time it worked... so I try to add it once more... I will see, if that helps. On 7 Dec 2023, at 17:18, i...@techworkspro.com wrote: I recently found the same problem you reported on MM r6008 (experimental build). In my case it was an Outlook IMAP account that was reporting the error What I found was that the password on my account’s SMTP settings was missing. I checked the Activity monitor first to verify the problem, then looked at IMAP Settings to confirm the cause. Re-entering the missing password cleared the issue up. HIH. YMMV, good luck! Henry - - Please excuse the tttapping errors... Sent from my iPhone C/T (954) 253-4125 Henry M. Seiden Techworks Pro On Dec 7, 2023, at 10:12, Stephan Bösebeck wrote: Hi, i am using the latest test-build for some days now, but I have a strange error message since today: IMAP Problem for "XXX" account The so-called UIDVALIDITY value of the mailbox "Sent" has changed. MailMate has to resynchronize the mailbox, that is, purge the local cache and refetch the messages of the mailbox. If this happens often then you should investigate the issue. Refetching messages is a very inefficient action. Note: The option to "Always Resynchronize" only works until MailMate is relaunched. I did that now 3 times and every time it restarts. Can it be related to SpamSieve? As this error only happens, if those messages are "trained" again... ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate ___mailmate mailing listmailmate@lists.freron.comhttps://lists.freron.com/listinfo/mailmate___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] IMAP Problem for Account
I remember this issue has come up on this list before. IIRC, it was related to something that changed on the email provider's side that confused MM. You can search the archives here: https://www.mail-archive.com/mailmate@lists.freron.com/ -Eric On 7 Dec 2023, at 11:36, Stephan Bösebeck wrote: Unfortunately this did not work. I tried also installing an older version (5937) - same issue. It ended up being so bad, that I could not use Mailmate anymore. So I removed the source... that caused errors, that Mailmate could not delete some emails. Then things went sideways. When trying to force delete, MailMate crashed. When keeping them, it also kept the account. So I deleted them via commandline - the whole account that is. Then, after staring MailMate again, it was downloading everything and it was _then_ fine... Until I sent an email. I got the UIDVALIDITY-Message more or less directly after sending. I removed the account in total again, this time it worked... so I try to add it once more... I will see, if that helps. On 7 Dec 2023, at 17:18, i...@techworkspro.com wrote: I recently found the same problem you reported on MM r6008 (experimental build). In my case it was an Outlook IMAP account that was reporting the error What I found was that the password on my account’s SMTP settings was missing. I checked the Activity monitor first to verify the problem, then looked at IMAP Settings to confirm the cause. Re-entering the missing password cleared the issue up. HIH. YMMV, good luck! Henry - - Please excuse the tttapping errors... Sent from my iPhone C/T (954) 253-4125 Henry M. Seiden Techworks Pro On Dec 7, 2023, at 10:12, Stephan Bösebeck wrote: Hi, i am using the latest test-build for some days now, but I have a strange error message since today: IMAP Problem for "XXX" account The so-called UIDVALIDITY value of the mailbox "Sent" has changed. MailMate has to resynchronize the mailbox, that is, purge the local cache and refetch the messages of the mailbox. If this happens often then you should investigate the issue. Refetching messages is a very inefficient action. Note: The option to "Always Resynchronize" only works until MailMate is relaunched. I did that now 3 times and every time it restarts. Can it be related to SpamSieve? As this error only happens, if those messages are "trained" again... ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] IMAP Problem for Account
Unfortunately this did not work. I tried also installing an older version (5937) - same issue. It ended up being so bad, that I could not use Mailmate anymore. So I removed the source... that caused errors, that Mailmate could not delete some emails. Then things went sideways. When trying to force delete, MailMate crashed. When keeping them, it also kept the account. So I deleted them via commandline - the whole account that is. Then, after staring MailMate again, it was downloading everything and it was _then_ fine... Until I sent an email. I got the UIDVALIDITY-Message more or less directly after sending. I removed the account in total again, this time it worked... so I try to add it once more... I will see, if that helps. On 7 Dec 2023, at 17:18, i...@techworkspro.com wrote: > I recently found the same problem you reported on MM r6008 (experimental > build). In my case it was an Outlook IMAP account that was reporting the error > > What I found was that the password on my account’s SMTP settings was missing. > I checked the Activity monitor first to verify the problem, then looked at > IMAP Settings to confirm the cause. Re-entering the missing password cleared > the issue up. > > HIH. YMMV, good luck! > Henry > - - > Please excuse the tttapping errors... > Sent from my iPhone > C/T (954) 253-4125 > Henry M. Seiden > Techworks Pro > > >> On Dec 7, 2023, at 10:12, Stephan Bösebeck wrote: >> >> >> Hi, >> >> i am using the latest test-build for some days now, but I have a strange >> error message since today: >> >> IMAP Problem for "XXX" account >> >> The so-called UIDVALIDITY value of the mailbox "Sent" has changed. MailMate >> has to resynchronize the mailbox, that is, purge the local cache and refetch >> the messages of the mailbox. >> If this happens often then you should investigate the issue. Refetching >> messages is a very inefficient action. >> Note: The option to "Always Resynchronize" only works until MailMate is >> relaunched. >> I did that now 3 times and every time it restarts. Can it be related to >> SpamSieve? As this error only happens, if those messages are "trained" >> again... >> >> ___ >> mailmate mailing list >> mailmate@lists.freron.com >> https://lists.freron.com/listinfo/mailmate > ___ > mailmate mailing list > mailmate@lists.freron.com > https://lists.freron.com/listinfo/mailmate signature.asc Description: OpenPGP digital signature ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
Re: [MlMt] IMAP Problem for Account
I recently found the same problem you reported on MM r6008 (experimental build). In my case it was an Outlook IMAP account that was reporting the error What I found was that the password on my account’s SMTP settings was missing. I checked the Activity monitor first to verify the problem, then looked at IMAP Settings to confirm the cause. Re-entering the missing password cleared the issue up. HIH. YMMV, good luck! Henry - - Please excuse the tttapping errors... Sent from my iPhone C/T (954) 253-4125 Henry M. Seiden Techworks Pro > On Dec 7, 2023, at 10:12, Stephan Bösebeck wrote: > > > Hi, > > i am using the latest test-build for some days now, but I have a strange > error message since today: > > IMAP Problem for "XXX" account > > The so-called UIDVALIDITY value of the mailbox "Sent" has changed. MailMate > has to resynchronize the mailbox, that is, purge the local cache and refetch > the messages of the mailbox. > If this happens often then you should investigate the issue. Refetching > messages is a very inefficient action. > Note: The option to "Always Resynchronize" only works until MailMate is > relaunched. > I did that now 3 times and every time it restarts. Can it be related to > SpamSieve? As this error only happens, if those messages are "trained" > again... > > ___ > mailmate mailing list > mailmate@lists.freron.com > https://lists.freron.com/listinfo/mailmate ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
[MlMt] IMAP Problem for Account
Hi, i am using the latest test-build for some days now, but I have a strange error message since today: ``` IMAP Problem for "XXX" account The so-called UIDVALIDITY value of the mailbox "Sent" has changed. MailMate has to resynchronize the mailbox, that is, purge the local cache and refetch the messages of the mailbox. If this happens often then you should investigate the issue. Refetching messages is a very inefficient action. Note: The option to "Always Resynchronize" only works until MailMate is relaunched. ``` I did that now 3 times and every time it restarts. Can it be related to SpamSieve? As this error only happens, if those messages are "trained" again... signature.asc Description: OpenPGP digital signature ___ mailmate mailing list mailmate@lists.freron.com https://lists.freron.com/listinfo/mailmate
