Advise needed for new mail server
Hello, I have been successfully using postfix+cyrus-imapd (2.4.17) for our small company for years on our local server. The emails are now accounting to a size of some 160GB. As we are having power and internet problems quite often, I rented a VPS from a world renowned hosting company and installed postfix+cyrus-imapd there. My question is, as I have limited hard disk space (40GB) on VPS, I can't (and don't want to) copy all of my local emails to the VPS. The new mail server will have a fresh start. But old emails needs to be accessible on the local server as well. Currently, I am planning to change the names of local domains to some non-existent name just for the internal lookup (example.com --> example2.com), so that we can setup example2.com on our email clients on lan. The real domain example.com will be setup on our desktop email clients as usual. I think, using example2.com on local lan just for reading mails by cyrus will work, but it is not an elegant solution. I would appreciate any ideas. Regards, Mufit Eribol Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Cyrus IMAP 2.4 to 2.5 replication
I am looking at migrating a Cyrus IMAP 2.4 server to 2.5 (actually Kolab 3.1 to 3.4) and was wondering if it was safe to use the built in replication between the releases. Thanks Mike Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Advise needed for new mail server
Hi Mufit, Quoting Mufit Eribol via Info-cyrus: Hello, I have been successfully using postfix+cyrus-imapd (2.4.17) for our small company for years on our local server. The emails are now accounting to a size of some 160GB. As we are having power and internet problems quite often, I rented a VPS from a world renowned hosting company and installed postfix+cyrus-imapd there. My question is, as I have limited hard disk space (40GB) on VPS, I can't (and don't want to) copy all of my local emails to the VPS. The new mail server will have a fresh start. But old emails needs to be accessible on the local server as well. Currently, I am planning to change the names of local domains to some non-existent name just for the internal lookup (example.com --> example2.com), so that we can setup example2.com on our email clients on lan. The real domain example.com will be setup on our desktop email clients as usual. I think, using example2.com on local lan just for reading mails by cyrus will work, but it is not an elegant solution. I would appreciate any ideas. Cyrus Murder my be the solution for you. https://cyrusimap.org/mediawiki/index.php/Cyrus_Murder The Clients will only connect to one server (VPS), and the mails can be stored on different backend servers. There is only minimal configuration change needed on your old server, but you would need to rename the folders. 1 backend (VPS) for the INBOX and folders with new Mail 1 backend (old System) with all old folders in an archive subfolder for each user 1 mupdate master (VPS) 1 frontend (VPS) Regards Michael Menge M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Advise needed for new mail server
Zitat von Michael Menge via Info-cyrus: Hi Mufit, Quoting Mufit Eribol via Info-cyrus : Hello, I have been successfully using postfix+cyrus-imapd (2.4.17) for our small company for years on our local server. The emails are now accounting to a size of some 160GB. As we are having power and internet problems quite often, I rented a VPS from a world renowned hosting company and installed postfix+cyrus-imapd there. My question is, as I have limited hard disk space (40GB) on VPS, I can't (and don't want to) copy all of my local emails to the VPS. The new mail server will have a fresh start. But old emails needs to be accessible on the local server as well. Currently, I am planning to change the names of local domains to some non-existent name just for the internal lookup (example.com --> example2.com), so that we can setup example2.com on our email clients on lan. The real domain example.com will be setup on our desktop email clients as usual. I think, using example2.com on local lan just for reading mails by cyrus will work, but it is not an elegant solution. I would appreciate any ideas. Cyrus Murder my be the solution for you. https://cyrusimap.org/mediawiki/index.php/Cyrus_Murder The Clients will only connect to one server (VPS), and the mails can be stored on different backend servers. There is only minimal configuration change needed on your old server, but you would need to rename the folders. 1 backend (VPS) for the INBOX and folders with new Mail 1 backend (old System) with all old folders in an archive subfolder for each user 1 mupdate master (VPS) 1 frontend (VPS) Regards Michael Menge Depending on the mail clients used and the number of clients you can also simply setup the new server as a additional IMAP Account and disable the (incoming) SMTP service on the old server. With this you will have the internal IMAP server as "archive" with a lot of storage and the new server for internet related traffic. Regards Andreas smime.p7s Description: S/MIME Cryptographic Signature Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: PATCH for lmtp was [frontend lmtp connections to mupdate master]
Hi, https://cyrusimap.org/mediawiki/index.php/Cyrus_Murder_Failure_Modes "2. Mail delivery via the frontends is deferred (lmtpproxyd cannot locate mailbox). " should be updated too Quoting Ken Murchison: Done. On 11/17/2015 03:29 AM, Michael Menge wrote: Hi Ken thanks. Do you intend to patch 2.4.x and 2.5.x ? I am a bit confused by the recent changes of cyrusimap and cyrus.fondation. Is the bugtracker https://bugzilla.cyrusimap.org still used by the project? If yes, you should close https://bugzilla.cyrusimap.org/show_bug.cgi?id=3866, if not, someone should add some information where the new bugtracker can be found Regards Michael Quoting Ken Murchison : I committed a revised version just a little while ago: https://git.cyrus.foundation/rI0fd86ca759ffa32e8d22dbdde78ea82d63650827 On 11/16/2015 04:41 AM, Michael Menge via Info-cyrus wrote: Hi, is there anything missing from my side, or something that I can do to help that my patch can be included? Regards Michael Quoting Nic Bernstein via Info-cyrus : Bron, We're starting to run into this same issue -- lmtp proxies fail to deliver mail when mupdate master craps -- and so started to investigate this thread. However, it doesn't look like Michael Menge's patch made it in. Your thoughts? -nic On 10/07/2014 08:17 AM, Bron Gondwana wrote: I'm convinced :) I'll probably add it with Ken while we're at CMU in a couple of weeks when we can test it together. This is precisely the kind of thing we love to see! Thanks. Bron. On Tue, Oct 7, 2014, at 10:23 PM, Michael Menge wrote: Hi, as we have had an other crash of mupdate master last week, we used the patch on our production system. After the patch was added the load on mupdate master was dropping form about 10 to about 1. After one week of using it we have not found any problems. As I have not received any other feedback, I added it to the bugtracker. https://bugzilla.cyrusimap.org/show_bug.cgi?id=3866 Pleas consider adding it to 2.5 and 2.4.next Regards Michael Quoting Michael Menge : Hi, Quoting Michael Menge : Quoting Michael Menge : By thew way, the reason I was so surprised in the first place was, that I have been fooled by the documentation: Quoting https://cyrusimap.org/docs/cyrus-imapd/2.4.17/install-murder.php Configuring the frontends [...] However, because the frontends only talk to the mupdate master via a slave running on the local machine, you will also need to set up a slave on the same machine, in the SERVICES section of cyrus.conf, like so And an other misleading DOC ! Quoting http://www.cyrusimap.org/mediawiki/index.php/Cyrus_Murder_Mail_Delivery UMich patch Patch Patches are against 2.2 but are being moved to 2.3 Lmtpproxyd will now use the local mailboxes.db Quoting Wesley Craig : On 29 Sep 2014, at 10:08, Michael Menge wrote: thanks for your mail. By any chance do you still have the patch? In fact, I don't. Dusting off my notes, I recall now that instead of patching this (bogus) code, we instead decided to configure the frontends as "unified", while leaving the backends "standard". The only downside of this approach was that a naive admin could potentially create a user's mailbox on a frontend. Sorry I said that we ported that code forward: in fact we simply got the effect of consulting mailboxes.db without porting forward. :wes I have patched my lmtpd to use the local mailbox.db in all cases, unified Murder, and standalone cyrus already did this. I tested it with a few testmails on my test system, but as i don't have a unified setup or a standalone test system at the moment i didn't test these setups. I would appreciate a review. Regards, Michael Menge M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus Email had 1 attachment: + smime.p7s 7k (application/pkcs7-signature) -- Nic Bernstein n...@onlight.com Onlight, Inc.