Sieve when over quota

[Frank Richter]

Hi,
a user has a sieve file containing:
  redirect "[EMAIL PROTECTED]";
  keep;

It works fine, but when this user's mailbox is over quota ...:
Whenever sendmail runs its queue, a mail is sent to
"[EMAIL PROTECTED]", but as the local delivery failes, the mail
remains in sendmail's queue.

In our example this user gets a lot of mail, so this is a real problem...

Any ideas (cyrus 1.6.22)?

- Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

Re: Sieve when over quota

[Frank Richter]

>>a user has a sieve file containing:
>>  redirect "[EMAIL PROTECTED]";
>>  keep;
>>It works fine, but when this user's mailbox is over quota ...:
>>Whenever sendmail runs its queue, a mail is sent to
>>"[EMAIL PROTECTED]", but as the local delivery failes, the mail
>>remains in sendmail's queue.

> What behavior do you expect?  Desire?

Hmm, perform the redirect action only once, and try to do the keep action.
I assume this is hard to implement...

- Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

Quota problem while upgrading 1.6.22 -> 2.0.16

[Frank Richter]

Hi,
I'm in the process of migrating from cyrus-imapd 1.6.22 to 2.0.16 on a new
machine. After rsync'ing all the data and doing actions described in
install-upgrade.html I'd like to do a 'quota -f'

This leads to syslog messages for the fist N mailboxes:
  quota[14733]: mailbox 'user.XXX' has old cyrus.header

Then
 quota[14733]: DBERROR db3: Closing closed cursor
 quota[14733]: DBERROR: error closing cursor: Das Argument ist ungültig
 quota[14733]: DBERROR: error advancing: Unbekannter Fehler 617631749

Output of the quota command is:

 user.XXX: usage was 1409, now 0
  for some mailboxes, then for the rest:
 user.YYY: removed

Do I have to run 'reconstruct' for every mailbox first?

Thanks for your time,
Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

Cyrus with Exim: Sieve problems

[Frank Richter]

Hi,
I use cyrus-imap-2.0.16 with Exim 3.32 on Linux with LMTP delivery via
localhost. It works but when it comes to Sieve there's a problem.

When lmtpd detects in a user's sieve script a redirect (or vacation)
action it calls "/usr/lib/sendmail -f from-address -- to-address" and
pipes the messages to it (as I read lmtpd.c right). In my installation
this "sendmail" is exim actually.
When "to-address" is an external address it works as expected.

When "to-address" is a local address, the message is given from exim to
LMTP for this user and weird things happen: an empty line occures in the header part
- so the message is broken (no duplicate delivery suppression -dangerous-, as the
Message-Id is after the empty line!).

I detected that lmtpd gives the message to sendmail (exim in my case) with
CRLF on line ends. This causes the problem with exim - I added exim's
-dropcr flag and it works.

So, where is the problem - when is the extra line feed added? Does anyone
have an idea how to track this down? Should lmtpd pipe the message without
CRLF to the local sendmail command?

Thanks,
Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

sieve parse error, expecting `$'

[Frank Richter]

Hi,
using 2.0.16 I see sporadic Sieve errors:

Oct  2 07:20:56 pat lmtpd[21021]: sieve parse error for rink: line 3:
address '[EMAIL PROTECTED]': parse error, expecting `$'

The Sieve filter is very simple:
-
# PHP-Sieve 1.1: forward

redirect "[EMAIL PROTECTED]";
-

The result of this error: Mail is deliverd to users INBOX, not redirected.
Other deliveries for this user work (are redirected).

Any ideas? Where to debug?

TIA, Frank

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

Re: sieve parse error, expecting `$'

[Frank Richter]

> > using 2.0.16 I see sporadic Sieve errors:
> >
> > Oct  2 07:20:56 pat lmtpd[21021]: sieve parse error for rink: line 3:
> > address '[EMAIL PROTECTED]': parse error, expecting `$'
> >
> > The Sieve filter is very simple:
> > -
> > # PHP-Sieve 1.1: forward
> >
> > redirect "[EMAIL PROTECTED]";
> > -

> Do you always see this problem with the same address?

I have other local users with similar simple scripts with sporadic "parse
error, expecting `$'". And the sender addresses vary.

> Does this script always fail?

No, most of the mails for this user are redirected properly, but some
(well, 2 in the last 3 days) end with this "parse error" (sieve file unchanged).

> What happens if you check the syntax of the script by
> running it through sieve/test?

Running sieve/test with the failed message leads to:
--
./test /mailbox/a/r/user/rink/60713. /imap/sieve/r/rink/default
redirecting message '/mailbox/a/r/user/rink/60713.' to
'[EMAIL PROTECTED]'
notify msg = 'You have new mail

To: [EMAIL PROTECTED]
From: .
Subject: Re: Ausgabeumlenkung und time

Action(s) taken:
Redirected to [EMAIL PROTECTED]
' with priority = medium
-

Looks good for me...

BTW, is this sieve action no longer valid (worked in cyrus-imap 1.6.22):
redirect "address1, address2";

- Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

Re: sieve parse error, expecting `$'

[Frank Richter]

> > BTW, is this sieve action no longer valid (worked in cyrus-imap 1.6.22):
> > redirect "address1, address2";
>
> I don't think that RFC3028 allows this, but the older cmu-sieve parsers
> may have allowed it.  I'm pretty sure the current code expects only one
> address.  What kind of error do you get with multiple addresses?

The same:
Oct  2 15:02:35 pat lmtpd[19337]: sieve parse error for maiho: line 4:
address 'address1,address2': parse error, expecting `$'

I've changed all the Sieve scripts containing this wrong redirect with 2
addresses 2 days ago. Well, since then I haven't seen these parse errors
with "good sieve scripts" ...

- Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

Re: sieve parse error, expecting `$'

[Frank Richter]

So, in my point of view, there are 2 reasons for my "sporadic Sieve parse
errors":

- I had some Sieve scripts containing syntax errors.
  So it's recommended to check the syntax of all sieve scripts while
  upgrading from 1.6.X - this should be noted in doc/install-upgrade.html

- These parse errors confuse (sometimes ?) following sieve filter
  processing in (reused) lmtpd... This is a bug.

Since I fixed the wrong Sieve scripts I haven't seen any sieve parse errors.

I think it would be a good idea to install the useful sieve/test program
as sievetest program in /usr/cyrus/bin by default.

Thanks for your help,
Frank

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

Q: Disabling IMAP REFERRAL?

[Frank Richter]

Hi,
I'm setting up a standard Murder: 2 backends, 2 frontends 
(Linux, cyrus-imapd 2.3.8, Simon's RPM).

Our backend servers should not support the whole authentication mechs.
So is it possible to disable the IMAP REFERRAL feature (like for Sieve 
sieve_allowreferrals: 0)?

Regards,
Frank Richter

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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: Q: Disabling IMAP REFERRAL?

[Frank Richter]

> > I'm setting up a standard Murder: 2 backends, 2 frontends
> > (Linux, cyrus-imapd 2.3.8, Simon's RPM).
> >
> > Our backend servers should not support the whole authentication mechs.
> > So is it possible to disable the IMAP REFERRAL feature (like for Sieve
> > sieve_allowreferrals: 0)?
> 
> We do this on cyrus 2.2.x with a patch given to us. 
[...]
> You can download the patch from:
> 
>   http://oregonstate.edu/~morgan/cyrus/patches/

Thanks, I adapted it for 2.3.8:
http://www-user.tu-chemnitz.de/~fri/cyrus-imapd-patches/

IMAP REFERRALS can be disabled by /etc/imapd.conf:
proxyd_disable_mailbox_referrals: 1

Seems to work for me (tried with pine).

Regards,
Frank

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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

deliver -q brings: Over Quota

[Frank Richter]

Hi,
I'm running a standard Murder: 2 backends, 2 frontends 
(Linux, cyrus-imapd 2.3.8, Simon's RPM).

I'd like to use 'deliver -q user' on the frontend for delivering 
"Over quota messages" to users. This doesn't work, neither for 
mailboxes over quota nor for users not over quota.

backend> quota user.fri
   Quota   % Used Used Root
  25 44 110050 user.fri read(0, "From: Mail-Administrator 

frontend> strace -s 1000 deliver -q fri < /tmp/message
...
connect(3, {sa_family=AF_FILE, path="/var/lib/imap/socket/lmtp"}, 28) = 0
read(3, "220 mailbox.hrz.tu-chemnitz.de LMTP Cyrus v2.3.8-Invoca-RPM-2.3.8-5 
ready\r\n", 4096) = 75
write(3, "LHLO murder\r\n", 13) = 13
read(3, 
"250-mailbox.hrz.tu-chemnitz.de\r\n250-8BITMIME\r\n250-ENHANCEDSTATUSCODES\r\n250-PIPELINING\r\n250-SIZE\r\n250-AUTH
 EXTERNAL\r\n250 IGNOREQUOTA\r\n", 4096) = 133
write(3, "RSET\r\n", 6) = 6
write(3, "MAIL FROM: AUTH=<>\r\n", 27) = 27
read(3, "250 2.1.0 ok\r\n", 4096)   = 14
write(3, "RCPT TO: IGNOREQUOTA\r\n", 27) = 27
read(3, "250 2.1.5 ok\r\n", 4096)   = 14
write(3, "DATA\r\n", 6) = 6
read(3, "354 go ahead\r\n", 4096)   = 14
write(3, "From: Mail-Administrator <[EMAIL PROTECTED]>\r\nTo: <[EMAIL 
PROTECTED]>\r\nSubject: Ihre E-Mailbox an der TU Chemnitz\r\nDate: Mon, 2 Apr 
2007 10:25:52 +0200\r\nMessage-Id: <[EMAIL 
PROTECTED]>\r\n\r\nTest\r\n\r\n\r\n.\r\n", 243) = 243

read(3, "452 4.2.2 Over quota\r\n", 4096) = 22

write(3, "QUIT\r\n", 6) = 6
read(3, "221 2.0.0 bye\r\n", 4096)  = 15


Any ideas?

Thanks,
Frank Richter

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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: How to stop IMAP referrals?

[Frank Richter]

> Is there a way to prevent an imapd front-end from advertizing or
> performing referrals to a back-end server, and just do proxying
> instead?

See 
http://cyrusimap.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=43322


>  There are a couple of reasons that I'd prefer this.  The
> main one is that the back-end server doesn't offer the full range of
> authentication mechanisms.  Another is that Pine users complain that
> they keep getting prompted for a password whenever they send mail, if
> they have their `sent mail' folder on the IMAP server.  I'd be happier
> if the front-end would just proxy the connections to the back-end.

Regards,
Frank

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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

Frontend becomes unusable when one backend dies

[Frank Richter]

Hello,
I'm running a simple standard murder environment (v2.3.8 on Linux x86_64) 
- one frontend, two backends. If one of the two backends is down, 
then the frontend (and the whole system) becomes unavailable after some 
minutes:

On the frontend imapd's and pop3d's are started till the maximum
count (maxchild in cyrus.conf) is reached. It seems that they're still 
trying to reach the "dead" backend server.

Maybe it is a timeout issue - I let the default client_timeout 
(10 seconds) in imapd.conf. Is this value relevant for this behavior?

Thanks,
Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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: Frontend becomes unusable when one backend dies

[Frank Richter]

> I assume that the frontend is also the murder master?

No, the mupdate master is on another server.

>  Other  pertinent questions are, "How many connection do you normally get?"  

Just now this number of daemons are running:
Imapd/s: 327/458 Pop3d/s: 10/5
Theymay get up to 700 ...
The limit on imapd / imaps in cyrus.conf is 1000 each.
We get 6 - 10 IMAP/POP logins per second.

Ok, counting: 5 connections to the failing backend per second, 
10 seconds timeout ... there should be enough free daemons available.

> and "In what way is the backend 'down'?"

Machine down ... crash, not reachable (not just imapd down).
Only one IPv4 address involved.

> The client_timeout sets an alarm that interrupts the connect system  
> call.  The frontend may try more than once, tho, if the backend has  
> more than one address, e.g., IPv4 and IPv6.  Are you observing imapd  
> and pop3d on the frontend that are waiting more than client_timeout  
> to give up?  As they fail to connect, clients should log:
> 
>   connect(server-name) failed: timed out

Yes, it's here: connect(server-name) failed: Connection timed out
Ok, this is exactly 10 seconds (== client_timeout) after the login 
message.

> Another possibility is that the clients are poorly behaved, e.g.,  
> they are getting an error on SELECT, but don't close the connection  
> to the frontend.  The client_timeout is just controlling the timeout  
> of the connect from the frontend to the backend, not the duration of  
> the life of the frontend processes.  For imapd, the timeout is 30  
> *minutes*.

Oh, well. I will get a "chance" to test this situation again next week 
(kernel upgrade on backends).
I'll try with enlarging the maxchild in cyrus.conf and/or decreasing the 
client_timeout in imapd.conf.

Thanks for your ideas and help!

- Frank

> > I'm running a simple standard murder environment (v2.3.8 on Linux  
> > x86_64)
> > - one frontend, two backends. If one of the two backends is down,
> > then the frontend (and the whole system) becomes unavailable after  
> > some
> > minutes:
> >
> > On the frontend imapd's and pop3d's are started till the maximum
> > count (maxchild in cyrus.conf) is reached. It seems that they're still
> > trying to reach the "dead" backend server.
> >
> > Maybe it is a timeout issue - I let the default client_timeout
> > (10 seconds) in imapd.conf. Is this value relevant for this behavior?

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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: Emergancy..... db4: PANIC: fatal region error

[Frank Richter]

eMail Lists wrote:
>
>
> On 7/27/07, *Simon Matter* <[EMAIL PROTECTED]
> > wrote:
>
> > Very nice.. Thank you.  It looks like my deliver.db is still a
> db(x) file.
> > Can the files in db/ just be erased and when cyrus starts up it
> creats new
> > files or do the __db* files ned to be converted.  I am not sure
> how to
> > tell
> > if those are db(x) or skiplist.
>
> That's something I don't know exactly. I think there are files
> created by
> BDB and skiplist in the db/ dir.
> At least the deliver.db you should be able so simply remove it an
> it will
> be created on startup again. But make sure you configure it as
> skiplist
> before, if you want that.
>
> Simon
>
>
> OK,  I have cyrus up and running but I can not get into the user
> accounts yet... I am not to sure how to move the user directories from
> the u/a/user/xxx to the /var/spool/cyrus/mail/user/x.  I have set
> the proper parm in /etc/imap.conf and also used Debian's
> cyrus-makedirs but I was hoping it would move the user mailboxes.  Do
> I need to do that by hand or does the system do it .. it is the equiv
> to the 'makedir', something like that. 
>
> The reason is because I am getting
> cyrus/imap[13131]: IOERROR: opening
> /var/spool/cyrus/mail/user/xxx/cyrus.header: No such file or directory
>
> The user dir is not at the location yet.
Hi,

please post your actual imapd.conf and the imapd.conf that was used
before the upgrade.
>
> -Adam
> 
>
> 
> 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


-- 



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: Emergancy..... db4: PANIC: fatal region error

[Frank Richter]

> Also another thing I have noticed..
>
> The sieve scripts all needed to be reranged.  The hash directory was all
> in
> lower case but tthen it need to be upper case so I changed that by hand
> then
> I noticed cyrus was looking for the scripts all in other directories.
>
> i.e.
> Scripts for 'adam' should be under 'a' or 'A' but found in 'F' or was it
> 'L'.  I can't see the logic in that.  So I moved the 'adam' directory over
> to 'F' and i check it with websieve and all my rules are there but when
> cyrus receives mail it does not even read the rules and just posts the
> mail
> in my INBOX.  I remember I read something about sieve not being the same..
> I am going to look for that again..
>

for 'seen' use:
find /var/imap/user -name \*.seen -exec /usr/cyrus/bin/cvt_cyrusdb \{\}
flat \{\}.new skiplist \; -exec mv \{\}.new \{\} \;

taken from this link:
http://cyrusimap.web.cmu.edu/imapd/install-upgrade.html

read this carefully...;-)

cheers
> -Adam
> 
> 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


-- 
--
Frank Richter
Max-Planck-Institut für Astronomie
Königstuhl 17
D-69117 Heidelberg
mailto:[EMAIL PROTECTED]
phone: +49 6221 528267
--



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: Emergancy..... db4: PANIC: fatal region error

[Frank Richter]

> Also another thing I have noticed..
>
> The sieve scripts all needed to be reranged.  The hash directory was all
> in
> lower case but tthen it need to be upper case so I changed that by hand
> then
> I noticed cyrus was looking for the scripts all in other directories.
>
> i.e.
> Scripts for 'adam' should be under 'a' or 'A' but found in 'F' or was it
> 'L'.  I can't see the logic in that.  So I moved the 'adam' directory over
> to 'F' and i check it with websieve and all my rules are there but when
> cyrus receives mail it does not even read the rules and just posts the
> mail
> in my INBOX.  I remember I read something about sieve not being the same..
> I am going to look for that again..
>

for 'seen' use:
find /var/imap/user -name \*.seen -exec /usr/cyrus/bin/cvt_cyrusdb \{\}
flat \{\}.new skiplist \; -exec mv \{\}.new \{\} \;

taken from this link:
http://cyrusimap.web.cmu.edu/imapd/install-upgrade.html

read this carefully...;-)

cheers
> -Adam
> 
> 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


-- 
--
Frank Richter
Max-Planck-Institut für Astronomie
Königstuhl 17
D-69117 Heidelberg
mailto:[EMAIL PROTECTED]
phone: +49 6221 528267
--



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

Problems with --enable-krb5afspts

[Frank Richter]

Hi,
I'm trying to use the pt code with AFS from cyrus-imapd 2.3.9 (Simon's RPM) 
on Scientific Linux 4.4 (aka Red Hat Enterprise Linux 4.4)
with OpenAFS-1.4.4:

configure ...  --enable-krb5afspts  --with-pts=afskrb  --with-afs=/usr

Compiling ends with:

gcc -c -I.. -I./../imap -I./../lib  -I/usr/include/db4 -I/usr/include/pcre 
-I/usr/kerberos/include   -I/usr/include/et  -I/usr/include/db4 
-I/usr/include/pcre -I/usr/kerberos/include   -I/usr/include/et 
-Iyes/include -DHAVE_CONFIG_H -I/usr/include/pcre -I/usr/kerberos/include   
-O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -fPIC -I/usr/include 
afskrb.c
In file included from /usr/include/afs/ptint.h:64,
 from /usr/include/afs/ptserver.h:13,
 from afskrb.c:77:
/usr/include/ubik.h:158: error: field `versionLock' has incomplete type
make[1]: *** [afskrb.o] Error 1
make[1]: Leaving directory `/tmp/rpm-fri/BUILD/cyrus-imapd-2.3.9/ptclient'

It seems it doesn't include /usr/include/lock.h (from OpenAFS) but from 
/lib/lock.h

Any hints welcome. Does anybody use ptloader with AFS groups?

Regards,
Frank
-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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

Sieve: UTF-7 changes in 2.3.12p2?

[Frank Richter]

Hi,
we recently upgraded to cyrus-imapd-2.3.12p2 (Simon's RPM 2.3.12p2-2).

We've detected a problem with Sieve fileinto for folder names containing 
umlauts. The Sieve script is generated by Horde's Ingo module:

 # Delivery to subfolder töster (t-umlaut o-ster):
 if header :comparator "i;ascii-casemap" :contains "Subject" "ZZZ"  {
fileinto "INBOX.t&APY-ster";
 }

Delivering with lmtp shows this:
Sep 23 11:16:40 augustus lmtp[23801]: autosievefolder: autosieve_subfolder() was 
called for user fri, folder user.fri.t&-APY-ster
Sep 23 11:16:40 augustus lmtp[23801]: sieve runtime error for fri id <[EMAIL 
PROTECTED]>: Fileinto: Mailbox does not exist
Sep 23 11:16:40 augustus lmtp[23801]: duplicate_check: <[EMAIL PROTECTED]> 
user.fri 0
Sep 23 11:16:40 augustus lmtp[23801]: duplicate_check: <[EMAIL PROTECTED]> 
user.fri 0
Sep 23 11:16:40 augustus lmtp[23801]: Delivered: <[EMAIL PROTECTED]> to 
mailbox: user.fri

The mail is delivered to the INBOX (user.fri)
The delivery is tried to user.fri.t&-APY-ster, NOT user.fri.t&APY-ster

Any hints where the error occurs?

Kind Regards,
Frank
--
E-Mail: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:   Computing Services,  Chemnitz University of Technology,  Germany
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: Sieve: UTF-7 changes in 2.3.12p2?

[Frank Richter]

>> Is this a bad joke or am I missing something? Sieve scripts of most
>> non-English-speakers are intentionally broken due to a BC breaking
>> change in a bugfix release version?
>
> I'm afraid you're not missing anything. It bit us as well :(
>
> Fortunately for us, there weren't that many people with non-english folder
> names with filter rules, but for other people, this could be a pretty nasty
> change.
>
> The change is actually the correct "fix", but dropping it in without any
> large "warning" in the changelog or release announcement is pretty rough.
>
> Fixing all the existing sieve scripts shouldn't be too hard though. A perl
> 1-liner could almost do it...

But it needs to fix the tool generating the sieve scripts, too.
Like Hordes's filter module. Jan, could you give a quick hint where to 
look for this?

Frank
-- 
E-Mail: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:   Computing Services,  Chemnitz University of Technology,  Germany

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

Thunderbird with cyrus-imapd: Why chose client certificate?

[Frank Richter]

Hi,
I've a cyrus-imapd 2.3.12 installation with these options in imapd.conf

tls_cert_file: /etc/exim/etc/server.crt
tls_key_file:  /etc/exim/etc/server.key
tls_ca_file:   /etc/pki/tls/certs/ca-chain.crt
tls_require_cert: 0

SSL and STARTTLS are working fine.

I've imported a personal S/MIME certificate to thunderbird. When 
connecting to the IMAP server (using STARTTLS), thunderbird asks me to 
select a client cert, showing (translated from German):
This website (!) requires a certificate for identification ...
Chose a certificate ...

The server doesn't and shouldn't accept client certificates.
So who is wrong? My configuration, thunderbird ...

I hope somebody will enlighten me ...

Thanks,
Frank

-- 
E-Mail: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:   Computing Services,  Chemnitz University of Technology,  Germany

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: Thunderbird with cyrus-imapd: Why chose client certificate?

[Frank Richter]

> | Hi,
> | I've a cyrus-imapd 2.3.12 installation with these options in imapd.conf
> |
> | tls_cert_file: /etc/exim/etc/server.crt
> | tls_key_file:  /etc/exim/etc/server.key
> | tls_ca_file:   /etc/pki/tls/certs/ca-chain.crt
> | tls_require_cert: 0
> |
> | SSL and STARTTLS are working fine.
> |
> | I've imported a personal S/MIME certificate to thunderbird. When
> | connecting to the IMAP server (using STARTTLS), thunderbird asks me to
> | select a client cert, showing (translated from German):
> | This website (!) requires a certificate for identification ...
> | Chose a certificate ...
> |
> | The server doesn't and shouldn't accept client certificates.
> | So who is wrong? My configuration, thunderbird ...
>
> If you don't want to do client authentication, why do you set
> tls_ca_file at all ?
>
> If you really need a CA file with your server cert,
> you can include it in your tls_cert_file.
> And you only need to do that if you have your server
> cert signed by an intermediate CA and not a root
> certificate:
>
> - ---   
> |root CA| -> |intermediate| ->... |server|
> - ---   
> do not   include in   in
> include  tls_cert_filetls_cert_file

Thanks, but ...
I did this - not defining a tls_ca_file, and adding my CA chain to 
tls_cert_file. I'm getting the same behavior - Thunderbird is asking for a 
client cert. And the log entry:
   TLS server engine: No CA file specified. Client side certs may not work

Regards,
Frank
-- 
E-Mail: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:   Computing Services,  Chemnitz University of Technology,  Germany

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: Patch: add new lmtptarget annotation

[Frank Richter]

Hello Stephen,

> We use shared mailboxes quite extensively for role-based communication.
> For quite some time we've had a problem with users deleting or renaming
> mailboxes into which we deliver mail. We can, and do, use IMAP ACLs to
> dissallow users from deleting the delivery target mailbox. But when a
> user creates a child mailbox it inherits the ACLs of the parent, and the
> user is then not able to delete or rename the sub folder.

This is an issue here as well. Thanks for your solution! 
Would be a good thing to see it included in an official release.

Frank

> As a fix, I have written a patch against 2.3.16 to add a new lmtptarget
> mailbox annotation. When enabled, Cyrus won't allow the mailbox to be
> deleted or renamed. We can then set whatever ACLs we want inherited by
> child mailboxes, happy in the knowledge the user won't blat the mailbox
> and cause mail to bounce.
>
> The rationale here is that Cyrus treats user.foo with special
> significance as a delivery target, but does not do the same for shared
> mailboxes because there is no way for Cyrus to know which shared
> mailboxes we intend to deliver mail into. Using a mailbox annotation
> seems a nice way of flagging this.
>
> Patch attached. Comments welcome.

-- 
E-Mail: frank.rich...@hrz.tu-chemnitz.de  http://www.tu-chemnitz.de/~fri/
Work:   Computing Services,  Chemnitz University of Technology,  Germany

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: Move of mailboxes

[frank . richter]

we have 2 backends in a murder environment (running cyrus 2.3.11) which works.

And now for the problem:

We want to replace both backends by new hardware. Therefore the mailboxes
from both must be moved to the replacement machines.

Is there a recommended procedure to do the move? Any pointers (even to 
pitfalls) are welcome.

You should upgrade Cyrus on the new machines because there's a quota bug<  
2.3.14 (I think) where the quota on the new machine counts expunged messages or 
something similar so you end up needing to run quota -f to fix it.

For a live migration, where downtime per mailbox is minimal - add the new 
hardware into the murder as machines 3 and 4. Use XFER to move the mailboxes to 
the new machines.


... with the consequence that you need more disk space on the new server if 
you're using "singleinstancestore: 1" in /etc/imapd.conf (default), as you 
'll loose the hardlinks. In our case this would be a facor of 1.3.


Frank Richter

<>

smime.p7s
Description: S/MIME Cryptographic Signature

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

How to get rid of reserved mailboxes?

[Frank Richter]

Hello,

over the last days I've upgraded our cyrus-imapd murder (2 frontends, 5 
backends) from 2.3.16 to 2.4.17.
With the help of the experience of many list members it wasn't  "painful" 
here - I've got one new backend with 2.4, moved mailboxes from one 2.3 
server to this, upgraded the now mostly "empty" 2.3 to 2.4, and so on. Now 
it works on 2.4 smoothly - many thanks to all of you!


In this process we've got one "reserved mailbox" in a backend's mailboxes.db:
user.xyz.bla   2 j xyzlrswipkxtecda

mupdate master:
user.xyz.bla   1 mailback4.hrz.tu-chemnitz.de!j xyz   lrswipkxtecda

How to get rid of this user.xyz.bla?
I tried ctl_cyrusdb -r  - no success

Thanks in advance,
Frank Richter

--
Frank Richter
CHEMNITZ UNIVERSITY OF TECHNOLOGY
Germany

<>

smime.p7s
Description: S/MIME Kryptografische Unterschrift

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: How to get rid of reserved mailboxes?

[Frank Richter]

Am 21.12.2012 15:47, schrieb Wolfgang Breyha:

Hi!

Frank Richter wrote, on 21.12.2012 12:00:

In this process we've got one "reserved mailbox" in a backend's mailboxes.db:
user.xyz.bla   2 j xyzlrswipkxtecda

I would try to stop cyrus on the backend, then look what
ctl_mboxlist -mw


I've got this output (changed user and folder name):

Remove from MUPDATE: user.xyz.bla
mupdate said: user.xyz.blub mailback4.hrz.tu-chemnitz.de!j xyz  
lrswipkxtecda
mailboxes.db said: user.xyz.bla mailback4.hrz.tu-chemnitz.de!j xyz
lrswipkxtecda

mupdate says: user.xyz.bla mailback4.hrz.tu-chemnitz.de!j xyz lrswipkxtecda
fatal error: mupdate said not us before it said us



says. If that looks sane and only talks about the mentioned mailbox then try
ctl_mboxlist -m


No changes, same output then with ctl_mboxlist -mw


to fix it. If another "-mw" is silent then restart cyrus.

Do not try ctl_mboxlist while cyrus is running!

Usually "ctl_mboxlist -m" is executed in cyrus.conf on startup on a backend.
Do you have this entry?

START {
   
   mupdatepush  cmd="ctl_mboxlist -m"
   
}


I have:

ctl_mboxlist -m -a

I did it the hard way then:

Stop cyrus-imapd
ctl_mbloxlist -d > /tmp/mailboxes
# remove the line in /tmp/mailboxes
# move mailboxes.db away
ctl_mbloxlist -u < /tmp/mailboxes

Start cyrus-imapd

Thank you,
Frank

--
Frank RICHTER
CHEMNITZ UNIVERSITY OF TECHNOLOGY
Germany

<>

smime.p7s
Description: S/MIME Kryptografische Unterschrift

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: Delayed expunge ON by default?

[Frank Richter]

On Sat, 18 Feb 2006, Simon Matter wrote:

> My question: Did anybody using delayed expunge have any problem with it?

No, our experience is very good, too.

I run cyr_expire at 04:00, after backup is funished.
It takes about an hour:
Feb 20 05:01:06 errol cyr_expire[2687]: expunged 22206 out of 335029 messages 
from 68047 mailboxes

What is the second number - 335029? The message count in all our mailboxes
is much more than 335029 ...

Thanks to all the developers, sponsors, and you, Simon, for the RPM!

- Frank

-- 
Email: [EMAIL PROTECTED]  http://www.tu-chemnitz.de/~fri/
Work:  Computing Services,  Chemnitz University of Technology,  Germany

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

Cyrus Homepage

[Frank Richter]

Hi,

if you follow the link "Cyrus Home Page" at the bottom --> Not found

think correct adress is: http://cyrusimap.web.cmu.edu/

nice WE

-- 
-------
Frank Richter
Max-Planck-Institut für Astronomie
Königstuhl 17
D-69117 Heidelberg
mailto:[EMAIL PROTECTED]
phone: +49 6221 528267
--- 


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: Cyrus-imapd memory tuning

[Frank Richter]

On Thu, Mar 13, 2014, at 04:18 AM, David R Bosso wrote:

I've been wondering if anyone has any positive experience with using recent XFS.


We use XFS on 5 backends (virtual servers, Scientific Linux 6) with 15 
partitions altogether (500 to 800 GB each) for many years without serious 
crashes.

We had only once a problem 2008 where a xfs_repair was needed.

Regards,
Frank

--
Frank Richter
Chemnitz University of Technology, Germany
www.tu-chemnitz.de/urz



smime.p7s
Description: S/MIME Cryptographic Signature

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

LIST ... RETURN (SUBSCRIBED) doesn't list all folders

[Frank Richter]

Hi,

I'm chasing a bug regarding the wrong display of folders in the recent 
Horde/IMP Webmail frontend

-> http://bugs.horde.org/ticket/13438

IMP sends this IMAP command:

C: 4 LIST () "" (INBOX INBOX.* user.* *) RETURN (SUBSCRIBED)

If I understand RFC 5258 right, this means:
 List *all* folders returning the Subscribed status.

But, cyrus-imapd 2.4.27 in a murder environment returns*only the subscribed* 
folders, not all folders with the given status.


The Cyrus frontend sends to the backend:
List (subscribed) "" (INBOX INBOX.* user.* *) return (subscribed)

and returns just this result, as it seems.

LIST () "" (INBOX INBOX.* user.* *)
returns all folders.

This seems to be a bug. Any ideas on that?

Thanks,
Frank

--
Frank Richter
Technische Universität Chemnitz, Germany



smime.p7s
Description: S/MIME Cryptographic Signature

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: users filling up disk microsoft office outlook 2013 ?

[Frank Richter]

I'm hitting a strange issue.  A user had his mailbox grow (multiple
GB) without him noticing.

I can clean up with cyr_expire.

Multiple messages are actually the same.  It seems that the client
uploads the message and deletes it immediately.

Yesterday it filled up a partition, so I couldn't enable telemetry on
his mailbox to actually see what happened.

The client is outlook 2013.

Has anybody seen this issue before? I'm running 2.4.17


Last night ecactly this  happened on our mail server the 1st time.
One partition was filled up ...
The user was noticing "some duplicate messages", but not thousands.
I'll check up if a virus scanner is involved in our case.


--
Frank Richter
Chemnitz University of Technology, Germany



smime.p7s
Description: S/MIME Cryptographic Signature

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: FreeBSD 9.3 STABLE, cyrus-imapd 2.5.9, Listen queue overflow

[Frank Richter via Info-cyrus]

On 09.08.2016 12:35, Alexander Demin via Info-cyrus wrote:

Hello.

I have strange problem with cyrus-imapd 2.5.9, after upgrade my server
OS from FreeBSD 7 to FreeBSD 9.3 STABLE and cyrus-imapd from 2.3.x to
2.5.9. All packages reinstalled after upgrade OS.
A problem that, after a 2 or 4 or 7 days (differently) of normal work of
service cyrus-imapd, he freeze. Users can't connect to mailboxes.
In the dmesg log i see it - sonewconn: pcb 0xfe0101da7c40: Listen
queue overflow: 49 already in queue awaiting acceptance (12 occurrences).
And netstat -LAan show me it - fe0081a747a0 tcp4  49/0/32*.993.
Why queue overflow, i'm not understand. I think that a problem in the
process idled, because after stoped cyrus-imapd process
("/usr/local/etc/rc.d/imapd stop"), several processes of idled are
visible in the list of processes (ps -ax).
I run command "kiilall -9 idled" and "/usr/local/etc/rc.d/imapd start" -
service normal work.


Hello Alexander,

I'm experiencing similar behavior on a system here.
From time to time imaps-logins are no longer
possible.

After restarting cyrus it works again.
Glad to see that I'm not the only one.

My system is FreeBSD 10.2 and cyrus 2.5.x

Checking with:

netstat -LAan


shows:

tcp4  0/0/32*.993

In the cyrus performance notes, there's a topic according to increasing 
listen queues.


Now I start cyrus with "-d -l 128" which lead to:

tcp4  0/0/128*.993


Just to let you know...

best Frank




Sorry about my english, my english is hard.
Maybe someone help me.

i have provided below detailed information about system and from logs
(service cyrus-imapd freeze).

System information:
# uname -a
FreeBSD mail.spectrum.ru 9.3-STABLE FreeBSD 9.3-STABLE #0: Sat Jul  2
17:48:04 MSK 2016
old...@mail.spectrum.ru:/usr/obj/usr/src/sys/SRVKERNEL  amd64

# pkg info | grep cyrus
cyrus-imapd25-2.5.9The cyrus mail server, supporting POP3
and IMAP4 protocols
cyrus-sasl-2.1.26_12   RFC  SASL (Simple Authentication and
Security Layer)
cyrus-sasl-saslauthd-2.1.26_3  SASL authentication server for cyrus-sasl2


Conf files
# cat /usr/local/etc/cyrus.conf
START {
 idled   cmd="idled"
 recover cmd="ctl_cyrusdb -r"
#   syncclient  cmd="sync_client -r"
}

SERVICES {
 imapcmd="imapd" listen="imap" prefork=0
 imaps   cmd="imapd -s" listen="imaps" prefork=0
 pop3cmd="pop3d" listen="pop3" prefork=0
 pop3s   cmd="pop3d -s" listen="spop3" prefork=0
 sieve   cmd="timsieved" listen="sieve" prefork=0
 lmtpunixcmd="lmtpd" listen="/data/imap/socket/lmtp"
prefork=0
 smmap   cmd="smmapd" listen="/data/imap/socket/smmap"
prefork=1
#   syncclient  cmd="sync_client -r" listen="csync" prefork=1
}

EVENTS {
 checkpoint  cmd="ctl_cyrusdb -c" period=30
 delprunecmd="cyr_expire -v -E 3" at=0400
 tlsprunecmd="tls_prune" at=0400
 squattercmd="squatter -i" at=0100
}

# cat /usr/local/etc/imapd.conf
admins: cyrus
allowanonymouslogin: no
allowplaintext: yes
altnamespace: yes
annotation_db: skiplist
configdirectory: /data/imap
defaultpartition: default
duplicate_db: berkeley-nosync
imapidresponse: yes
imapmagicplus: 0
lmtp_downcase_rcpt: 1
lmtpsocket: /data/imap/socket/lmtp
mboxlist_db: skiplist
munge8bit: 0
partition-default: /data/spool/imap
postmaster: postmaster
ptscache_db: berkeley
rfc2046_strict: 0
sasl_auxprop_plugin: sasldb
sasl_log_level: 1
sasl_mech_list: plain cram-md5 digest-md5 login
sasl_pwcheck_method: auxprop
seenstate_db: skiplist
sendmail: /usr/sbin/sendmail
sievedir: /data/imap/sieve
subscription_db: flat
# sync_authname: cyrus
# sync_batch_size: 0
# sync_host: support.spectrum.ru
# sync_log: 1
# sync_password: pDkazwok
# sync_repeat_interval: 5
# sync_shutdown_file: /data/imap/socket/syncshutdown
tls_server_ca_file: /etc/ssl/imapserver.pem
tls_server_cert: /etc/ssl/imapserver.pem
tls_server_key: /etc/ssl/imapserver.pem
tls_session_timeout: 1440
unixhierarchysep: no
virtdomains: userid


Information from logs:
# netstat -LAan
Current listen queue sizes (qlen/incqlen/maxqlen)
TcpcbProto Listen Local Address
fe01257a33d0 tcp4  0/0/32 *.4190
fe0125e45b70 tcp4  0/0/32 *.995
fe00a4a38b70 tcp4  0/0/32 *.110
fe0081a747a0 tcp4  49/0/32*.993
fe00a434e000 tcp4  0/0/32 *.143
fe00a4f453d0 tcp4  0/0/10 *.587
fe0007ccd3d0 tcp4  0/0/10 *.465
fe0125e453d0 tcp4  0/0/10 *.25
fe0007ccd7a0 tcp4  0/0/512*.113
fe0007ccdb70 tcp4  0/0/512*.79
fe0007acc3d0 tcp4  0/0/128*.22
fe00079947a0 tcp4  0/0/512127.0.0.1.8891
fe00079943d0 tcp4  0/0/128*.888
fe0007acd3d0 tcp4  0/0/128127.0.0.1.953
fe0007994b70 tcp4  0/0/10 127.0.0.1.53
unix  0/0/32 /data/imap/socket/