Re: Little bug in 3.0.8 when calling sync_client from cyrus.conf
I can confirm this thread was just noise it works just fine, please ignore it... I had to have done something wrong the past day... you know too much work :) in a migration proccess... nights of work etc etc... :) sorry again mates, El 2019-02-18 18:14, ego...@sarenet.es escribió: > I have to do some more checks > > I think created the proccess properly as it has done in my testing env but, > it didn't run the amx8c channel log... I remember I'll try it slightly > more... and tell the real issue > > Sorry for the noise mates.. > > El 2019-02-18 18:00, ego...@sarenet.es escribió: > > Sorry I meant > > syncclient cmd="/usr/local/cyrus/sbin/sync_client -r -l -n amx8c" > > as line for launching it in START section. > > Cheers! > > El 2019-02-18 17:59, ego...@sarenet.es escribió: > > Hi mates, > > It seems cyrus.conf file config parser, does not parse properly sync_client > line when you specify a channel. It seems it ignores it. When you specify a > line like in start section : > > syncclient cmd="/usr/local/cyrus/sbin/sync_client -r -l optarg-n amx8c" > > It ignores the part "-n amx8c" > > I have taken a fast look to split_args() and proccess_section() but have not > figured where the issue could be (have not debbuged what could be > there...)... it seems the issue should be there because if you launch > sync_client from the shell it works as expected. But if you launch from > cyrus.conf it just runs : /usr/local/cyrus/sbin/sync_client -r -l > > I have workarounded from the shell but... it seemed to be something there... > > Cheers! 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: Little bug in 3.0.8 when calling sync_client from cyrus.conf
I have to do some more checks I think created the proccess properly as it has done in my testing env but, it didn't run the amx8c channel log... I remember I'll try it slightly more... and tell the real issue Sorry for the noise mates.. El 2019-02-18 18:00, ego...@sarenet.es escribió: > Sorry I meant > > syncclient cmd="/usr/local/cyrus/sbin/sync_client -r -l -n amx8c" > > as line for launching it in START section. > > Cheers! > > El 2019-02-18 17:59, ego...@sarenet.es escribió: > >> Hi mates, >> >> It seems cyrus.conf file config parser, does not parse properly sync_client >> line when you specify a channel. It seems it ignores it. When you specify a >> line like in start section : >> >> syncclient cmd="/usr/local/cyrus/sbin/sync_client -r -l optarg-n amx8c" >> >> It ignores the part "-n amx8c" >> >> I have taken a fast look to split_args() and proccess_section() but have not >> figured where the issue could be (have not debbuged what could be >> there...)... it seems the issue should be there because if you launch >> sync_client from the shell it works as expected. But if you launch from >> cyrus.conf it just runs : /usr/local/cyrus/sbin/sync_client -r -l >> >> I have workarounded from the shell but... it seemed to be something there... >> >> Cheers! 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: Little bug in 3.0.8 when calling sync_client from cyrus.conf
Sorry I meant syncclient cmd="/usr/local/cyrus/sbin/sync_client -r -l -n amx8c" as line for launching it in START section. Cheers! El 2019-02-18 17:59, ego...@sarenet.es escribió: > Hi mates, > > It seems cyrus.conf file config parser, does not parse properly sync_client > line when you specify a channel. It seems it ignores it. When you specify a > line like in start section : > > syncclient cmd="/usr/local/cyrus/sbin/sync_client -r -l optarg-n amx8c" > > It ignores the part "-n amx8c" > > I have taken a fast look to split_args() and proccess_section() but have not > figured where the issue could be (have not debbuged what could be > there...)... it seems the issue should be there because if you launch > sync_client from the shell it works as expected. But if you launch from > cyrus.conf it just runs : /usr/local/cyrus/sbin/sync_client -r -l > > I have workarounded from the shell but... it seemed to be something there... > > Cheers! 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
Little bug in 3.0.8 when calling sync_client from cyrus.conf
Hi mates, It seems cyrus.conf file config parser, does not parse properly sync_client line when you specify a channel. It seems it ignores it. When you specify a line like in start section : syncclient cmd="/usr/local/cyrus/sbin/sync_client -r -l optarg-n amx8c" It ignores the part "-n amx8c" I have taken a fast look to split_args() and proccess_section() but have not figured where the issue could be (have not debbuged what could be there...)... it seems the issue should be there because if you launch sync_client from the shell it works as expected. But if you launch from cyrus.conf it just runs : /usr/local/cyrus/sbin/sync_client -r -l I have workarounded from the shell but... it seemed to be something there... Cheers! 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
Xapian experience and Roundcube
Hi mates, After our upgrade of a little part of our mail service to 3.0.8 we tried to see if Xapian was so nice as we saw in our sandbox. Should say it certainly is :) . I though it was not working as I expected but yes, it was totally. All the problem was in the imap client side. I was using Roundcube as an Imap client for my testing (should say too I use Roundcube as my only email client). If you use Roundcube with conversation view (thread view) the search delay is far more bigger because it tries to do something for grouping the email and takes far more and it seems to do far more searches. If you see the list view instead of conversation view you see all behaviour is as expected. I have reproduced this situation... so please keep in mind this if you use Roundcube for testing all this... Cheers!! 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: another problem with conversations db
Quoting Bron Gondwana : ctl_conversationsdb -b should update the cid. BUT - if you're running old mailboxes which have a format which doesn't support saving the CID, that would for sure break things! I did run "reconstruct -V max" during the upgrade. So all mailboxes should have been updated but checking with mbexamine user/* | grep " Minor Version: 12" I found some mailboxes that where not updated correctly. I didn't see any errors during the initial upgrade, but I don't have the logs anymore so i don't know what happened. Any idea what could lead to "reconstruct -V max" failing for some mailboxes? I did rerun "reconstruct -r -V max user/LoginID" for those users, but I had two accounts where the reconstruct command didn't update the index for the INBOX of that account. Rerunning it again did update it. The rebuild of the conversation_db worked fine after the Index was updated.. Do this did resolve the endless loop in ctl_conversationsdb. I would suggest to add a check for the index version in ctl_conversationsdb I will monitor my log files if the IOERRORS will reappear, or if the wrong index version was the root of that problem too. @Bron Thanks for the help M.MengeTel.: (49) 7071/29-70316 Universität Tübingen Fax.: (49) 7071/29-5912 Zentrum für Datenverarbeitung mail: michael.me...@zdv.uni-tuebingen.de Wächterstraße 76 72074 Tübingen Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Sieve not working
Dear Egoitz and Cyrus friends,
Check if sieve is actually listening at port 2000 as well.
Wiel Offermans
wil...@offermans.rompen.nl
> On 18 Feb 2019, at 09:34, ego...@sarenet.es wrote:
>
> Hi!
>
>
>
> Could you try enabling local6.debug channel in syslog, so that you could see
> additional Sieve debugging information?. Can you then post that log?
>
>
>
> Cheers!
>
>
>
>
> El 2019-02-15 12:32, J Pilfold-Bagwell escribió:
>
>> Hi All,
>>
>> I have a Centos 7 box running with the latest default cyrus install from the
>> Centos 7 repo, i.e. cyrus-imapd-2.4.17-13.el7.x86_64 .
>>
>> The problem I have is that sieve doesn't seem to pay any attention to the
>> scripts. I have sieve running, I can successfully log in to it using
>> sieveshell, create, upload and activate scripts, but they don't seem to be
>> applied to the incoming mail. First I was trying the vacation and reject
>> scripts so checked that the correct sendmail is in use but it fails on
>> fileinto as well.
>>
>> ~~
>>
>> imapd.conf looks like this:
>>
>> [root@mail admin]# cat /etc/imapd.conf
>> configdirectory: /var/lib/imap
>> partition-default: /var/spool/imap
>> admins: cyradmin
>> sieve_admins: cyradmin
>> sievedir: /var/lib/imap/sieve
>> sendmail: /usr/sbin/sendmail
>> hashimapspool: true
>> sasl_pwcheck_method: auxprop
>> sasl_auxprop_plugin: sasldb
>> sasl_mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5
>> allowplaintext: yes
>> allowusermoves: yes
>> defaultdomain: mail
>> lmtp_downcase_rcpt: yes
>>
>> tls_cert_file: /etc/ssl/certs/cyrus-imapd/newcert.pem
>> tls_key_file: /etc/ssl/certs/cyrus-imapd/newkey.pem
>> tls_ca_file: /etc/ssl/certs/cyrus-imapd/cacert.pem
>> tls_ca_path: /etc/ssl/certscyrus-imapd
>>
>>
>>
>> cyrus.conf:
>>
>> # standard standalone server implementation
>>
>> START {
>> # do not delete this entry!
>> recovercmd="ctl_cyrusdb -r"
>>
>> # this is only necessary if using idled for IMAP IDLE
>> idledcmd="idled"
>> }
>>
>> # UNIX sockets start with a slash and are put into /var/lib/imap/sockets
>> SERVICES {
>> # add or remove based on preferences
>> imapcmd="imapd" listen="imap" prefork=5
>> imapscmd="imapd -s" listen="imaps" prefork=1
>> # pop3cmd="pop3d" listen="pop3" prefork=3
>> # pop3scmd="pop3d -s" listen="pop3s" prefork=1
>> sievecmd="timsieved" listen="0.0.0.0:2000" prefork=0
>> sieve cmd="timsieved" listen="0.0.0.0:4190" prefork=0
>> # managesieve cmd="timsieved" listen="localhost:4190" prefork=0
>>
>> # these are only necessary if receiving/exporting usenet via NNTP
>> # nntpcmd="nntpd" listen="nntp" prefork=3
>> # nntpscmd="nntpd -s" listen="nntps" prefork=1
>>
>> # at least one LMTP is required for delivery
>> # lmtpcmd="lmtpd" listen="lmtp" prefork=0
>> lmtpunixcmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1
>>
>> # this is only necessary if using notifications
>> # notifycmd="notifyd" listen="/var/lib/imap/socket/notify" proto="udp"
>> prefork=1
>> }
>>
>> EVENTS {
>> # this is required
>> checkpointcmd="ctl_cyrusdb -c" period=30
>>
>> # this is only necessary if using duplicate delivery suppression,
>> # Sieve or NNTP
>> delprunecmd="cyr_expire -E 3" at=0400
>>
>> # this is only necessary if caching TLS sessions
>> tlsprunecmd="tls_prune" at=0400
>>
>> # reindex changed mailboxes (fulltext) approximately every three hours
>> squatter1 cmd="/usr/bin/ionice -c idle /usr/lib/cyrus/bin/squatter
>> -s" period=180
>>
>> # reindex all mailboxes (fulltext) daily
>> squattera cmd="/usr/lib/cyrus/bin/squatter" at=0117
>> }
>>
>>
>>
>> sieveshell logs in fine:
>>
>> [root@mail admin]# sieveshell --authname=cyradmin --user=testuser1 localhost
>> connecting to localhost
>> Please enter your password:
>>>
>>> list
>> mail
>> sieve-test <- active script
>>
>> telnet
>>
>> Telnet login provides:
>>
>> [root@mail admin]# telnet 192.168.0.6 4190
>> Trying 192.168.0.6...
>> Connected to 192.168.0.6.
>> Escape character is '^]'.
>> "IMPLEMENTATION" "Cyrus timsieved v2.4.17-Fedora-RPM-2.4.17-13.el7"
>> "SASL" "PLAIN LOGIN CRAM-MD5 DIGEST-MD5"
>> "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags
>> notify envelope relational regex subaddress copy"
>> "STARTTLS"
>> "UNAUTHENTICATE"
>> OK
>>
>> ~
>>
>> And this works for both port 2000 and 4190 on all interfaces. LMTP is in use
>> but somewhere, they aren't talking.
>>
>> Does anyone have any troubleshooting tips they can feed me or, can anyone
>> see a glaringly obvious error I've made because it's all gone a bit wood for
>> the trees here.
>>
>> The logs
Speed-differences in listing mailboxes between 2.4 and 3.0
Hi all, we are trying to migrate our mailservers from cyrus imapd 2.4 to 3.0 and are currently looking at speed differences in listing mailboxes. Both the imap command 'list "" ""' for a user and a ctl_mboxlist -d seem to be quite a bit slower. At the moment the 3.0 environment has around around 170k mail folders listed by ctl_mboxlist -d and takes about 0.8s to list all those entries (piping the output to /dev/null). This system has no real load except for the list command). In the 2.4 environment we have 244k mail folders listed and it takes about 0.5s to list those entries (again piped to /dev/null). This system is our productive mail server and had some load to handle while listing was done. mailboxes.db is in skiplist format on the 2.4 environment. We tried twoskip and skiplist on the 3.0 environment, but it didn't change that much. Using perf record -F 99 -g ctl_mboxlist -d > /dev/null and then perf report I get for 3.0 + 41.67% 0.00% ctl_mboxlist libcyrus.so.0.0.0 [.] cyrusdb_foreach + 41.67% 0.00% ctl_mboxlist libcyrus_imap.so.0.0.0 [.] mboxlist_allmbox + 41.67% 0.00% ctl_mboxlist ctl_mboxlist[.] do_dump + 34.52% 0.00% ctl_mboxlist [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath + 22.62% 5.95% ctl_mboxlist libc-2.22.so[.] do_fcntl + 22.62% 2.38% ctl_mboxlist libc-2.22.so[.] __xstat64 ... and for 2.4 I get + 11.63% ctl_mboxlist [kernel.kallsyms] [k] kmem_cache_alloc + 9.30% ctl_mboxlist [kernel.kallsyms] [k] system_call_after_swapgs + 6.98% ctl_mboxlist [kernel.kallsyms] [k] kmem_cache_free + 6.98% ctl_mboxlist [kernel.kallsyms] [k] fcntl_setlk + 4.65% ctl_mboxlist [kernel.kallsyms] [k] fget_raw + 4.65% ctl_mboxlist [kernel.kallsyms] [k] locks_copy_lock + 4.65% ctl_mboxlist [kernel.kallsyms] [k] _raw_spin_lock + 2.33% ctl_mboxlist libc-2.11.3.so [.] __GI_strtoll_l_internal + 2.33% ctl_mboxlist libc-2.11.3.so [.] __free ... Has anyone an idea, why cyrusdb_foreach and mboxlist_allmbox is so promiment in the 3.0 recording or rather why 3.0 appears to be so much slower compared to 2.4? Felix 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: Sieve not working
Hi!
Could you try enabling local6.debug channel in syslog, so that you could
see additional Sieve debugging information?. Can you then post that log?
Cheers!
El 2019-02-15 12:32, J Pilfold-Bagwell escribió:
> Hi All,
>
> I have a Centos 7 box running with the latest default cyrus install from the
> Centos 7 repo, i.e. cyrus-imapd-2.4.17-13.el7.x86_64 .
>
> The problem I have is that sieve doesn't seem to pay any attention to the
> scripts. I have sieve running, I can successfully log in to it using
> sieveshell, create, upload and activate scripts, but they don't seem to be
> applied to the incoming mail. First I was trying the vacation and reject
> scripts so checked that the correct sendmail is in use but it fails on
> fileinto as well.
>
> ~~
>
> imapd.conf looks like this:
>
> [root@mail admin]# cat /etc/imapd.conf
> configdirectory: /var/lib/imap
> partition-default: /var/spool/imap
> admins: cyradmin
> sieve_admins: cyradmin
> sievedir: /var/lib/imap/sieve
> sendmail: /usr/sbin/sendmail
> hashimapspool: true
> sasl_pwcheck_method: auxprop
> sasl_auxprop_plugin: sasldb
> sasl_mech_list: PLAIN LOGIN CRAM-MD5 DIGEST-MD5
> allowplaintext: yes
> allowusermoves: yes
> defaultdomain: mail
> lmtp_downcase_rcpt: yes
>
> tls_cert_file: /etc/ssl/certs/cyrus-imapd/newcert.pem
> tls_key_file: /etc/ssl/certs/cyrus-imapd/newkey.pem
> tls_ca_file: /etc/ssl/certs/cyrus-imapd/cacert.pem
> tls_ca_path: /etc/ssl/certscyrus-imapd
>
>
>
> cyrus.conf:
>
> # standard standalone server implementation
>
> START {
> # do not delete this entry!
> recovercmd="ctl_cyrusdb -r"
>
> # this is only necessary if using idled for IMAP IDLE
> idledcmd="idled"
> }
>
> # UNIX sockets start with a slash and are put into /var/lib/imap/sockets
> SERVICES {
> # add or remove based on preferences
> imapcmd="imapd" listen="imap" prefork=5
> imapscmd="imapd -s" listen="imaps" prefork=1
> # pop3cmd="pop3d" listen="pop3" prefork=3
> # pop3scmd="pop3d -s" listen="pop3s" prefork=1
> sievecmd="timsieved" listen="0.0.0.0:2000" prefork=0
> sieve cmd="timsieved" listen="0.0.0.0:4190" prefork=0
> # managesieve cmd="timsieved" listen="localhost:4190" prefork=0
>
> # these are only necessary if receiving/exporting usenet via NNTP
> # nntpcmd="nntpd" listen="nntp" prefork=3
> # nntpscmd="nntpd -s" listen="nntps" prefork=1
>
> # at least one LMTP is required for delivery
> # lmtpcmd="lmtpd" listen="lmtp" prefork=0
> lmtpunixcmd="lmtpd" listen="/var/lib/imap/socket/lmtp" prefork=1
>
> # this is only necessary if using notifications
> # notifycmd="notifyd" listen="/var/lib/imap/socket/notify" proto="udp"
> prefork=1
> }
>
> EVENTS {
> # this is required
> checkpointcmd="ctl_cyrusdb -c" period=30
>
> # this is only necessary if using duplicate delivery suppression,
> # Sieve or NNTP
> delprunecmd="cyr_expire -E 3" at=0400
>
> # this is only necessary if caching TLS sessions
> tlsprunecmd="tls_prune" at=0400
>
> # reindex changed mailboxes (fulltext) approximately every three hours
> squatter1 cmd="/usr/bin/ionice -c idle /usr/lib/cyrus/bin/squatter -s"
> period=180
>
> # reindex all mailboxes (fulltext) daily
> squattera cmd="/usr/lib/cyrus/bin/squatter" at=0117
> }
>
>
>
> sieveshell logs in fine:
>
> [root@mail admin]# sieveshell --authname=cyradmin --user=testuser1 localhost
> connecting to localhost
> Please enter your password:
>
>> list
> mail
> sieve-test <- active script
>
> telnet
>
> Telnet login provides:
>
> [root@mail admin]# telnet 192.168.0.6 4190
> Trying 192.168.0.6...
> Connected to 192.168.0.6.
> Escape character is '^]'.
> "IMPLEMENTATION" "Cyrus timsieved v2.4.17-Fedora-RPM-2.4.17-13.el7"
> "SASL" "PLAIN LOGIN CRAM-MD5 DIGEST-MD5"
> "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags notify
> envelope relational regex subaddress copy"
> "STARTTLS"
> "UNAUTHENTICATE"
> OK
>
> ~
>
> And this works for both port 2000 and 4190 on all interfaces. LMTP is in use
> but somewhere, they aren't talking.
>
> Does anyone have any troubleshooting tips they can feed me or, can anyone see
> a glaringly obvious error I've made because it's all gone a bit wood for the
> trees here.
>
> The logs are huge but if you'd like to see the contents, let me know what
> you'd like it grep'd for and I'll provide.
>
> Thanks,
>
> Julian
>
> --
> This email is from Borden Grammar School Trust.
>
> This email, together with any files transmitted with it, is confidential, and
> is intended solely for the use of the individual or entity to whom it is
> addressed. Any unauthorised dissemination or copying of
