From l.schimmer at cgv.tugraz.at Thu Aug 1 10:12:31 2019 From: l.schimmer at cgv.tugraz.at (Lars Schimmer) Date: Thu, 1 Aug 2019 16:12:31 +0200 Subject: Upgrade report debian cyrus Message-ID: <05af0a25-6d4d-c4e0-9584-c0eb56c2c70a@cgv.tugraz.at> Hi! Just upgraded my old debian cyrus 2.4.16-4+deb7u2 to cyrus 3.0.8-6. I did use a new hardware system for this, copied over all mailbox, sieve,.. data and did a recontruct. It seems the reconstruct needs a few uns to reconstruct our 100GB mail archive (in ~120 mailboxes). I did a reconctruct -V max and it did not find all mails, I did run it twice, and on second run it did find a lot of mails with "reappending" messages. Also, after migration, some users did not seem to have a inbox, I needed to "cm user.xcy" and copy mailbox data into it and recontruct manually. (seems like those are new mailboxes and are not in the copied data of main cyrus db). But some mailboxes were existent, but empty after the 2 reconstruct (and quota) run, I did explicit run reconstruct -r -f user.xyyya on those. To bad they got all mails as unseen. On the most accounts all worked fine, but all mails prior to sept 2011 are set to unseen. Seems like some change of dataformat, as I did upgrade in sept 2011 :-) Now I sit here and wait for more error reports from the users. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut f?r ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer at cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From karagian at gmail.com Thu Aug 1 10:40:03 2019 From: karagian at gmail.com (Savvas Karagiannidis) Date: Thu, 1 Aug 2019 17:40:03 +0300 Subject: Upgrade report debian cyrus In-Reply-To: <05af0a25-6d4d-c4e0-9584-c0eb56c2c70a@cgv.tugraz.at> References: <05af0a25-6d4d-c4e0-9584-c0eb56c2c70a@cgv.tugraz.at> Message-ID: Hi Lars, there was an issue when upgrading to 3.0.x from older versions (2.x). The issue is this: https://github.com/cyrusimap/cyrus-imapd/issues/2208 >From my experience, the only way to safely upgrade to 3.0 was to run reconstruct -G -V max on all mailboxes while still in the older version. Ellie explains the exact issues with old mail in the last comment before closing the issue mentioned above and I'm surprised to not see any mention of this (the -G parameter) in the 3.0 release notes and upgrade instructions... You can still run reconstruct -G -V max on the new system with the latest version but the result will probably be that these older messages will appear as unread. Regards, Savvas Karagiannidis On Thu, Aug 1, 2019 at 5:13 PM Lars Schimmer wrote: > Hi! > > Just upgraded my old debian cyrus 2.4.16-4+deb7u2 to cyrus 3.0.8-6. > I did use a new hardware system for this, copied over all mailbox, > sieve,.. data and did a recontruct. > > It seems the reconstruct needs a few uns to reconstruct our 100GB mail > archive (in ~120 mailboxes). > > I did a reconctruct -V max and it did not find all mails, I did run it > twice, and on second run it did find a lot of mails with "reappending" > messages. > > Also, after migration, some users did not seem to have a inbox, I needed > to "cm user.xcy" and copy mailbox data into it and recontruct manually. > (seems like those are new mailboxes and are not in the copied data of > main cyrus db). > > But some mailboxes were existent, but empty after the 2 reconstruct (and > quota) run, I did explicit run reconstruct -r -f user.xyyya on those. > To bad they got all mails as unseen. > > On the most accounts all worked fine, but all mails prior to sept 2011 > are set to unseen. > Seems like some change of dataformat, as I did upgrade in sept 2011 :-) > > Now I sit here and wait for more error reports from the users. > > > > MfG, > Lars Schimmer > -- > ------------------------------------------------------------- > TU Graz, Institut f?r ComputerGraphik & WissensVisualisierung > Tel: +43 316 873-5405 E-Mail: l.schimmer at cgv.tugraz.at > Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 > > > > ---- > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ellie at fastmail.com Sun Aug 4 20:21:32 2019 From: ellie at fastmail.com (ellie timoney) Date: Mon, 05 Aug 2019 10:21:32 +1000 Subject: Upgrade report debian cyrus In-Reply-To: References: <05af0a25-6d4d-c4e0-9584-c0eb56c2c70a@cgv.tugraz.at> Message-ID: On Thu, Aug 1, 2019 at 5:13 PM Lars Schimmer wrote: > and on second run it did find a lot of mails with "reappending" messages. Actually, this sounds like this bug: https://github.com/cyrusimap/cyrus-imapd/issues/2839 (fixed last week in 3.0.11) There is a Debian report for it too: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163 I guess we're going to see a lot of this here, as people start upgrading older systems to the new Debian stable and getting Debian's 3.0.8 instead of whatever they had before. On Fri, Aug 2, 2019, at 12:44 AM, Savvas Karagiannidis wrote: > there was an issue when upgrading to 3.0.x from older versions (2.x). The issue is this: > https://github.com/cyrusimap/cyrus-imapd/issues/2208 > > Ellie explains the exact issues with old mail in the last comment before closing the issue mentioned above and I'm surprised to not see any mention of this (the -G parameter) in the 3.0 release notes and upgrade instructions... Oh, I'd forgotten about that! I'm going to add a note about this to the reconstruct -G documentation as well as the upgrade notes. It is a different issue though: the impact of #2208 (since the crash was fixed in 3.0.8, anyway) is being unable to replicate due to missing GUID's. You need reconstruct with -G before upgrading if you plan to build a new server and replicate your old store to it (which you will find out when you try to replicate). But it won't affect in-place upgrades until you try to replicate them somewhere later. #2839 is rather more annoying because it affects in-place upgrades and copy-files-and-reconstruct upgrades! Cheers, ellie On Fri, Aug 2, 2019, at 12:44 AM, Savvas Karagiannidis wrote: > Hi Lars, > there was an issue when upgrading to 3.0.x from older versions (2.x). The issue is this: > https://github.com/cyrusimap/cyrus-imapd/issues/2208 > > From my experience, the only way to safely upgrade to 3.0 was to run reconstruct -G -V max on all mailboxes while still in the older version. > Ellie explains the exact issues with old mail in the last comment before closing the issue mentioned above and I'm surprised to not see any mention of this (the -G parameter) in the 3.0 release notes and upgrade instructions... > You can still run reconstruct -G -V max on the new system with the latest version but the result will probably be that these older messages will appear as unread. > > > Regards, > Savvas Karagiannidis > > On Thu, Aug 1, 2019 at 5:13 PM Lars Schimmer wrote: >> Hi! >> >> Just upgraded my old debian cyrus 2.4.16-4+deb7u2 to cyrus 3.0.8-6. >> I did use a new hardware system for this, copied over all mailbox, >> sieve,.. data and did a recontruct. >> >> It seems the reconstruct needs a few uns to reconstruct our 100GB mail >> archive (in ~120 mailboxes). >> >> I did a reconctruct -V max and it did not find all mails, I did run it >> twice, and on second run it did find a lot of mails with "reappending" >> messages. >> >> Also, after migration, some users did not seem to have a inbox, I needed >> to "cm user.xcy" and copy mailbox data into it and recontruct manually. >> (seems like those are new mailboxes and are not in the copied data of >> main cyrus db). >> >> But some mailboxes were existent, but empty after the 2 reconstruct (and >> quota) run, I did explicit run reconstruct -r -f user.xyyya on those. >> To bad they got all mails as unseen. >> >> On the most accounts all worked fine, but all mails prior to sept 2011 >> are set to unseen. >> Seems like some change of dataformat, as I did upgrade in sept 2011 :-) >> >> Now I sit here and wait for more error reports from the users. >> >> >> >> MfG, >> Lars Schimmer >> -- >> ------------------------------------------------------------- >> TU Graz, Institut f?r ComputerGraphik & WissensVisualisierung >> Tel: +43 316 873-5405 E-Mail: l.schimmer at cgv.tugraz.at >> Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 >> >> >> >> ---- >> 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From gbulfon at sonicle.com Mon Aug 5 03:26:42 2019 From: gbulfon at sonicle.com (Gabriele Bulfon) Date: Mon, 5 Aug 2019 09:26:42 +0200 (CEST) Subject: Cyrus 2.5.11 default domain on auth In-Reply-To: <23e4cf73-3461-7ef5-6411-f856a5548a4a@home.wdc.spb.ru> References: <1243978856.960.1564562538571@www> <23e4cf73-3461-7ef5-6411-f856a5548a4a@home.wdc.spb.ru> Message-ID: <636346394.500.1564990002597@www> Thanks. So this means that default domain is not treated as a virutal domain mailbox. What I want to achieve is: - if the user try to authenticate with name.lastname at domain.com ?, get into the specific user/name.lastname at domain.com mailbox - if the user try to authenticate with name.lastname, authenticate?against a default domain defdomain.com, and if it's correct, get into the specific user/name.lastname at defdomain.com ? How can I do this? ? Gabriele? ? ? Sonicle S.r.l.? :? http://www.sonicle.com Music:? http://www.gabrielebulfon.com Quantum Mechanics :? http://www.cdbaby.com/cd/gabrielebulfon Da: Eugene V. Boontseff A: Gabriele Bulfon Data: 3 agosto 2019 17.54.36 CEST Oggetto: Re: Cyrus 2.5.11 default domain on auth On 31.07.2019 11:42, Gabriele Bulfon wrote: ? If I try adding defaultdomain, what happens is that authentication works both with and without specifying domain, but then you're not on your normal inbox of user/name.lastname at domain.com but somewhere else strange, a SELECT INBOX returns mailbox not found. ? What's wrong? How can I achieve my goal? Default domain mailboxes look like this: user/name.lastname ? Thanks! Gabriele ? ? -- Eugene -------------- next part -------------- An HTML attachment was scrubbed... URL: From karagian at gmail.com Mon Aug 5 07:27:37 2019 From: karagian at gmail.com (Savvas Karagiannidis) Date: Mon, 5 Aug 2019 14:27:37 +0300 Subject: Upgrade report debian cyrus In-Reply-To: References: <05af0a25-6d4d-c4e0-9584-c0eb56c2c70a@cgv.tugraz.at> Message-ID: Thanks for clarifying this Ellie, I thought the two issues are actually related. And thanks for adding the mention to -G to the release notes. Regards, Savvas Karagiannidis On Mon, Aug 5, 2019 at 3:22 AM ellie timoney wrote: > On Thu, Aug 1, 2019 at 5:13 PM Lars Schimmer > wrote: > > and on second run it did find a lot of mails with "reappending" messages. > > > Actually, this sounds like this bug: > https://github.com/cyrusimap/cyrus-imapd/issues/2839 (fixed last week in > 3.0.11) > There is a Debian report for it too: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163 > > I guess we're going to see a lot of this here, as people start upgrading > older systems to the new Debian stable and getting Debian's 3.0.8 instead > of whatever they had before. > > > On Fri, Aug 2, 2019, at 12:44 AM, Savvas Karagiannidis wrote: > > there was an issue when upgrading to 3.0.x from older versions (2.x). The > issue is this: > https://github.com/cyrusimap/cyrus-imapd/issues/2208 > > Ellie explains the exact issues with old mail in the last comment before > closing the issue mentioned above and I'm surprised to not see any mention > of this (the -G parameter) in the 3.0 release notes and upgrade > instructions... > > > Oh, I'd forgotten about that! I'm going to add a note about this to the > reconstruct -G documentation as well as the upgrade notes. > > It is a different issue though: the impact of #2208 (since the crash was > fixed in 3.0.8, anyway) is being unable to replicate due to missing > GUID's. You need reconstruct with -G before upgrading if you plan to build > a new server and replicate your old store to it (which you will find out > when you try to replicate). But it won't affect in-place upgrades until > you try to replicate them somewhere later. > > #2839 is rather more annoying because it affects in-place upgrades and > copy-files-and-reconstruct upgrades! > > Cheers, > > ellie > > On Fri, Aug 2, 2019, at 12:44 AM, Savvas Karagiannidis wrote: > > Hi Lars, > there was an issue when upgrading to 3.0.x from older versions (2.x). The > issue is this: > https://github.com/cyrusimap/cyrus-imapd/issues/2208 > > From my experience, the only way to safely upgrade to 3.0 was to run > reconstruct -G -V max on all mailboxes while still in the older version. > Ellie explains the exact issues with old mail in the last comment before > closing the issue mentioned above and I'm surprised to not see any mention > of this (the -G parameter) in the 3.0 release notes and upgrade > instructions... > You can still run reconstruct -G -V max on the new system with the latest > version but the result will probably be that these older messages will > appear as unread. > > > Regards, > Savvas Karagiannidis > > On Thu, Aug 1, 2019 at 5:13 PM Lars Schimmer > wrote: > > Hi! > > Just upgraded my old debian cyrus 2.4.16-4+deb7u2 to cyrus 3.0.8-6. > I did use a new hardware system for this, copied over all mailbox, > sieve,.. data and did a recontruct. > > It seems the reconstruct needs a few uns to reconstruct our 100GB mail > archive (in ~120 mailboxes). > > I did a reconctruct -V max and it did not find all mails, I did run it > twice, and on second run it did find a lot of mails with "reappending" > messages. > > Also, after migration, some users did not seem to have a inbox, I needed > to "cm user.xcy" and copy mailbox data into it and recontruct manually. > (seems like those are new mailboxes and are not in the copied data of > main cyrus db). > > But some mailboxes were existent, but empty after the 2 reconstruct (and > quota) run, I did explicit run reconstruct -r -f user.xyyya on those. > To bad they got all mails as unseen. > > On the most accounts all worked fine, but all mails prior to sept 2011 > are set to unseen. > Seems like some change of dataformat, as I did upgrade in sept 2011 :-) > > Now I sit here and wait for more error reports from the users. > > > > MfG, > Lars Schimmer > -- > ------------------------------------------------------------- > TU Graz, Institut f?r ComputerGraphik & WissensVisualisierung > Tel: +43 316 873-5405 E-Mail: l.schimmer at cgv.tugraz.at > Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 > > > > ---- > 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 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From eugene at home.wdc.spb.ru Mon Aug 5 13:21:52 2019 From: eugene at home.wdc.spb.ru (Eugene V. Boontseff) Date: Mon, 5 Aug 2019 20:21:52 +0300 Subject: Cyrus 2.5.11 default domain on auth In-Reply-To: <636346394.500.1564990002597@www> References: <1243978856.960.1564562538571@www> <23e4cf73-3461-7ef5-6411-f856a5548a4a@home.wdc.spb.ru> <636346394.500.1564990002597@www> Message-ID: <3265e583-0ec7-ea25-45e7-a9d35a2b4b3b@home.wdc.spb.ru> On 05.08.2019 10:26, Gabriele Bulfon wrote: > > Thanks. > So this means that default domain is not treated as a virutal domain > mailbox. > What I want to achieve is: > - if the user try to authenticate with name.lastname at domain.com > ?, get into the specific > user/name.lastname at domain.com mailbox > - if the user try to authenticate with name.lastname, > authenticate?against a default domain defdomain.com, and if it's > correct, get into the specific user/name.lastname at defdomain.com > How can I do this? As far as I understand, this is impossible. You can try to transfer information about the boxes and the boxes themselves from the places where you have it now, to the place where the default domain should be. After that, run reconstruct. But I'm not completely sure. > Gabriele > > *Sonicle S.r.l. *: http://www.sonicle.com > *Music: *http://www.gabrielebulfon.com > *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon > > ------------------------------------------------------------------------ > > > *Da:* Eugene V. Boontseff > *A:* Gabriele Bulfon > *Data:* 3 agosto 2019 17.54.36 CEST > *Oggetto:* Re: Cyrus 2.5.11 default domain on auth > > > On 31.07.2019 11:42, Gabriele Bulfon wrote: > > > If I try adding defaultdomain, what happens is that > authentication works both with and without specifying domain, > but then you're not on your normal inbox of > user/name.lastname at domain.com but somewhere else strange, a > SELECT INBOX returns mailbox not found. > What's wrong? How can I achieve my goal? > > Default domain mailboxes look like this: user/name.lastname > > Thanks! > Gabriele > > -- > Eugene > > > ---- > 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 -- Eugene -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.schimmer at cgv.tugraz.at Tue Aug 20 04:45:26 2019 From: l.schimmer at cgv.tugraz.at (Lars Schimmer) Date: Tue, 20 Aug 2019 10:45:26 +0200 Subject: debian cyrus 3.0.8 saslauth, AD and apple mail pop3s issue Message-ID: <3ee30d76-068d-ac07-1d20-ee0ac4dbaf14@cgv.tugraz.at> Hi! I did setup a debian buster system with cyrus 3.0.8-6 We setup cyrus to use saslauth to authenticate against AD. So far all known windows/linux IMAP clients do fetch their IMAP mails without issues. But we got a issue with POP3s on a iPad, it cannot login and I do not see much information why it does not work, not much in logs. Any seen this issue before? MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut f?r ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer at cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From Hagedorn at uni-koeln.de Tue Aug 20 05:01:34 2019 From: Hagedorn at uni-koeln.de (Sebastian Hagedorn) Date: Tue, 20 Aug 2019 11:01:34 +0200 Subject: debian cyrus 3.0.8 saslauth, AD and apple mail pop3s issue In-Reply-To: <3ee30d76-068d-ac07-1d20-ee0ac4dbaf14@cgv.tugraz.at> References: <3ee30d76-068d-ac07-1d20-ee0ac4dbaf14@cgv.tugraz.at> Message-ID: Am 20.08.19 um 10:45 Uhr schrieb Lars Schimmer: > Hi! > > I did setup a debian buster system with cyrus 3.0.8-6 > We setup cyrus to use saslauth to authenticate against AD. > > So far all known windows/linux IMAP clients do fetch their IMAP mails > without issues. > > But we got a issue with POP3s on a iPad, it cannot login and I do not > see much information why it does not work, not much in logs. > > Any seen this issue before? No, but I wonder if IMAP works on the iPad. If not I would suspect certificate issues. When you say "not much in logs", what do you see? If the iPad gets past the SSL handshake, you should be able to see what's going wrong by enabling telemetry on the server. Create a directory with the user name in config directory/logs Make sure that it's writable by Cyrus. -- .:.Sebastian Hagedorn - Weyertal 121 (Geb?ude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universit?t zu K?ln / Cologne University - ? +49-221-470-89578.:. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x197B06994D105B45.asc Type: application/pgp-keys Size: 17099 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Hagedorn.vcf Type: text/x-vcard Size: 333 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5367 bytes Desc: S/MIME Cryptographic Signature URL: From l.schimmer at cgv.tugraz.at Tue Aug 20 05:12:53 2019 From: l.schimmer at cgv.tugraz.at (Lars Schimmer) Date: Tue, 20 Aug 2019 11:12:53 +0200 Subject: debian cyrus 3.0.8 saslauth, AD and apple mail pop3s issue - solved In-Reply-To: References: <3ee30d76-068d-ac07-1d20-ee0ac4dbaf14@cgv.tugraz.at> Message-ID: On 8/20/19 11:01 AM, Sebastian Hagedorn wrote: > > Am 20.08.19 um 10:45 Uhr schrieb Lars Schimmer: >> Hi! >> >> I did setup a debian buster system with cyrus 3.0.8-6 >> We setup cyrus to use saslauth to authenticate against AD. >> >> So far all known windows/linux IMAP clients do fetch their IMAP mails >> without issues. >> >> But we got a issue with POP3s on a iPad, it cannot login and I do not >> see much information why it does not work, not much in logs. >> >> Any seen this issue before? > > No, but I wonder if IMAP works on the iPad. If not I would suspect > certificate issues. When you say "not much in logs", what do you see? > > If the iPad gets past the SSL handshake, you should be able to see > what's going wrong by enabling telemetry on the server. Create a > directory with the user name in > > config directory/logs > > Make sure that it's writable by Cyrus. Thank you for the tips. IMAP does work flawless. I did have had a deeper look in some older posts, and I did find, I did have had libsasl2-modules-ldap:amd64 2.1.27 installed. Removing that deb package, restart cyrus, IMAP still works fine, and pop3s works for apple. what a strange issue. But thanks all, works now. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut f?r ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer at cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: