[BlueOnyx:26487] Re: POP sent to IMAP sent
Hi Meaulnes, I guess all of you guys use IMAP on all of your computers, so you don't have this problem... I was looking for a solution for fetching my Sent folder contents automatically from my office desktop computer to the remote Sent folder on the server. Like Taco and Chris have already mentioned: This day and age IMAP is really the best choice if you want to use the same account on multiple devices AND have all emails (sent and received) accessible everywhere. I was in the same boat many years ago and was still using POP3 on an important account. Eventually it really became too much of an hassle when using multiple devices for checking emails. Here is what I did: In Thunderbird I disabled the account that was still using POP3 and excluded it from being checked. I also renamed it to "usern...@server.com (POP3)" to make it really obvious: That's one old one. Then I recreated the account in Thunderbird (using the same server, username and password), but configured it to use IMAP instead. That way I now had two configurations in the email client for the very same account: An active one using IMAP, and a disabled one that used to use POP3 before it got disabled and was now excluded from regular email checks. Now there were a few recent messages (and replies of mine) that I wanted to be present on the server and accessible via IMAP. So in Thunderbird I selected those messages and copied them from the disabled POP3 account to the now active IMAP account. Which then uploaded the messages via IMAP to the server. Then I set up a sensible folder structure and sorted the messages into the right folders. If there were still a message older than that which I needed? I still had the old POP3 account data in Thunderbird and could fetch 'em from there. So it's really not too much hassle to switch from POP3 to IMAP in the email-client. To the contrary: That little discomfort during the switch is repaid tenfold from there on. Also, when you do this: Email clients usually also allow you to configure how long they keep messages on the server before deleting them there, or what to do with messages after that expiry date. Especially with IMAP (which usually leaves emails on the server) you should set up some sensible expunging or archiving. Depending on the accounts typical usage I leave emails on the server for a few days or so and then archive them into either an IMAP folder on the server, or a local folder on my PC. -- With best regards Michael Stauber ___ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
[BlueOnyx:26486] Re: Strange SSL error
Hi Colin, Unfortunately that hasn't fixed it. I set up a test and still get a problem. The vsite in question has the main host FQDN with 3 aliases: So vsite is for example mail.domain.com Also aliases smtp.domain.com, pop.domain.com If the email client settings use incoming server as mail.domain.com all works fine. If the email client uses either of the aliases it fails - returning the BX host cert. :-/ Indeed. I just replicated that setup on a test box and did some testing. The revised code from last weekend indeed wasn't catching all "DNS:" entries from the parsed SSL cert. If that line had three entries, it caught the first and last entry and ignored the middle one. I just published new base-email-* RPMs for BlueOnyx 5210R and 5211R which fix this issue. Please do another "yum clean all" and "yum update" to get these updates. That will then also automatically restart CCEd, which will then fix the SNI cert configs for both Dovecot and Postfix. Sorry about that. -- With best regards Michael Stauber ___ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
[BlueOnyx:26485] Re: Strange SSL error
Hi Michael, >To address your issue do the following: >Run "yum clean all" and "yum update" to make sure you have all updates >installed. Then restart CCEd for good measure: >/usr/sausalit/sbin/cced.init restart >If that doesn't fix it, try to renew the SSL certificate for the Vsite >in question. Unfortunately that hasn't fixed it. I set up a test and still get a problem. The vsite in question has the main host FQDN with 3 aliases: So vsite is for example mail.domain.com Also aliases smtp.domain.com, pop.domain.com If the email client settings use incoming server as mail.domain.com all works fine. If the email client uses either of the aliases it fails - returning the BX host cert. :-/ Regards Colin ___ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
[BlueOnyx:26484] Re: Strange SSL error
Thanks Michael, >> This weekend we started getting complaints of SSL errors when using >> email clients – the email client apparently returning the cert for the >> host server rather than the vsite when using one of the aliases. >This might be related to a YUM update that was published on Friday. >While working on a client server I noticed that he had non-working SNI >for several Vsites. The Vsites where it didn't work all had a single >FQDN which they responded to. And the Handler/Constructor that parse the >SSL certs to generate the SNI config files for Postfix and Dovecot so f>ar only parse the "DNS:" line in the certificates, but not the >"Subject:" line. So single FQDN certs resulted in a somewhat borked >email SNI configuration. The update from Friday fixes that. I thought it must have been an update! >To address your issue do the following: >Run "yum clean all" and "yum update" to make sure you have all updates >installed. Then restart CCEd for good measure: >/usr/sausalit/sbin/cced.init restart >If that doesn't fix it, try to renew the SSL certificate for the Vsite >in question. Have done that so will see how many complaints we get tomorrow! Kind regards Colin ___ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
[BlueOnyx:26483] Re: POP sent to IMAP sent
On 9/18/2023 1:42 AM, Taco Scargo via Blueonyx wrote: Maybe a stupid suggestion, but why not use IMAP everywhere. That's not a stupid suggestion at all. If email is to be sync'd across devices, IMAP is really the only logical solution You can then (maybe using rules) move any e-mail that is older than, say 14 days, to a local folder if you want to save storage space on your server. Yes, that's absolutely a possibility. For instance, in Thunderbird you can set a message filter based on Age in Days, greater than, then define the number, and select an action such as move to a local folder. If that's even a requirement for you... server storage is plentiful these days. If you need a larger server to store your emails, let me know and I'll price it up for you! ;) What I personally do though is having Gmail pop the mail from my BlueOnyx server. Gmail offers me enough space :) Ooof. Now that's one I REALLY dislike. Having self-hosted email since 1996, I cannot imagine handing any of my own email over to the likes of Google. Once it's in their system, goodness only knows how that's manipulated, sold or stolen. I'd stay far away from that as a "solution." Perhaps I'm just not trusting enough of Google (and so forth) to treat my data with respect. -- Chris Gebhardt VIRTBIZ Internet Services Access, Web Hosting, Colocation, Dedicated www.virtbiz.com | toll-free (866) 4 VIRTBIZ ___ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
[BlueOnyx:26482] Re: Strange SSL error
Hi Colin, We have a strange SSL error with email that has just raised its head. Been fine for years but may have been an update? We have a 5210R running postfix. A Vsite on the server has a couple of web aliases (historical combining of servers). The LE cert has all aliases and if using a web browser to access roundcube then it all works fine. Site is secure. Many of our customers are still using one of the aliases in their email client server address and have done for years. This weekend we started getting complaints of SSL errors when using email clients – the email client apparently returning the cert for the host server rather than the vsite when using one of the aliases. This might be related to a YUM update that was published on Friday. While working on a client server I noticed that he had non-working SNI for several Vsites. The Vsites where it didn't work all had a single FQDN which they responded to. And the Handler/Constructor that parse the SSL certs to generate the SNI config files for Postfix and Dovecot so far only parse the "DNS:" line in the certificates, but not the "Subject:" line. So single FQDN certs resulted in a somewhat borked email SNI configuration. The update from Friday fixes that. To address your issue do the following: Run "yum clean all" and "yum update" to make sure you have all updates installed. Then restart CCEd for good measure: /usr/sausalit/sbin/cced.init restart If that doesn't fix it, try to renew the SSL certificate for the Vsite in question. -- With best regards Michael Stauber ___ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
[BlueOnyx:26481] Strange SSL error
Good morning, We have a strange SSL error with email that has just raised its head. Been fine for years but may have been an update? We have a 5210R running postfix. A Vsite on the server has a couple of web aliases (historical combining of servers). The LE cert has all aliases and if using a web browser to access roundcube then it all works fine. Site is secure. Many of our customers are still using one of the aliases in their email client server address and have done for years. This weekend we started getting complaints of SSL errors when using email clients – the email client apparently returning the cert for the host server rather than the vsite when using one of the aliases. Changing to the primary host for the vsite in the email client settings solves the problem but many of our customers are elderly and not comfortable with changing settings. Does anybody know what has changed and why this is suddenly happening? Hope I have explained clearly! Thanks Colin ___ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx
