Re: odd problem with cyradm
On 2017-08-21 08:57, Egoitz Aurrekoetxea wrote: > Have you copied from another machine or similar the quota database?? > > > You should never do that No. The mailstore was transferred with imapsync many months ago. The test enviroment behaves identical, ie. the MUA'a and bin/quota with and without -f all report correct values for quota. Only thing that does not work is cyradm for reading qoutas, "set quota" works. I think I'm giving up on this one for now because it is not a problem really production-wise. Thanks, > > El 21/8/17 a las 8:42, Per olof Ljungmark escribió: >> On 2017-08-21 08:11, Egoitz Aurrekoetxea wrote: >>> Good morning, >>> >>> >>> What happens if you launch the cyradm from a remote machine?. For >>> instance in a FreeBSD with another Perl version?. Does it work?. >>> >> >> No, tried that and results are the same. Current line of thought is >> that something is not right with the quota database, I am building a >> testing setup now to verify. >> >>> >>> El 19/8/17 a las 13:18, Per olof Ljungmark escribió: >>>> Hi all, >>>> >>>> Wonder if someone can offer help. >>>> >>>> Host is FreeBSD 11.0-STABLE #0 r316644M and cyrus 2.5.11 in a jail. >>>> If I run cyradm as user cyrus (admin) and issue the lq command, usually >>>> there is a proper response at first, but subsequent commands fail. This >>>> could very well be a FreeBSD problem but I thought I'll ask here first. >>>> >>>> 1st: >>>> >>>> read(0,"lq user/\n",8192) = 15 (0xf) >>>> write(3,"8 GETQUOTA user/\r\n",24) = 24 (0x18) >>>> select(4,{ 3 },{ },0x0,0x0) = 1 (0x1) >>>> read(3,"* QUOTA user/ (STORAGE 888619 1000)\r\n8 OK >>>> Completed\r\n",4096) = 63 (0x3f) >>>> write(1," STORAGE 888619/1000",24) = 24 (0x18) >>>> write(1," (8.88619%)",11)= 11 (0xb) >>>> write(1,"\n",1) = 1 (0x1) >>>> write(1,"192.168.64.12> ",15)= 15 (0xf) >>>> >>>> and following >>>> >>>> read(0,"lq user/\n",8192) = 15 (0xf) >>>> write(3,"10 GETQUOTA user/\r\n",25)= 25 (0x19) >>>> select(4,{ 3 },{ },0x0,0x0) = 1 (0x1) >>>> read(3,"* QUOTA user/ (STORAGE 888619 1000)\r\n10 OK >>>> Completed\r\n",4096) = 64 (0x40) >>>> write(1,"192.168.64.12> ",15)= 15 (0xf) >>>> >>>> As one can see, cyradm does not write out the info, just reads it. >>>> >>>> There are no quota problems AFAICS, bin/quota and -f all works as >>>> expected and mail agents sees proper quota info, so I am inclined to >>>> think there is something fishy with cyradm or possibly something I >>>> cannot see with the quotas. >>>> >>>> Same with both quotas.db twoskip and quotalegacy. Other cyradm commands >>>> works fine. >>>> >>>> Thanks! >>>> >>>> //per >>>> >>>> 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 >>> >>> -- >>> >>> >>> sarenet >>> *Egoitz Aurrekoetxea* >>> Departamento de sistemas >>> 944 209 470 >>> Parque Tecnológico. Edificio 103 >>> 48170 Zamudio (Bizkaia) >>> ego...@sarenet.es <mailto:ego...@sarenet.es> >>> www.sarenet.es <https://www.sarenet.es> >>> >>> Antes de imprimir este correo electrónico piense si es necesario >>> hacerlo. >>> >>> >>> >>> 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 > > -- > > > sarenet > *Egoitz Aurrekoetxea* > Departamento de sistemas > 944 209 470 > Parque Tecnológico. Edificio 103 > 48170 Zamudio (Bizkaia) > ego...@sarenet.es <mailto:ego...@sarenet.es> > www.sarenet.es <https://www.sarenet.es> > > Antes de imprimir este correo electrónico piense si es necesario hacerlo. > > > > 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
Re: odd problem with cyradm
On 2017-08-21 08:11, Egoitz Aurrekoetxea wrote: Good morning, What happens if you launch the cyradm from a remote machine?. For instance in a FreeBSD with another Perl version?. Does it work?. No, tried that and results are the same. Current line of thought is that something is not right with the quota database, I am building a testing setup now to verify. El 19/8/17 a las 13:18, Per olof Ljungmark escribió: Hi all, Wonder if someone can offer help. Host is FreeBSD 11.0-STABLE #0 r316644M and cyrus 2.5.11 in a jail. If I run cyradm as user cyrus (admin) and issue the lq command, usually there is a proper response at first, but subsequent commands fail. This could very well be a FreeBSD problem but I thought I'll ask here first. 1st: read(0,"lq user/\n",8192) = 15 (0xf) write(3,"8 GETQUOTA user/\r\n",24) = 24 (0x18) select(4,{ 3 },{ },0x0,0x0) = 1 (0x1) read(3,"* QUOTA user/ (STORAGE 888619 1000)\r\n8 OK Completed\r\n",4096) = 63 (0x3f) write(1," STORAGE 888619/1000",24) = 24 (0x18) write(1," (8.88619%)",11)= 11 (0xb) write(1,"\n",1) = 1 (0x1) write(1,"192.168.64.12> ",15)= 15 (0xf) and following read(0,"lq user/\n",8192) = 15 (0xf) write(3,"10 GETQUOTA user/\r\n",25)= 25 (0x19) select(4,{ 3 },{ },0x0,0x0) = 1 (0x1) read(3,"* QUOTA user/ (STORAGE 888619 1000)\r\n10 OK Completed\r\n",4096) = 64 (0x40) write(1,"192.168.64.12> ",15)= 15 (0xf) As one can see, cyradm does not write out the info, just reads it. There are no quota problems AFAICS, bin/quota and -f all works as expected and mail agents sees proper quota info, so I am inclined to think there is something fishy with cyradm or possibly something I cannot see with the quotas. Same with both quotas.db twoskip and quotalegacy. Other cyradm commands works fine. Thanks! //per 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 -- sarenet *Egoitz Aurrekoetxea* Departamento de sistemas 944 209 470 Parque Tecnológico. Edificio 103 48170 Zamudio (Bizkaia) ego...@sarenet.es <mailto:ego...@sarenet.es> www.sarenet.es <https://www.sarenet.es> Antes de imprimir este correo electrónico piense si es necesario hacerlo. 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
odd problem with cyradm
Hi all, Wonder if someone can offer help. Host is FreeBSD 11.0-STABLE #0 r316644M and cyrus 2.5.11 in a jail. If I run cyradm as user cyrus (admin) and issue the lq command, usually there is a proper response at first, but subsequent commands fail. This could very well be a FreeBSD problem but I thought I'll ask here first. 1st: read(0,"lq user/\n",8192) = 15 (0xf) write(3,"8 GETQUOTA user/\r\n",24) = 24 (0x18) select(4,{ 3 },{ },0x0,0x0) = 1 (0x1) read(3,"* QUOTA user/ (STORAGE 888619 1000)\r\n8 OK Completed\r\n",4096) = 63 (0x3f) write(1," STORAGE 888619/1000",24) = 24 (0x18) write(1," (8.88619%)",11)= 11 (0xb) write(1,"\n",1) = 1 (0x1) write(1,"192.168.64.12> ",15)= 15 (0xf) and following read(0,"lq user/\n",8192) = 15 (0xf) write(3,"10 GETQUOTA user/\r\n",25)= 25 (0x19) select(4,{ 3 },{ },0x0,0x0) = 1 (0x1) read(3,"* QUOTA user/ (STORAGE 888619 1000)\r\n10 OK Completed\r\n",4096) = 64 (0x40) write(1,"192.168.64.12> ",15)= 15 (0xf) As one can see, cyradm does not write out the info, just reads it. There are no quota problems AFAICS, bin/quota and -f all works as expected and mail agents sees proper quota info, so I am inclined to think there is something fishy with cyradm or possibly something I cannot see with the quotas. Same with both quotas.db twoskip and quotalegacy. Other cyradm commands works fine. Thanks! //per 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: IDN - Need help
On 2017-06-19 02:31, Nicola Nye wrote: Hi Per, Your mail has generated a lot of discussion in the FastMail office about the state of Cyrus's international character support. The short answer is that you are correct: Cyrus lmtp does not offer SMTPUTF8. We have added this to the roadmap as something we want to address in the short-medium term. The plan is to write a bunch of tests and see where Cyrus has gaps, then we'll know how much work we have to do to provide support. (If anyone wants to join in this effort, let us know: we love getting more folks involved, and it means you get the features you want, faster) https://github.com/cyrusimap/cyrus-imapd/issues/1647 I am happy to help with my limited capability, anytime. //per On Sun, Jun 18, 2017, at 10:00 PM, Per olof Ljungmark wrote: I am re-posting this - would really like some help here. We need Cyrus to accept mail with international characters in sender address. If someone have experience please share, thanks! This is what Postfix reports when it tries to deliver to Cyrus: (SMTPUTF8 is required, but was not offered by host XXX [/var/imap/socket/lmtp]) (can't see anything relevant in the log from Cyrus) We want it to be delivered but I cannot figure out how - the sender address has a "ü" in it. Really grateful for a hint. Thanks, //per 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 Per olof Ljungmark CEO -- M: +46 707 50 20 46 Intersonic AB Stockholm, Sweden SE556539368201 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: IDN - Need help
On 2017-06-19 05:47, Walter H. via Info-cyrus wrote: Are you sure he's talking about the right thing as he mentioned this: "The sender in question uses a @gmail address." please first declare the part of E-mail address you are talking of ... name @ domain in case you're are talking about the 'name' part, there is not any character besides [0-9a-z\.\-_] defined (see RFC 2821) and in case you're talking about the 'domain' part, there is used Punycode, which results in the same character set I am talking about exactly what is stated below, "Cyrus lmtp does not offer SMTPUTF8". On 19.06.2017 02:31, Nicola Nye wrote: Hi Per, Your mail has generated a lot of discussion in the FastMail office about the state of Cyrus's international character support. The short answer is that you are correct: Cyrus lmtp does not offer SMTPUTF8. We have added this to the roadmap as something we want to address in the short-medium term. The plan is to write a bunch of tests and see where Cyrus has gaps, then we'll know how much work we have to do to provide support. (If anyone wants to join in this effort, let us know: we love getting more folks involved, and it means you get the features you want, faster) https://github.com/cyrusimap/cyrus-imapd/issues/1647 Cheers, Nicola On Sun, Jun 18, 2017, at 10:00 PM, Per olof Ljungmark wrote: I am re-posting this - would really like some help here. We need Cyrus to accept mail with international characters in sender address. If someone have experience please share, thanks! This is what Postfix reports when it tries to deliver to Cyrus: (SMTPUTF8 is required, but was not offered by host XXX [/var/imap/socket/lmtp]) (can't see anything relevant in the log from Cyrus) We want it to be delivered but I cannot figure out how - the sender address has a "ü" in it. Really grateful for a hint. Thanks, //per 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 Per olof Ljungmark CEO -- M: +46 707 50 20 46 Intersonic AB Stockholm, Sweden SE556539368201 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
IDN - Need help
I am re-posting this - would really like some help here. We need Cyrus to accept mail with international characters in sender address. If someone have experience please share, thanks! This is what Postfix reports when it tries to deliver to Cyrus: (SMTPUTF8 is required, but was not offered by host XXX [/var/imap/socket/lmtp]) (can't see anything relevant in the log from Cyrus) We want it to be delivered but I cannot figure out how - the sender address has a "ü" in it. Really grateful for a hint. Thanks, //per 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: IDN
On 2017-05-12 23:37, Per Olof Ljungmark wrote: Thank you for your reply - I meant exactly what I wrote - is it up to the delivery agent only (Postfix/lmpt in our case) to decide whether to accept a sender with 8bit characters in the address and if it does will cyrus digest it. Thanks /per On 12 May 2017 21:45:07 GMT+02:00, "Niels Dettenbach (Syndicat.com <http://Syndicat.com>)" <n...@syndicat.com> wrote: Am 12.05.2017 um 19:39 schrieb Per olof Ljungmark <p...@intersonic.se>: Does Cyrus Imap support IDN (International Domain Names) as sender address or is it just the delivery agent that takes care of this? Not sure, what you mean in detail. We successfully receive mail from IDN domain senders over EXIM / Cyrus, while it is typically not a good idea to have any IDN domain in an email address (lack of "standardization" / compatibility). But I’m not sure how reliable this works. Like, for instance, über or gösta. Then of course is the question if there is support for 8bit mailbox names as well. For that what i have seen - not really. In the past we recommended our users to avoid using i.e. german Umlauts within folder names, even if they seems to get „converted“ by cyrus in a working or even proper manner - there will be problems with several IMAP clients not liking this, which still have problems with that on their side… This is what Postfix reports when it tries to deliver to Cyrus: (SMTPUTF8 is required, but was not offered by host XXX [/var/imap/socket/lmtp]) (can't see anything relevant in the log from Cyrus) We want it to be delivered but I cannot figure out how - the sender address has a "ü" in it. Really grateful for a hint. Thanks, //per 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: Cyrus 2.5.10 IMAP search
On 2017-06-02 16:38, Anton via Info-cyrus wrote: Hi Robert! Unfortunately it is impossible nearest one or two years. New software like version 3 is very dangerous in production. Strange things... emails with cyrillic which was created at 2.4.17 find with IMAP search, but ones which was created after migration to 2.5.10 wasn't. Mail clients are the same and CHARSET is the same - UTF8. Im really unhappy because I have no clue what's happened. Need help. Hi, We just switched from 2.4 to 2.5 and had similar experience. Something happened with the squat database between versions but unclear what. We had to delete the cyrus.squat files and recreate them, unfortunately that also made them grow tenfold in size. That in turn, made some of them over 2GB in size and that is over the FreeBSD mmap capability. I'm still working with this, perhaps someone else can explain the differences between 2.4 and 2.5 with respect to SEARCH and squatter. 2 июня 2017 г., в 8:19 ПП, Robert Stepanek> написал(а): Hi, On Thu, Jun 1, 2017, at 12:41, Anton Shilov via Info-cyrus wrote: I've upgraded CyrusIMAP from 2.4.17 to 2.5.10 and after that has been broken IMAP search in email body russian language. Search for english works fine. Is upgrading to 3.0 an option for you? 3.0 includes both Xapian and a new character set implementation for international language search. Cheers, Robert 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
Re: squat index files - upgrade 2.4 to 2.5
On 2017-05-30 18:57, Per olof Ljungmark wrote: Hi, Can someone confirm that the squat indexes must be completely rebuilt after 2.4 -> 2.5 upgrade? We just did that and we only see new messages in the searches. We did move from skiplist to twoskip as well, supposedly this cases the problem. Or is there a better way? In the lack of response I deleted all the squat files and started squatter, should only take a few days to have it indexed... 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
squat index files - upgrade 2.4 to 2.5
Hi, Can someone confirm that the squat indexes must be completely rebuilt after 2.4 -> 2.5 upgrade? We just did that and we only see new messages in the searches. We did move from skiplist to twoskip as well, supposedly this cases the problem. Or is there a better way? Thanks, //per 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: IDN
Thank you for your reply - I meant exactly what I wrote - is it up to the delivery agent only (Postfix/lmpt in our case) to decide whether to accept a sender with 8bit characters in the address and if it does will cyrus digest it. Thanks /per On 12 May 2017 21:45:07 GMT+02:00, "Niels Dettenbach (Syndicat.com)" <n...@syndicat.com> wrote: >> >> Am 12.05.2017 um 19:39 schrieb Per olof Ljungmark ><p...@intersonic.se>: >> >> Does Cyrus Imap support IDN (International Domain Names) as sender >address or is it just the delivery agent that takes care of this? >Not sure, what you mean in detail. > >We successfully receive mail from IDN domain senders over EXIM / Cyrus, >while it is typically not a good idea to have any IDN domain in an >email address (lack of "standardization" / compatibility). But I’m not >sure how reliable this works. > >> Like, for instance, über or gösta. >> >> Then of course is the question if there is support for 8bit mailbox >names as well. >For that what i have seen - not really. > >In the past we recommended our users to avoid using i.e. german Umlauts >within folder names, even if they seems to get „converted“ by cyrus in >a working or even proper manner - there will be problems with several >IMAP clients not liking this, which still have problems with that on >their side… > > > >hth a bit >cheerioh, > > >Niels Dettenbach 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
IDN
Hi, Simple question: Does Cyrus Imap support IDN (International Domain Names) as sender address or is it just the delivery agent that takes care of this? Like, for instance, über or gösta. Then of course is the question if there is support for 8bit mailbox names as well. Thanks, //per 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: RFC6154 and upgrade to Cyrus 2.5
On 2015-10-18 12:09, Bron Gondwana wrote: > On Sat, Oct 17, 2015, at 03:25, Per olof Ljungmark wrote: >> >> On 2015-10-16 15:00, Sebastian Hagedorn wrote: >>> --On 16. Oktober 2015 14:56:32 +0200 Per olof Ljungmark >>> <p...@intersonic.se> wrote: >>> >>>> If the xlist folder flags worked in 2.4, why were they removed >>>> in 2.5? >>> >>> Because XLIST was a hack that was first introduced and then >>> deprecated by Google. Leave it to Microsoft to rely on hacks. >> >> OK, I can understand that. But it is still the way you redirect >> your OL users to have their sent mail etc ending up in the right >> place. >> >> This looks like a show stopper for for us to go to 2.5 then. > > The XLIST command still works fine, and gets the special use flags > (including magic \Inbox for XLIST but not list-return-specialuse) - > the only change is that instead of hard-coding the names for everyone > on the server, you use the specialuse annotation from the RFC to set > which folders have which special-use, allowing users with different > language folders on the same server. > > It does mean that your provisioning system needs to support creating > with a use, like this: > > TAG CREATE INBOX.Trash (USE (\Trash)) > > You could definitely create a case for improving the tooling around > that, and maybe even adding support to the autocreate options. I > think we'd be happy to backport that to 2.5. "create a case" as in enter a Bugzilla request? I wish we could support in development but that would be more than we can master. Thank you and sorry for not getting the point properly... //per 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: RFC6154 and upgrade to Cyrus 2.5
On 2015-10-14 14:32, Wolfgang Breyha wrote: > Marco wrote on 09/10/15 08:58: >> Hello, >> >>on Cyrus 2.4 I see extenstion for xlist folder flags. Folders and >> flags must be configured on imapd.conf. Great, it works! Flags are >> magically applied to all folders! >> >> If I upgrade to Cyrus 2.5 or upper, what does it happen? I see that >> Cyrus 2.5 also support "create special use", but I can't see no more >> xlist-* configs. It seems that starting from Cyrus>=2.5 only client >> can set flags during CREATE. But what does it happen to previously >> Cyrus2.4 folder-flag associations? > > With a little help from Bron I came to the following solution... > > 2.5 does not have xlist- and the only way to "migrate" it is to set it as > annotation to every mailbox. > > It is possible to set it by connecting to the backend/server as admin user > authorized as the individual user and push eg. > . SETANNOTATION INBOX.Trash "/specialuse" ("value.priv" "\Trash") > commands. Maybe I get this to work over my 2.4 frontends as well. > > On 2.5 the new SETMETADATA is available as well... > . SETMETADATA INBOX.Sent ("/private/specialuse" "Sent") If the xlist folder flags worked in 2.4, why were they removed in 2.5? //per 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: RFC6154 and upgrade to Cyrus 2.5
On 2015-10-16 15:00, Sebastian Hagedorn wrote: > --On 16. Oktober 2015 14:56:32 +0200 Per olof Ljungmark > <p...@intersonic.se> wrote: > >> If the xlist folder flags worked in 2.4, why were they removed in 2.5? > > Because XLIST was a hack that was first introduced and then deprecated > by Google. Leave it to Microsoft to rely on hacks. OK, I can understand that. But it is still the way you redirect your OL users to have their sent mail etc ending up in the right place. This looks like a show stopper for for us to go to 2.5 then. //per 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: Header CRC mismatch for mailbox
On 2015-09-26 14:01, Per olof Ljungmark wrote: > Hi all, > > In preparation for 2.4 -> 2.5 migration the testruns is mostly OK but > there are one that we cannot get over, no matter how many different > reconstructs we do: > > Running "quota -f", a handful of mailboxes returns like > > quota[56656]: Header CRC mismatch for mailbox > user.xxx.Drafts: D5DFCD33 022858D4 > > cyrus-imap 2.5.6 > OS is FreeBSD 10-STABLE > > Ideas? > Just for the sake of completion, it was operator error, the file transfer from production to test was not done properly. Sorry for the noise... 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
Header CRC mismatch for mailbox
Hi all, In preparation for 2.4 -> 2.5 migration the testruns is mostly OK but there are one that we cannot get over, no matter how many different reconstructs we do: Running "quota -f", a handful of mailboxes returns like quota[56656]: Header CRC mismatch for mailbox user.xxx.Drafts: D5DFCD33 022858D4 cyrus-imap 2.5.6 OS is FreeBSD 10-STABLE Ideas? 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
COMPRESS received NO response: Compression already active: DEFLATE
sync_client starts with compression enable (-z) but as soon as it restarts, it fails to enable it. Server side at first start syncserver[87122]: accepted connection syncserver[87122]: cmdloop(): startup syncserver[87122]: login: [client-IP] cyrus PLAIN User logged in syncserver[87122]: created decompress buffer of 4102 bytes syncserver[87122]: created compress buffer of 4102 bytes Client at first restart sync_client[49902]: sync_client RESTART succeeded sync_client[49902]: COMPRESS received NO response: Compression already active: DEFLATE sync_client[49902]: Failed to enable compression, continuing uncompressed cyrus-imap is 2.4.17 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
Replication and TLS
Hi all, Could someone please tell how to enforce encryption for replication? We authenticate users through allowplaintext: 1 sasl_mech_list: plain sasl_pwcheck_method: saslauthd Certificates are installed and SSL/TLS work fine but some of our users require that allowplaintext: yes is set. I have looked at the sync traffic and it is definitely not encrypted. So the question is, what additional steps are required to make replication use TLS as well without complicating things too much? Sorry for not being able to figure it out myself... Imapd 2.4.17 and sasl-2.1.26 and FreeBSD. //per 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: cyrus 2.3.16 ssl/tls and no deleting message on Samsung galaxy
On 12/29/11 18:54, Xavier Bestel wrote: On 12/28/2011 09:00 AM, Josef Karliak wrote: Hi there, it maybe some error or bug somewhere - we use Samsung galaxy S2, android 2.3.3. I've set it up as a imap client. When I delete a message, it disapears from the phone email list. After renewing mail box the deleted message is in the new messages again. I'm interested in a solution if you find one. We use k9mail for our droids with Cyrus and it works quite well, at least much better than the built-in client. http://code.google.com/p/k9mail/ Best, Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
scripts
Hi all, Is there a collection somewhere with helpful scripts, perl, shell, python, whatever that people developed and use for Cyrus and would be useful for a standard install, with some mods of course. Thanks, Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: squatter stops when it encounters a locked mailbox?
On 06/21/11 08:23, Bron Gondwana wrote: On Tue, Jun 21, 2011 at 02:16:07AM +0200, Per olof Ljungmark wrote: All, While migrating a few accounts from Exchange to Cyrus ( has nothing to do with the below really) and staring at log files I noted the following squatter[70553]: error locking index user/xyz: Mailbox is locked by POP server and squatter bails out without indexing the remaining mailboxes. Is this expected behaviour in 2.3.16? Sorry, POP locking in cyrus before 2.4.x is a bit of a mess. Yeah, it's expected for some value - the bailing out kind of sucks too, but I really don't want to try and fix 2.3.x any more. Bron ( particularly things like this that I changed the locking architecture specifically to avoid! ) OK, thanks, should have read more b4 posting I suppose. We have an upgrade plan in the works anyway and we would not want you to spend time on older stuff. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
squatter stops when it encounters a locked mailbox?
All, While migrating a few accounts from Exchange to Cyrus ( has nothing to do with the below really) and staring at log files I noted the following squatter[70553]: error locking index user/xyz: Mailbox is locked by POP server and squatter bails out without indexing the remaining mailboxes. Is this expected behaviour in 2.3.16? Thanks, Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: reconstruct caused mailboxes (skiplist) corruption?
On 11/12/10 00:06, Bron Gondwana wrote: On Thu, Nov 11, 2010 at 10:12:31AM +0100, Paul Dekkers wrote: Hmm, allright, so I ran it with a truss (like strace for FreeBSD) to give me a bit more verbosity, and I realized I should chown. But then: # chown cyrus 22003. # sudo -u cyrus /usr/local/cyrus/bin/reconstruct user.bla fatal error: can't read mailboxes file Confirmed: bug in FreeBSD's truss. If you must truss, always run it with a specified output file, which should avoid the bug. Otherwise a random file (mailboxes.db in this case) will get random stderr junk written to it! File a bug with FreeBSD? http://www.freebsd.org/support/bugreports.html Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Cyrus IMAPd 2.4.0 Released
On 10/13/10 18:44, Simon Matter wrote: Simon Matter wrote: On Tue, Oct 12, 2010 at 02:23:18PM -0700, David Lang wrote: (...) IIRC autocreate is on the official todo list, isn't it? That would solve it forever. Simon Excuse my ignorance, but where can I find the Official ToDo list? Thanks, -- per Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Re: Having two replica servers
Milos Gmail wrote: Hi, I have atm 1 master server and 1 replica server. All works great, but is there an option to have 1 master server and 2 replica servers ? Never tried rolling replication to two servers but here we have one rolling replication and a second that does a one-shot every four hours and then off to tape. Works like charm. -- per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Autocreate patch for 2.3.15?
Simon Matter wrote: Has anyone used the 2.3.14 autocreate patch on 2.3.15? There does not seem to be a patch for 2.3.15 on the site and I have tried using the 2.3.14 patch and it does not apply cleanly. It fails at imap/Makefile.in Find attached my version of the patch adopted for 2.3.15. Note that this is not an official patch from UOA but it is widely used because it's the patch used in my cyrus-imapd rpms. IIRC UOA is not using 2.3.x which is why they are not so fast upgrading the patches. https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3182 Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Autocreate patch for 2.3.15?
Michael Menge wrote: Quoting Simon Matter simon.mat...@invoca.ch: Has anyone used the 2.3.14 autocreate patch on 2.3.15? There does not seem to be a patch for 2.3.15 on the site and I have tried using the 2.3.14 patch and it does not apply cleanly. It fails at imap/Makefile.in Find attached my version of the patch adopted for 2.3.15. Note that this is not an official patch from UOA but it is widely used because it's the patch used in my cyrus-imapd rpms. IIRC UOA is not using 2.3.x which is why they are not so fast upgrading the patches. Is there a reason that this patch is not in the official cyrus release? I'll chime in here and and vote for it too, I know it has been discussed before but if it's not too complicated I would really like to be part of the official release. Would be interesting to have the opinion of others on the list...? Thanks, -- per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Replication rolling or cron?
Bron Gondwana wrote: On Fri, Feb 20, 2009 at 10:21:38PM -0500, Wesley Craig wrote: On 20 Feb 2009, at 12:00, Shelley Waltz wrote: I can get things working with a reboot, however, this is disruptive. Question is - should I abandon rolling and just force a replication via a cron job every 10 min? I have low volume and only 200 accounts. Does anyone have a monitoring script or a script to run sync_client by cron? Running sync_client out of cyrus.conf is a mistake. It can be started stand-alone, and that's the best way to do it. If it dies, review why it died, fix whatever problems the review reveals, and restart just sync_client. Rolling replication is better than simply running sync_client from cron. We should probably document that... Aha! We are tricked! install-replication.html: Add a line similar to the following in the STARTUP section of cyrus.conf: syncclient cmd=/usr/cyrus/bin/sync_client -r I thought I was a regular reader of the mailing list but I sure missed this one, bet there are a bunch of people running rolling replication out of cyrus.conf. That said, it's been working just fine... Cheers, -- per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Any plans for a 2.3.14?
Hi, Any plans to get a new release out soonish? We are planning for other work on the mail system and it would be nice to have the latest bugfixes and improvements done. Thanks for a great piece of software! -- per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: cyr_expire signaled to death by 11
Bron Gondwana wrote: On Thu, Sep 25, 2008 at 10:34:30AM -0400, Wesley Craig wrote: On 25 Sep 2008, at 10:04, Per olof Ljungmark wrote: No idea why, comments anyone? A limitation of some sort when expunging a lot of messages? cyr_expire [96599]: Expunged 3005 messages from user.myuser.Trash cyr_expire[96599]: expunged 4907 out of 109443 messages from 143 mailboxes master[833]: process 96599 exited, signaled to death by 11 It would be great to see a traceback. Also your imapd.conf. In particular: is delayed delete enabled? It looks like cyr_expire has finished expunging messages, and is either cleaning up delayed delete mailboxes, or purging the deliver.db. The traceback will tell for sure. I am sorry but no traces available this time. Will make preparations so if it happens again there will be one. And yes, delayed delete is enabled. imapd.conf servername: ourserver configdirectory: /var/imap defaultdomain: defaultdomain.tld virtdomains: off altnamespace: on unixhierarchysep: 1 singleinstancestore: 0 reject8bit: no quotawarn: 95 quotawarnkb: 2 lmtp_over_quota_perm_failure: 1 lmtp_strict_quota: 0 lmtp_downcase_rcpt: yes timeout: 60 imapidlepoll: 60 # Delayed expunge, see also cyrus.conf expunge_mode: delayed delete_mode: delayed deletedprefix: DELETED poptimeout: 15 popminpoll: 0 # We are using LDAP: username_tolower: on ### Sync section sync_authname: authname sync_host: IP sync_password: a password sync_repeat_interval: 5 sync_log: 1 sync_machineid: 1 sync_shutdown_file: /var/imap/shutdown-sync sync_batch_size: 1000 guid_mode: sha1 ### End sync directives ### partition-default: /var/spool/imap admins: admins autocreatequota: 50 createonpost: on autocreateinboxfolders: Sent|Trash|Drafts|Templates autosubscribeinboxfolders: Sent|Trash sieveusehomedir: false sievedir: /var/imap/sieve sieve_maxscriptsize: 64 sieve_maxscripts: 8 sieve_tls_cert_file: disabled sieve_tls_key_file: disabled sendmail: /usr/sbin/sendmail postmaster: postmaster duplicatesuppression: 0 # Note: Cyrus does *NOT* have BDB support compiled in! annotation_db: skiplist mboxlist_db: skiplist seenstate_db: skiplist subscription_db: flat tlscache_db: skiplist ptscache_db: skiplist duplicate_db: skiplist statatuscache_db: skiplist statuscache: 1 sasl_mech_list: plain sasl_pwcheck_method: saslauthd sasl_ldap_servers: localhost saslauthd_path: /var/state/saslauthd/mux sasl_log_level: 10 allowplaintext: 1 allowplainwithouttls: yes allowanonymouslogin: no tls_require_cert: 0 tls_cert_file: certfile tls_key_file: keyfile tls_ca_file: cafile notifysocket: /var/imap/socket/notify # EOF Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
cyr_expire signaled to death by 11
No idea why, comments anyone? A limitation of some sort when expunging a lot of messages? cyr_expire [96599]: Expunged 3005 messages from user.myuser.Trash cyr_expire[96599]: expunged 4907 out of 109443 messages from 143 mailboxes master[833]: process 96599 exited, signaled to death by 11 --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Problem with sync_client
Avinash Sultanpur wrote: Hi, I am in the process of setting up replication. I have setup the replica server and I have tested it successfully with sync_test. sync_host: replica ^^^ I thought this paramter needs to be hostname or IP of replica? sync_host: none Name of the host (replica running sync_server(8)) to which replication actions will be sent by sync_client(8). --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Web-cyradm and Zimbra maybe?
Leon Kolchinsky wrote: Hello All, I'm using web-cyradm (mysql frontend for virt. domains+cyrus+postfix integration) for years and very happy with it. Now we need some implementation for shared calendars (let's say calendar solution for all our users). What would you recommend? Web-cyradm and Zimbra integration? Anyone have any experience with it? How would you handle authentication issue? We use Horde here with LDAP for domains+cyrus+postfix+calendars but it works equally well with SQL. Got excellent webmail interface as well as shared calendar support. http://www.horde.org/ --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sync: DELSUB on non-existant mailbox
Wesley Craig wrote: The user's subscription DB, on either the master or the replica. But then why does ADDSUB work but not DELSUB? I've got the feeling I'm missing something here... ADD/DELSUB both works for the online replica with rolling replication... The command is sync_client -l -S IP -u -f file-with-uid's --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
sync: DELSUB on non-existant mailbox
On a sync job running from cron to the tape backup server I get this on a few mailboxes. Problem is, the ones below are nowhere to be found on master or slave. Where does sync_client fetch the mailbox info from? DELSUB username INBOX^INBOX^Drafts DELSUB username INBOX^INBOX^Sent DELSUB username INBOX^INBOX^Trash DELSUB username INBOX^Trash^INBOX^Drafts DELSUB username INBOX^Trash^INBOX^Sent DELSUB username INBOX^Trash^INBOX^Trash Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sync: DELSUB on non-existant mailbox
Wesley Craig wrote: The user's subscription DB, on either the master or the replica. Yes, indeed, it was on the replica. Thanks a lot! On 10 Aug 2008, at 10:56, Per olof Ljungmark wrote: Where does sync_client fetch the mailbox info from? DELSUB username INBOX^INBOX^Drafts DELSUB username INBOX^INBOX^Sent DELSUB username INBOX^INBOX^Trash DELSUB username INBOX^Trash^INBOX^Drafts DELSUB username INBOX^Trash^INBOX^Sent DELSUB username INBOX^Trash^INBOX^Trash Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: even more questions on replication and expire
Bron Gondwana wrote: On Tue, Jul 29, 2008 at 05:09:05PM +0200, Per olof Ljungmark wrote: Bron Gondwana wrote: On Tue, Jul 29, 2008 at 12:16:01PM +0200, Rudy Gevaert wrote: Per olof Ljungmark wrote: In the course of setting up delayed expunge on our production server I came across the following; - With delayed_expunge on the master, messages that are expunged by a user will be retained -X days on the master but immideately deleted on the replica unless it has delayed_expunge too. So if I implement delayed_expunge on the replica, do I need cyr_expire to permanently remove messages after -X days or will sync_client do that? yes That's yes to you need to run cyr_expire on the replica too. Thanks for the info. I can't help wonder if this was a firm design decision? From a user perspective it should be easier if this followed the synchronization I believe. Anyway, thanks, that was the last piece needed to finish off. I would much prefer that it was done via synchronisation as well. It's a pain from a consistency point of view. Yes indeed. This is gonna be interesting. Sorry to bugger the list with all those perhaps already answered questions but I'm on my toes here. First run of cyr_expire on a replica exhibited this: cyr_expire[5829]: Expunged 4 messages from user.user1 cyr_expire[5829]: IOERROR: reading cache record for user.user2: got bogus offset 1935894896 for 4/1617; try reconstruct master[4384]: process 5829 exited, signaled to death by 11 What does the figure 4/1617 tell me if anything? I assume the cure here is reconstruct -r -f -k user/user2 ? If I omit the -k, will I end up without cyrus.expunge and orphaned message files or will they be deleted? Thanks again all. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
even more questions on replication and expire
In the course of setting up delayed expunge on our production server I came across the following; - With delayed_expunge on the master, messages that are expunged by a user will be retained -X days on the master but immideately deleted on the replica unless it has delayed_expunge too. So if I implement delayed_expunge on the replica, do I need cyr_expire to permanently remove messages after -X days or will sync_client do that? I can imagine situations where master and replica is far from synced if one is not careful here. Sorry if this is already in the docs or list somewhere. --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: even more questions on replication and expire
Bron Gondwana wrote: On Tue, Jul 29, 2008 at 12:16:01PM +0200, Rudy Gevaert wrote: Per olof Ljungmark wrote: In the course of setting up delayed expunge on our production server I came across the following; - With delayed_expunge on the master, messages that are expunged by a user will be retained -X days on the master but immideately deleted on the replica unless it has delayed_expunge too. So if I implement delayed_expunge on the replica, do I need cyr_expire to permanently remove messages after -X days or will sync_client do that? yes That's yes to you need to run cyr_expire on the replica too. Thanks for the info. I can't help wonder if this was a firm design decision? From a user perspective it should be easier if this followed the synchronization I believe. Anyway, thanks, that was the last piece needed to finish off. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: help with cyr_expire please
Per olof Ljungmark wrote: Wesley Craig wrote: On 27 Jul 2008, at 17:36, Per olof Ljungmark wrote: Here's the entire log output from one of the events. The message: expiring messages in ... older than ... days is only given on stderr and when verbose is given. I've decided to take the opposite approach and given up trying to figure out what caused it. Instead, I ran a reconstruct across the whole spool including rebuilding the cyrus.expunge files. Then, after -E days I can test cyr_expire on a few mailboxes, if that works out ok I should be able to implement nightly pruning, with the -a switch as a security measure in case I missed annotations somewhere. I guess this could leave a few orphaned files in the spool? but some clever scripting should dig them out too. Thanks all for your help. --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
help with cyr_expire please
It seems I do not fully understand how cyr_expire works. Some background: I've set up a testing server with 2.3.12-p2 with delayed expunge and delayed delete. In cyrus.conf: delpruneandexpunge cmd=cyr_expire -D 7 -E 3 -X 7 at=0400 and it all worked as expected. Now I'm ready to implement this on our production (2.3.12-p2) machine, added the proper statements to imapd.conf expunge_mode: delayed delete_mode: delayed deletedprefix: DELETED Then i tested the following command: su cyrus -c /usr/local/cyrus/bin/cyr_expire -D 5 -E 5 -X 5 -p user.spamdump -v and to my horror it did not only delete expunged messages but a fair share of messages without any flags set: expunged 677607 out of 682456 messages from 30 mailboxes Unfortunately I have no idea why this occured, can someone shed light here? Obviously I cannot implement this now... or I'm off very quickly to South America... and, what is the difference between delpruneandexpunge and delprune? The delpruneandexpunge prefix is not documented anywhere AFAICS. Thanks! Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: help with cyr_expire please
Bron Gondwana wrote: On Sun, Jul 27, 2008 at 11:18:43AM +0200, Per olof Ljungmark wrote: It seems I do not fully understand how cyr_expire works. Some background: I've set up a testing server with 2.3.12-p2 with delayed expunge and delayed delete. In cyrus.conf: delpruneandexpunge cmd=cyr_expire -D 7 -E 3 -X 7 at=0400 and it all worked as expected. Now I'm ready to implement this on our production (2.3.12-p2) machine, added the proper statements to imapd.conf expunge_mode: delayed delete_mode: delayed deletedprefix: DELETED Then i tested the following command: su cyrus -c /usr/local/cyrus/bin/cyr_expire -D 5 -E 5 -X 5 -p user.spamdump -v and to my horror it did not only delete expunged messages but a fair share of messages without any flags set: expunged 677607 out of 682456 messages from 30 mailboxes Did you check if any live messages were actually deleted, or was it just expunged messages cleaned up? I can imagine that being the case for a spamdump user that you clean up frequently. Yes, almost all of them were live, no delete or even seen flag set. Of course we have backups both tape and offline disks but it got kinda tedious with that number of messages :-) cyradm info: {user/spamdump}: condstore: false duplicatedeliver: false lastpop: lastupdate: 27-Jul-2008 09:58:55 +0200 partition: default sharedseen: false size: 0 (there are no msg's at root level, only folders) I ran the same command on another mailbox and it behaved as I had expected, i.e. deleted messages that had sufficient days since expunge. {user/postmaster}: condstore: false duplicatedeliver: false lastpop: lastupdate: 27-Jul-2008 10:42:08 +0200 partition: default sharedseen: false size: 2022710 Tried again just now with yet another account and it behaved again fine. To sum it up, three accounts had emails removed physically that I think should not have, the first (spamdump) as it seemed randomly, the second and third up till -E days. Two other accounts faired just fine. confusion. --per (heading back to restore camp just now) Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: help with cyr_expire please
Bron Gondwana wrote: On Sun, Jul 27, 2008 at 11:18:43AM +0200, Per olof Ljungmark wrote: It seems I do not fully understand how cyr_expire works. Some background: I've set up a testing server with 2.3.12-p2 with delayed expunge and delayed delete. In cyrus.conf: delpruneandexpunge cmd=cyr_expire -D 7 -E 3 -X 7 at=0400 and it all worked as expected. Now I'm ready to implement this on our production (2.3.12-p2) machine, added the proper statements to imapd.conf expunge_mode: delayed delete_mode: delayed deletedprefix: DELETED Then i tested the following command: su cyrus -c /usr/local/cyrus/bin/cyr_expire -D 5 -E 5 -X 5 -p user.spamdump -v and to my horror it did not only delete expunged messages but a fair share of messages without any flags set: expunged 677607 out of 682456 messages from 30 mailboxes Did you check if any live messages were actually deleted, or was it just expunged messages cleaned up? I can imagine that being the case for a spamdump user that you clean up frequently. If I redo the command above with same messages /restored from backup/mailbox reconstructed/ nothing is removed so something has changed. I did a reconstruct before the first run as well FYI. Apparently there is a parameter that tells cyr_expire to delete the message and at the moment it seems it is randomly set between mailboxes. I guess I need to dig deeper... The deletion happens from the -E flag, this much I know now. From the cyr_expire man page: Cyr_expire is used to expire messages and duplicate delivery database entries. But when does it expire messages and when does it only remove duplicates? No further explanation is given furter down: −E expire-days Prune the duplicate database of entries older than expire-days. Any guesses as to what this could be if the msg itself is not marked for deletion? Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: help with cyr_expire please
Wesley Craig wrote: If you're getting a message like this: expiring messages in ... older than ... days that's the result of the /vendor/cmu/cyrus-imapd/expire annotation being set. It's controlled with the -E flag. A spam dump is a pretty typical place to find an annotation like that. none of the mailboxes had such an annotation but I'm not ready to completely rule this out yet. but if there is not such an annotation in place, exactly where does cyr_expire fetch the info on to expire or not? --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: help with cyr_expire please
Wesley Craig wrote: If you're getting a message like this: expiring messages in ... older than ... days that's the result of the /vendor/cmu/cyrus-imapd/expire annotation being set. It's controlled with the -E flag. A spam dump is a pretty typical place to find an annotation like that. Here's the entire log output from one of the events. * spamdump is actually an archive kept for a client so it is not supposed to expire anytime soon. I am the only person with direct access to it. * Notable is that in each folder, not all of the messages were deleted, just the majority of them. cyr_expire[6935]: Expunged 64610 messages from user.spamdump.archive.2005.07-12 cyr_expire[6935]: Expunged 36311 messages from user.spamdump.archive.2006.01-02 cyr_expire[6935]: Expunged 27641 messages from user.spamdump.archive.2006.03 cyr_expire[6935]: Expunged 26391 messages from user.spamdump.archive.2006.04 cyr_expire[6935]: Expunged 29141 messages from user.spamdump.archive.2006.05 cyr_expire[6935]: Expunged 31915 messages from user.spamdump.archive.2006.06 cyr_expire[6935]: Expunged 35437 messages from user.spamdump.archive.2006.07 cyr_expire[6935]: Expunged 84262 messages from user.spamdump.archive.2006.08 cyr_expire[6935]: Expunged 93719 messages from user.spamdump.archive.2006.09 cyr_expire[6935]: Expunged 72904 messages from user.spamdump.archive.2006.10 cyr_expire[6935]: Expunged 60404 messages from user.spamdump.archive.2006.11 cyr_expire[6935]: Expunged 58841 messages from user.spamdump.archive.2006.12 cyr_expire[6935]: Expunged 9178 messages from user.spamdump.archive.2007.12 cyr_expire[6935]: Expunged 2711 messages from user.spamdump.archive.Virus.2004 cyr_expire[6935]: expunged 677607 out of 682456 messages from 30 mailboxes cyr_expire[6935]: Removed 0 deleted mailboxes cyr_expire[6935]: duplicate_prune: pruning back 5 days cyr_expire[6935]: duplicate_prune: purged 0 out of 1324 entries Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: patches since 2.3.12-p2?
Alain Spineux wrote: On Fri, Jul 18, 2008 at 6:10 PM, Per olof Ljungmark [EMAIL PROTECTED] wrote: Simon Matter wrote: Hi all, Could some kind soul recommend what patches it makes sense to apply since the latest release? There are a number of them circulating on the list but I cannot figure out for sure which ones are generally safe and recommended. In particular, anything that addresses DBERROR db4: 176 lockers (We don't use Berkeley at all. Switched statuscache.db from I think there is something strange with your current config. If Cyrus-imapd doesn't use any BDB then I think there will never be any of those messages in your logs. Did you switch from BDB to skiplist and not removing some BDB stuff? To get rid of anything left you should be able to do the following: - Cleanly shutdown Cyrus - go to $configdir - mkdir db.old - mv db/* db.old/ - db.backup* db.old/ - Start Cyrus Thanks for the advice, cannot shut server down right now however. I changed statuscache.db from berkely-nosync to skiplist (to see if the error went away) but also deleted statuscache.db in between. All else has been skiplist or flat for a long long time. The error in question started to appear after upgrade from 2.3.11 to 2.3.12-p2 when I used berkely-nosync for the statuscache. Would not the db.backup* files already be in the same stae, they are recreated every 30 minutes...? This is configured in your cyrus.conf . Do you have this error every 30min ? No, randomly. They do not seem to harm much either. What puzzles me is that Cyrus was using BerkelyDB even though I had skiplist configured in imapd.conf and deleted statuscache.db in between. Is this information stored anywhere else except imapd.conf? Last night I * Recompiled Cyrus without BDB support * Changed line 1034 in ./lib/imapoptions to take skiplist as default and now finally statuscache.db is using skiplist. I wish I knew what went wrong in the first place, need to build a test setup to figure this one out, cannot fiddle more with the production unit. Now, for the original question, I applied Skiplist Readlocktracking Skiplist Safeunlock last night and I'm considering Fast Rename as well. Thank you Simon and Alan for your comments. --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
patches since 2.3.12-p2?
Hi all, Could some kind soul recommend what patches it makes sense to apply since the latest release? There are a number of them circulating on the list but I cannot figure out for sure which ones are generally safe and recommended. In particular, anything that addresses DBERROR db4: 176 lockers (We don't use Berkeley at all. Switched statuscache.db from berkeley-nosync to skiplist to see if that made it go away but it did not.) and skiplist: unlock while not locked Sorry if I'm asking the obvious... --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: patches since 2.3.12-p2?
Simon Matter wrote: Hi all, Could some kind soul recommend what patches it makes sense to apply since the latest release? There are a number of them circulating on the list but I cannot figure out for sure which ones are generally safe and recommended. In particular, anything that addresses DBERROR db4: 176 lockers (We don't use Berkeley at all. Switched statuscache.db from I think there is something strange with your current config. If Cyrus-imapd doesn't use any BDB then I think there will never be any of those messages in your logs. Did you switch from BDB to skiplist and not removing some BDB stuff? To get rid of anything left you should be able to do the following: - Cleanly shutdown Cyrus - go to $configdir - mkdir db.old - mv db/* db.old/ - db.backup* db.old/ - Start Cyrus Thanks for the advice, cannot shut server down right now however. I changed statuscache.db from berkely-nosync to skiplist (to see if the error went away) but also deleted statuscache.db in between. All else has been skiplist or flat for a long long time. The error in question started to appear after upgrade from 2.3.11 to 2.3.12-p2 when I used berkely-nosync for the statuscache. Would not the db.backup* files already be in the same stae, they are recreated every 30 minutes...? imapd.conf configdirectory: /var/imap defaultdomain: example.com virtdomains: off altnamespace: on unixhierarchysep: 1 singleinstancestore: 0 reject8bit: no quotawarn: 95 quotawarnkb: 2 lmtp_over_quota_perm_failure: 1 lmtp_strict_quota: 0 lmtp_downcase_rcpt: yes timeout: 60 # Delayed expunge, see also cyrus.conf # expunge_mode: delayed poptimeout: 15 popminpoll: 0 # We are using LDAP: username_tolower: on # username_tolower: off ### Sync section sync_authname: cyrus sync_host: IP # # sync_realm: sync_password: password sync_repeat_interval: 5 sync_log: 1 sync_machineid: 1 sync_shutdown_file: /var/imap/shutdown-sync sync_batch_size: 500 guid_mode: sha1 ### End sync directives ### partition-default: /var/spool/imap admins: cyrus admin autocreatequota: 50 createonpost: on autocreateinboxfolders: Sent|Trash|Drafts|Templates autosubscribeinboxfolders: Sent|Trash sieveusehomedir: false sievedir: /var/imap/sieve sieve_maxscriptsize: 64 sieve_maxscripts: 8 sieve_tls_cert_file: disabled sieve_tls_key_file: disabled sendmail: /usr/sbin/sendmail postmaster: postmaster duplicatesuppression: 0 annotation_db: skiplist mboxlist_db: skiplist seenstate_db: skiplist subscription_db: flat tlscache_db: skiplist ptscache_db: skiplist duplicate_db: skiplist # statuscache_db: berkeley-nosync statatuscache_db: skiplist statuscache: 1 Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: imapsync authentication failure
brian wrote: I'd like to use imapsync to migrate some mailboxes but haven't been able to authenticate to the source server with it. First, here's the failed transaction (run from a 3rd machine): -- snip -- did you try: allowplaintext: 0 Allow the use of cleartext passwords on the wire. in imapd.conf? Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: error when applying UoA patches to cyrus-imapd 2.3.11
David Newman wrote: Greetings. I'm building a 2.3.11 server from ports on FreeBSD 7.0/i386. I'm also using these two University of Athens patches: http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.11/cyrus-imapd-2.3.11-autocreate-0.10-0.diff http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.11/cyrus-imapd-2.3.11-autosieve-0.6.0.diff The following steps produced the error output pasted below. Thanks in advance for any help in understanding what's wrong. Hi, This is what I do and it worked for me: cd /usr/ports/mail/cyrus-imapd23 make clean make patch cd work/cyrus-imapd-2.3.11/ fetch http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.8/cyrus-imapd-2.3.8-autocreate-0.10-0-FreeBSD6.2.diff fetch http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.11/cyrus-imapd-2.3.11-autocreate-0.10-0.diff fetch http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.11/cyrus-imapd-2.3.11-autosieve-0.6.0.diff patch cyrus-imapd-2.3.11-autocreate-0.10-0.diff cyrus-imapd-2.3.8-autocreate-0.10-0-FreeBSD6.2.diff patch -p1 cyrus-imapd-2.3.11-autocreate-0.10-0.diff patch -p1 cyrus-imapd-2.3.11-autosieve-0.6.0.diff cd ../../ make You need to fix the line wraps above though. Good luck, --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: confused about quota -f
Simon Matter wrote: Hi all, I had to restore a users mailbox from backup which went well. After running reconstruct on the users mailbox I did a quota -f. That fixed this particular users quota but screwed another ones, used quota was at about 1/6 of actual. I had that kind of problem more than once. IIRC there were different reasons why it happened. 1) There were versions of cyrus-imapd which had somehow broken quota functionality. If you used those version you ended up with some problems. 2) Using quota -f on a somehow corrupt mailspool resulted in all kind of funny things. Fixing everything witch reconstruct first has helped, but I think I still had to run quota -f twice after it at least with certain versions of cyrus-imapd. The current 2.3.x version seem to do fine with me. A little bit of Vodoo in there yes, I should have mentioned that the version is 2.3.8. What was really odd was the fact that quota -f fixed the mailbox I had restored and then proceeded to screw the qouta on another. But does anyone know why it is not recommended to use quota -f mailbox? AFAICS it fixed the problem for me and nothing bad happened. --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
confused about quota -f
Hi all, I had to restore a users mailbox from backup which went well. After running reconstruct on the users mailbox I did a quota -f. That fixed this particular users quota but screwed another ones, used quota was at about 1/6 of actual. After several attempts with reconstruct and quota -f on this new problem that changed nothing, I finally did a quota -f user/username and that fixed it. Now, the docs says: Running quota with both the -f option and mailbox-prefix arguments is not recommended. which is why I avoided it until nothing else helped. And now I seriously wonder *why* it says so. What is the problem here? Anyone? --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Logging or verbose doesn't work
[EMAIL PROTECTED] wrote: Hy all, I'm trying to get more verbose or more logging to solve an issue with TLS. I got problem on my Freebsd 6.2. If I set in my syslog.conf local6.* /var/log/imapd.log touch the imapd.log file and restart syslog, it doesn't write anything in it. If i set the envirronement variable CYRUS_VERBOSE=5 in my loader.conf or rc.conf or in /root/.profile , it also doesn't verbose more in my /var/log/messages or /var/log/maillog Hi, I've got local6.debug /var/log/imapd.log in syslog.conf on FBSD 6 and it works... HTH, --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cannot get vacaion right..
Anders Norrbring wrote: I have a problem with relaying vacation messages from Sieve on the Cyrus IMAP server, I always get this: Dec 6 12:47:48 svea postfix/pickup[15082]: 94BD5246D: uid=96 from= Dec 6 12:47:48 svea postfix/cleanup[15090]: 94BD5246D: message-id=[EMAIL PROTECTED] Dec 6 12:47:48 svea postfix/qmgr[15081]: 94BD5246D: from=, size=644, nrcpt=1 (queue active) Dec 6 12:47:49 svea postfix/smtp[15094]: 94BD5246D: to=[EMAIL PROTECTED], relay=192.168.222.210[192.168.222.210]:25, delay=13, delays=12/0.08/0.02/0.01, dsn=5.5.3, status=bounced (host 192.168.222.210[192.168.222.210] said: 550 5.5.3 END-OF-MESSAGE: End-of-data rejected: Multi-recipient bounce (in reply to end of DATA command)) Can I please have some advice on where to look for errors? Sounds like a Postfix configuration error, try http://www.google.se/search?hl=enq=cyrus+%22Multi-recipient+bounce%22btnG=Google+Searchmeta= http://www.postfix.org/postconf.5.html#reject_multi_recipient_bounce Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Bad problems with 2.3.10 on FreeBSD
Rich Wales wrote: I recently upgraded my system to 2.3.10. My main Cyrus server runs FreeBSD 6.2, replicating to a second server running Ubuntu 7.10. I had decided to upgrade now from 2.3.9 to 2.3.10 because of replication bailing out errors in 2.3.9 that are reportedly fixed in 2.3.10. At first, I was having lots of seg-fault errors, but I added the getgrouplist() patch to auth_unix.c on my FreeBSD system, and that seemed to take care of the core-dumps. However, I started seeing other problems on the FreeBSD box -- such as ctl_cyrusdb -c checkpoint jobs hanging, and other mail delivery attempts hanging (or timing out) and piling up in my Postfix queue. I had to restart Cyrus frequently on the FreeBSD system in order to clear the logjams. I finally gave up and went back to 2.3.9 on both servers. Given the instability of 2.3.10 on my main server, I felt I had no choice. Any ideas what might have been happening? If I can't figure out how to get 2.3.10 running stably, I assume I'm going to either have to stick with 2.3.9 (and figure out some other way around the replication bailout errors until 2.3.11 comes out), or else move my main Cyrus operations onto some other platform (maybe another Ubuntu box). Did you check anything with the FBSD port maintainer? There may be patches available that cannot be commited due to the freeze. --per Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
syncserver DBERROR
Hi, After upgrade 2.3.8 - 2.3.9 i see this in the log although everything seems normal. We're using skiplist or flat for all databases so I'm assuming the below it's just because Berkeley is compiled in but not used? Is there way to get rid of the message without recompiling cyrus? /var/imap/db exists btw... Sep 15 02:43:22 miracle syncserver[36301]: DBERROR db4: no absolute path for the current directory: No such file or directory Sep 15 02:43:22 miracle syncserver[36301]: DBERROR db4: no absolute path for the current directory: No such file or directory Sep 15 02:43:22 miracle syncserver[36301]: DBERROR: dbenv-open '/var/imap/db' failed: No such file or directory Sep 15 02:43:22 miracle syncserver[36301]: DBERROR: init() on berkeley Thanks, Per olof Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: autocreate and autosieve patches for 2.3.9?
David Newman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Previously I installed cyrus 2.3.7 from FreeBSD ports (this is on FreeBSD 6.2-RELENG) and applied autocreate and autosieve patches following the instructions given here: http://www.wistful.net/wiki/Ed's_FreeBSD_Virtual_Mail_How-To However, upgrading to cyrus 2.3.9 fails. The uoa.gr site's most recent patches are for 2.3.8. When I tried applying those patches on version 2.3.9, I got the errors pasted below at the end of this message. I can successfully upgrade to 2.3.9 using the portupgrade command but not with those patches. As a result Squirrelmail login attempts return this error: Bad request: The IMAP server is reporting that plain text logins are disabled. Using CRAM-MD5 or DIGEST-MD5 authentication instead may work. Also, the use of TLS may allow SquirrelMail to login. Please contact your system administrator and report this error. At least I think I can answer this one; PLAIN is disabled by default from 2.3.9. The failed login attempt is not a result of failed patches. Also, there ought to be a switch for this in imapd.conf although I did not look. For the UOA patches, let's give them some more time... Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
syncserver crashes with Too many open files
In implementing the scheme I discussed a few days ago I came across this error. Because syncserver needs to delete all the mailboxes first, it crashes with Too many open files when the user has a lot of messages. I'm unsure if this is a cyrus or system error, but my guess is cyrus. Does syncserver take the maxfds argument? It takes a restart of the imapserver to get it back running properly. syncserver[25602]: Deleted mailbox user.xxx.yyy.zzz syncserver[25602]: Deleted mailbox user.xxx.bbb.ccc etc syncserver[25602]: IOERROR: creating quota file /var/imap/quota/m/user.xxx.NEW: Too many open files syncserver[25602]: DBERROR: error storing user.xxx: cyrusdb error syncserver[25602]: LOSTQUOTA: unable to record free of 35066 bytes in quota (null) syncserver[25602]: Deleted mailbox user.xxx.ddd.eee fff syncserver[25602]: IOERROR: opening quota file /var/imap/quota/m/user.xxx: Too many open files Thank you, Per olof Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Replication to more than one replica?
Rob Mueller wrote: Could you do it then with sync_client -S -u instead of -r to one of the relicas? -u User mode. Remaining arguments are list of users who should be replicated. Which user though? You could do all users, but that takes time. The point is that cyrus programs (lmtpd, imapd, etc) log actions that change mailboxes, so you know exactly which mailboxes need syncing. It's those logs you have to play twice to apply to two replicas to keep replication as close as possible to real time. It would be a way to keep a second offline replica for backing up to a tape archive, which is what I plan to do. I realize it's slower than the standard rolling replication but the archive is mainly for ooops I deleted that mail kind of scenario. In fact, I'm testing the setup right know with a list of all users. First run will take a while but further ones should only take a couple of minutes. Of course this setup is a workaround and it gets increasingly more difficult with the number of users, here we only have around 500 although many mailboxes are quite large. Per olof Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Replication to more than one replica?
Rob Mueller wrote: Disagree. I am replicating one server to two and have been doing it for quite a while with cyrus 2.3. Can you explain how you're doing this? If you're just running multiple sync_clients with different config files that point to different replica servers, then what you've got is broken because each sync_client will be randomly grabbing different log files, so each replica will be only getting half the required updates and will at any moment be randomly out of sync with the master. The only way you can reliably make this work is. 1. Write a process that that like sync_client, regularly grabs and atomically rotates the log files in the conf/log directory 2. That process then either: a) puts two copies of the log file in separate directories, and you have two separate sync_client processes running in rolling mode picking up the files in those directories, each sync_client with a different config file pointing to the two different replica servers b) it runs a sync_client -f on the file twice, but with separate config filess to each of the two different replica servers Could you do it then with sync_client -S -u instead of -r to one of the relicas? Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Replication to more than one replica?
Well, it's in the subject. I seem to recall a previous discussion about this but cannot find it unfortunately. Thanks, Per olof Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Replication to more than one replica?
Per olof Ljungmark wrote: Well, it's in the subject. I seem to recall a previous discussion about this but cannot find it unfortunately. OK, found the thread now, answer was: Not Possible, at least not without a fair amont of hacking. Sorry for the noise. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: squatter segfaults on large mailboxes - FreeBSD
Greg A. Woods wrote: At Fri, 20 Apr 2007 21:45:05 +0200, Per olof Ljungmark wrote: Subject: Re: squatter segfaults on large mailboxes - FreeBSD The error is Indexing mailbox user/spamdump/archive/2006/08... Segmentation fault kernel: pid 6988 (squatter), uid 60: exited on signal 11 Never mind - corrupted mailbox - sorry for the noise. It still shouldn't crash -- that's still a _major_ bug! Maybe you've got a core dump that you can analyze? At least to get a stack backtrace and a dump of the local variables, etc.? Sorry, no. Although the system itself is configured to dump cores there are no traces left behind here. This is a test setup so it is likely that I could recreate the scenario to get a dump if it is of any general interest? Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
squatter segfaults on large mailboxes - FreeBSD
Cyrus-IMAP 2.3.8 with UOA autocreate patches FreeBSD 6-STABLE The command was: su cyrus -c /usr/local/cyrus/bin/squatter -r -s -v user The error is Indexing mailbox user/spamdump/archive/2006/08... Segmentation fault kernel: pid 6988 (squatter), uid 60: exited on signal 11 There is free memory available when this happens but still it could be a system limit somehow. Anyone else out there running FreeBSD that could give a hint? Have two more boxes where this works fine on same mailbox but they do have a bit more RAM. Thanks, Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: squatter segfaults on large mailboxes - FreeBSD
The error is Indexing mailbox user/spamdump/archive/2006/08... Segmentation fault kernel: pid 6988 (squatter), uid 60: exited on signal 11 Never mind - corrupted mailbox - sorry for the noise. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
allowed characters in user names
Hi, Need to find out what characters are allowed in users mailbox names, could anyone please point me to a good source of information thanks. Per olof Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
sync_clients: all users group?
Setting up test with replication here. For initial replication I was wondering if there is a wildcard or keyword that represents all users for the -u switch to sync_client? Or I must use a file (-f) with all user names? Thanks, Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
syncserver[4715]: Fatal error: Virtual memory exhausted
After performing an initial sync of 65G worth of mailboxes the above error occurred. I kept an eye on the process initally but saw nothing worrying, then it died about halfway through the sync. Could I have hit some system limits? Vanilla FreeBSD 6.2. I'm starting off fresh now again to try to figure it out. And, while at it, here are one more sync related: * The sync_shutdown_file: switch, does it mean that the presence of this file will stop the sync process? At least that is how I intepret it... Thanks again... Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: syncserver[4715]: Fatal error: Virtual memory exhausted
Wesley Craig wrote: You probably encountered a single very large mailbox. This patch: Thanks for the patch, applied it, rebuilt and wiped out test replica config and spool. One puzzling thing so far: At first try, rolling replication started by itself, replicating the complete spool. At this eecond go, this does not occur. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
limiting unsuccessful login attempts?
Cyrus 2.2.12 saslauthd with OpenLDAP 2.3 directory FreeBSD 5.5 Does anyone know a good way to limit the number of unsuccessful login attempts? Thanks, Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: limiting unsuccessful login attempts?
Dmitriy Kirhlarov wrote: On Wed, Apr 11, 2007 at 02:15:52PM +0200, Per olof Ljungmark wrote: Cyrus 2.2.12 saslauthd with OpenLDAP 2.3 directory FreeBSD 5.5 Does anyone know a good way to limit the number of unsuccessful login attempts? slapo-ppolicy(5) pwdMaxFailure ? Yes, looks like that would do it, thanks! Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: tool for migration to cyrus ?
RJ45 wrote: Hello, I Want to migrate mailbox from imapuw to a new server with cyrus 2.3 installed. Is there any tool or scritp avaliable which I an customize to achieve my goal of migrate imap-uw mbox to cyrus mailboxes ? thanks a lot http://freshmeat.net/projects/imapsync/ Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Alternatives to websieve
I wonder if there are any alternatives to Websieve for simple management tasks. I need to delegate some administration to people who are not prepared to use cyradm and I cannot seem to get Websieve working properly, quotas are not displayed/manageable. This is 2.2.12 with users in LDAP. Thanks, --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
logo -
I was hoping to add a nice Cyrus-IMAP logo-symbol-picture to the login page of our webmail but failed to locate one, am I correct in saying there is none? If there is not I hope some artist could step forward and create one, this great piece of software deserves it! Thanks, Per olof --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
lmpt/quota behaviour
Hi all, I'm running a test setup and today I tried setting the quota for a mailbox below the current size of it to see what happened. No surprise, lmpt started responding 452 4.2.2 Over quota as it should. Then I increased the quota again so that there were plenty of room, waited for the 452 response to go away but it did not. After an hour I restarted the lmtp process and the account accepted mail again. Q: How long should it normally take for lmtp to see the changes? The change TO Over quota was registered instantly but the not the opposite apparently. Can this time be adjusted? I know the test scheme was perhaps not a real world one but should not an account be able to accept mail more or less immideately after the quota is fixed? 2.2.10 with patches from UOA. Thanks, --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: New user creation
Sasa Stupar wrote: Hi! Running FC3 with Sendmail+Cyrus. Is there any tool to automatically create a mailbox when a new system user is add? Sasa Here is one, this was posted to the list 11/24/04, I believe there is a perl script as well out there. Hello all, The UoA patches (autocreate, autosieve, rmquota and deletemailbox) are released for cyrus 2.2.10. There is a small bugfix only for the autocreate patch[1], the rest are the same as 2.2.7 , i just made sure they compiled cleanly. You can find them at the usual place : http://email.uoa.gr/projects/cyrus/ (with an updated web page. Hi Avel :)) ) For any problems don't hesitate to contact us (http://email.uoa.gr/contact/) Best regards, Aristotelis --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: NOT ABLE TO ADMINISTER MAIL BOXES WITH CYRUS-2.2.10
Peter P. Benac wrote: There is several references in the archives that state the version of cyradm must be the same as Cyrus IMAP; however since your PHP progams fails I have to wonder if you have setup all the directories with the correct permissions. You should check to make sure permissions on all the IMAP directories are as discribed in the documenation. Cyradm for imap is OK for me now bit sieve fails, I have double-checked the perms ok. [stranger] /var/spool/imap# sivtest -a cyrus localhost S: IMPLEMENTATION Cyrus timsieved v2.2.10 S: SASL PLAIN S: SIEVE fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex S: STARTTLS S: OK Please enter your password: C: AUTHENTICATE PLAIN {24+} sOmErUbBisHhErE= S: NO Authentication Error Authentication failed. generic failure Security strength factor: 0 Funnily, this is what saslauthd does: Dec 11 22:41:40 stranger saslauthd[80663]: do_auth : auth success: [user=cyrus] [service=sieve] [realm=] [mech=ldap] Dec 11 22:41:40 stranger saslauthd[80663]: do_request : response: OK Out of curiosity, do you run 2.2.10? --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Login failures
Hi list, I'm using cyrus 2.2 with saslauthd as sasl_pwcheck_method and I configured saslauthd to use ldap and shadow as it's mechanisms. My mail users are stored in a ldap directory and the cyrus user is a system user (thus in my shadow file). When I now want to use cyradm to create new mailboxes I have to login as user cyrus but somehow saslauthd doesn't fall back to shadow when it can't find the cyrus user in the ldap database and doesn't authenticate the cyrus user. Can anyone tell me how to solve this? Thanks Uli I have a similar problem, FreeBSD 5.3, Cyrus 2.2.10. Is this a clue, tried to use saslpasswd2 stranger saslpasswd2: setpass succeeded for cyrus stranger saslpasswd2: Couldn't update db The logs says everything is fine... Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=6 BIND anonymous mech=implicit ssf=0 Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=6 BIND dn= method=128 Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=6 RESULT tag=97 err=0 text= Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=7 SRCH base=o=inter-sonic.com scope=2 deref=0 filter=(uid=cyrus) Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=7 SRCH attr=dn Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=7 SEARCH RESULT tag=101 err=0 nentries=1 text= Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=8 BIND dn=uid=cyrus,o=inter-sonic.com method=128 Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=8 BIND dn=uid=cyrus,o=inter-sonic.com mech=SIMPLE ssf=0 Dec 9 23:28:31 stranger slapd[60020]: conn=2 op=8 RESULT tag=97 err=0 text= Dec 9 23:28:31 stranger saslauthd[59783]: do_auth : auth success: [user=cyrus] [service=sieve] [realm=] [mech=ldap] Dec 9 23:28:31 stranger saslauthd[59783]: do_request : response: OK --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html