RE: Recommended ways to test Sieve scripts

[Michael Sims]

Sorry guys, I guess my searching skills were pretty weak on this one.  For
the benefit of anyone who finds this thread, there is a test program in the
sieve/ directory of the source distribution that you can compile via "make
test".  It accepts a message file and a compiled sieve script and reports
what action would be taken on the message.  Sorry for the noise...

Michael



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

sieve script and notify

[zorg]

Hi
I want to be notify to a another adress when a mail arrive so i try this 
script and other without any success
can someone can explain me what am i doing wrong

require 
["fileinto","reject","vacation","imapflags","relational","regex","notify"];
if true {
  notify :method "mailto" :options "cy...@zorg.com"
  :message "test";

  }

thanks

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

Re: Replication & CONDSTORE [Documentation bug?]

[Bron Gondwana]

On Tue, Feb 15, 2011 at 11:03:40AM -0500, Adam Tauno Williams wrote:
> The page 
> states
> 
> 
> Note that the replication protocol currently does not have the facility
> to support the IMAP CONDSTORE extension (modification sequences). It is
> recommended that you do not try to use both CONDSTORE and replication at
> this time. The deficiencies in the replication protocol will be fixed in
> version 2.3.9. 
> 
> 
> Which seems odd in the release notes for 2.3.16.  
> 
> One *assumes* that it *was* fixed in 2.3.9?

It took a few iterations to be rock solid (some events weren't being
logged that were required to keep it fully up-to-date) but it's rock
solid in 2.3.16.

Bron ( at least - the checkreplication scripts that were running for
   months on 2.3.16 at FastMail think it is! )

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

Re: XFER problems with 2.4.6

[karavelov]

- Цитат от Simon Amor (simon.a...@daily.co.uk), на 15.02.2011
в 17:26 -   
In your example, it says .xx!user.000 for the quota, but then 
deleting ^xx!user^000 - this is the same thing that I had. After 
the XFER failed, dumping the mailboxes.db on the mupdate server 
revealed that there were duplicated mailboxes - one in each format.


The mailbox in question was xx...@.co.uk (masked of course)


cyrus@mupdate $ /usr/lib/cyrus-imapd/cyr_dbtool /var/lib/imap/ 
mailboxes.db skiplist show


^co^uk!user^xx^yy
^co^uk!user^xx^yy^Sent
^co^uk!user^xx^yy^Trash


.co.uk!user.xx^yy
.co.uk!user.xx^yy.Sent
.co.uk!user.xx^yy.Trash


I have looked in the mailbox dbs on the source and destination server but
here is no mismatch. It is not murder setup, so no mupdate server/db. We
have setup standalone IMAP stores with a nginx in front of them to redirect
the clients to the IMAP store where its mailbox resides. 


Thanks for the suggestions  


--
"Perhaps, there is no greater love than that of a
 revolutionary couple where each of the two lovers is
 ready to abandon the other at any moment if revolution
 demands it."
 Zizek
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

Re: XFER problems with 2.4.6

[karavelov]

- Цитат от Simon Amor (simon.a...@daily.co.uk), на 15.02.2011
в 17:26 -   On 15 Feb 2011, at 13:42, karave...@mail.bg wrote:


Feb 11 14:41:10 stor5 cyrus/imap[11569]: LOSTQUOTA: unable to record 
quota file .xx!user.000
Feb 11 13:23:47 stor5 cyrus/imap[11445]: Deleted mailbox ^xx! 
user^000^pay   


This looks similar to when I tried to migrate a mailbox from 2.4.6 
back to 2.3.12, there were some weird log entries that had mismatched 
'.' vs '^' substitutions. unixhierarchysep is set to on for both 
servers.   


Yes the same problem occurs for me if I try to move users from 2.4.6 back
to 2.3.16 server, but I decided that there was some compatibility problem
between versions. 


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

Re: SIEVE Scripts on a shared folder

[Jeroen van Meeuwen (Kolab Systems)]

Adam Tauno Williams wrote:
> cyrus-imapd-2.3.14-8
> 
> I've done this before, but now I'm stumped [possibly Friday induced
> brain fade].  I'm trying to set a SIEVE script on a shared folder.
> 

Now that you mention it, I find that indeed the sieve script I was trying to 
use does not work... ;-)

2.3.16 for me.

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com

pgp: 9342 BF08

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

Re: sync_client "bailing out" /sync_eatlines_unsolicited

[Patrick Boutilier]

On 02/15/2011 01:02 PM, Adam Tauno Williams wrote:

On Tue, 2011-02-15 at 11:56 -0500, Adam Tauno Williams wrote:

On Tue, 2011-02-15 at 12:44 -0400, Patrick Boutilier wrote:

On 02/15/2011 12:40 PM, Adam Tauno Williams wrote:


Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
resynchronised okay
Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
out!
Feb 15 11:34:33 sardine sync_client[22520]: Processing sync log
file /var/lib/imap/sync/log-21931 failed: Bad protocol
Feb 15 11:34:33 sardine sync_client[21931]: process 22520 exited, status
1

What does "sync_eatlines_unsolicited" signify?  Followed by
"resynchronised okay" the significance is not clear.
Attempting to "sync_client -v -l -m user.nawrot.Trash" reproduces this
error every time.

Have you tried reconstructing user.nawrot.Trash ?

Yes, multiple times. Reconstruction seems to complete without incident.
/usr/lib/cyrus-imapd/reconstruct -s -G -r user.nawrot
With and without "-s -G", the users entire tree and just .Trash.
Attempting to just replicate that use always fails.


Huh.  Doing a reconstruct *on the replica* seems to have fixed the
issue; that user's mailboxes can now be replicated.


I usually just delete the account on the replica when this happens and 
then sync from client again. That way I am guaranteed to get all the 
mail for the user.








-bash-3.2$ /usr/lib/cyrus-imapd/sync_client -v -l -u nawrot
USER nawrot
Error from do_user(nawrot): bailing out!




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


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

Re: sync_client "bailing out" /sync_eatlines_unsolicited

[Adam Tauno Williams]

On Tue, 2011-02-15 at 11:56 -0500, Adam Tauno Williams wrote: 
> On Tue, 2011-02-15 at 12:44 -0400, Patrick Boutilier wrote: 
> > On 02/15/2011 12:40 PM, Adam Tauno Williams wrote:
> > > 
> > > Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
> > > Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
> > > resynchronised okay
> > > Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
> > > out!
> > > Feb 15 11:34:33 sardine sync_client[22520]: Processing sync log
> > > file /var/lib/imap/sync/log-21931 failed: Bad protocol
> > > Feb 15 11:34:33 sardine sync_client[21931]: process 22520 exited, status
> > > 1
> > > 
> > > What does "sync_eatlines_unsolicited" signify?  Followed by
> > > "resynchronised okay" the significance is not clear.
> > > Attempting to "sync_client -v -l -m user.nawrot.Trash" reproduces this
> > > error every time.
> > Have you tried reconstructing user.nawrot.Trash ?
> Yes, multiple times. Reconstruction seems to complete without incident.
> /usr/lib/cyrus-imapd/reconstruct -s -G -r user.nawrot
> With and without "-s -G", the users entire tree and just .Trash.
> Attempting to just replicate that use always fails.

Huh.  Doing a reconstruct *on the replica* seems to have fixed the
issue; that user's mailboxes can now be replicated.

> -bash-3.2$ /usr/lib/cyrus-imapd/sync_client -v -l -u nawrot
> USER nawrot
> Error from do_user(nawrot): bailing out!



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

Re: sync_client "bailing out" /sync_eatlines_unsolicited

[Patrick Boutilier]

On 02/15/2011 12:56 PM, Adam Tauno Williams wrote:

On Tue, 2011-02-15 at 12:44 -0400, Patrick Boutilier wrote:

On 02/15/2011 12:40 PM, Adam Tauno Williams wrote:


Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
resynchronised okay
Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
out!
Feb 15 11:34:33 sardine sync_client[22520]: Processing sync log
file /var/lib/imap/sync/log-21931 failed: Bad protocol
Feb 15 11:34:33 sardine sync_client[21931]: process 22520 exited, status
1

What does "sync_eatlines_unsolicited" signify?  Followed by
"resynchronised okay" the significance is not clear.
Attempting to "sync_client -v -l -m user.nawrot.Trash" reproduces this
error every time.

Have you tried reconstructing user.nawrot.Trash ?


Yes, multiple times. Reconstruction seems to complete without incident.

/usr/lib/cyrus-imapd/reconstruct -s -G -r user.nawrot

With and without "-s -G", the users entire tree and just .Trash.

Attempting to just replicate that use always fails.

-bash-3.2$ /usr/lib/cyrus-imapd/sync_client -v -l -u nawrot
USER nawrot
Error from do_user(nawrot): bailing out!



Problem could be on the sync_server end. Anything in the logs on that end?








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


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

Re: sync_client "bailing out" /sync_eatlines_unsolicited

[Adam Tauno Williams]

On Tue, 2011-02-15 at 12:44 -0400, Patrick Boutilier wrote: 
> On 02/15/2011 12:40 PM, Adam Tauno Williams wrote:
> > 
> > Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
> > Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
> > resynchronised okay
> > Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
> > out!
> > Feb 15 11:34:33 sardine sync_client[22520]: Processing sync log
> > file /var/lib/imap/sync/log-21931 failed: Bad protocol
> > Feb 15 11:34:33 sardine sync_client[21931]: process 22520 exited, status
> > 1
> > 
> > What does "sync_eatlines_unsolicited" signify?  Followed by
> > "resynchronised okay" the significance is not clear.
> > Attempting to "sync_client -v -l -m user.nawrot.Trash" reproduces this
> > error every time.
> Have you tried reconstructing user.nawrot.Trash ?

Yes, multiple times. Reconstruction seems to complete without incident.

/usr/lib/cyrus-imapd/reconstruct -s -G -r user.nawrot

With and without "-s -G", the users entire tree and just .Trash.

Attempting to just replicate that use always fails.

-bash-3.2$ /usr/lib/cyrus-imapd/sync_client -v -l -u nawrot
USER nawrot
Error from do_user(nawrot): bailing out!



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

Re: sync_client "bailing out" /sync_eatlines_unsolicited

[Patrick Boutilier]

On 02/15/2011 12:40 PM, Adam Tauno Williams wrote:


Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
resynchronised okay
Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
out!
Feb 15 11:34:33 sardine sync_client[22520]: Processing sync log
file /var/lib/imap/sync/log-21931 failed: Bad protocol
Feb 15 11:34:33 sardine sync_client[21931]: process 22520 exited, status
1


What does "sync_eatlines_unsolicited" signify?  Followed by
"resynchronised okay" the significance is not clear.

If I try to sync the specific folder I think causes this condition I
see:


Feb 15 11:34:25 sardine sync_client[22520]: MAILBOX user.nawrot
Feb 15 11:34:25 sardine sync_client[22520]: MAILBOX user.nawrot.Trash
Feb 15 11:34:25 sardine sync_client[22520]: MAILBOXES: Invalid
unsolicited response type 1 from server: 0
Feb 15 11:34:25 sardine sync_client[22520]: Discarding:
 ()
Feb 15 11:34:25 sardine sync_client[22520]: Discarding: 156594 1
 ()
...
eb 15 11:34:33 sardine sync_client[22520]: Discarding: 158342 1
 (NonJunk)
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 158343 1
 (NonJunk)
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 158344 1
f0a15e97d5f2aa9367fc2c69d823f9abff65691a (NonJunk)
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 5f1789d349660dd5
user.nawrot.sent-mail "nawrot lrswipcda steve lrswipcda group:cis
lrwipkxtecda cyrus lcda adam lrkxtecda " 1231424981 60 1 1
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 58 1
 ()
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 60 1
 ()
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: INBOX.Archives
Feb 15 11:34:33 sardine sync_client[22520]: Discarding:
INBOX.Archives.2010
Feb 15 11:34:33 sardine sync_client[22520]: Discarding:
INBOX.Archives.2011
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: INBOX.CIS
...
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
resynchronised okay
Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
out!


Attempting to "sync_client -v -l -m user.nawrot.Trash" reproduces this
error every time.




Have you tried reconstructing user.nawrot.Trash ?












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


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

sync_client "bailing out" /sync_eatlines_unsolicited

[Adam Tauno Williams]

Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
resynchronised okay
Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
out!
Feb 15 11:34:33 sardine sync_client[22520]: Processing sync log
file /var/lib/imap/sync/log-21931 failed: Bad protocol
Feb 15 11:34:33 sardine sync_client[21931]: process 22520 exited, status
1 


What does "sync_eatlines_unsolicited" signify?  Followed by
"resynchronised okay" the significance is not clear.

If I try to sync the specific folder I think causes this condition I
see:


Feb 15 11:34:25 sardine sync_client[22520]: MAILBOX user.nawrot
Feb 15 11:34:25 sardine sync_client[22520]: MAILBOX user.nawrot.Trash
Feb 15 11:34:25 sardine sync_client[22520]: MAILBOXES: Invalid
unsolicited response type 1 from server: 0
Feb 15 11:34:25 sardine sync_client[22520]: Discarding:
 ()
Feb 15 11:34:25 sardine sync_client[22520]: Discarding: 156594 1
 ()
...
eb 15 11:34:33 sardine sync_client[22520]: Discarding: 158342 1
 (NonJunk)
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 158343 1
 (NonJunk)
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 158344 1
f0a15e97d5f2aa9367fc2c69d823f9abff65691a (NonJunk)
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 5f1789d349660dd5
user.nawrot.sent-mail "nawrot lrswipcda steve lrswipcda group:cis
lrwipkxtecda cyrus lcda adam lrkxtecda " 1231424981 60 1 1
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 58 1
 ()
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: 60 1
 ()
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: INBOX.Archives
Feb 15 11:34:33 sardine sync_client[22520]: Discarding:
INBOX.Archives.2010
Feb 15 11:34:33 sardine sync_client[22520]: Discarding:
INBOX.Archives.2011
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: INBOX.CIS
...
Feb 15 11:34:33 sardine sync_client[22520]: Discarding: User completed
Feb 15 11:34:33 sardine sync_client[22520]: sync_eatlines_unsolicited():
resynchronised okay
Feb 15 11:34:33 sardine sync_client[22520]: Error in do_sync(): bailing
out!


Attempting to "sync_client -v -l -m user.nawrot.Trash" reproduces this
error every time.


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

Replication & CONDSTORE [Documentation bug?]

[Adam Tauno Williams]

The page 
states


Note that the replication protocol currently does not have the facility
to support the IMAP CONDSTORE extension (modification sequences). It is
recommended that you do not try to use both CONDSTORE and replication at
this time. The deficiencies in the replication protocol will be fixed in
version 2.3.9. 


Which seems odd in the release notes for 2.3.16.  

One *assumes* that it *was* fixed in 2.3.9?


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

Re: SIEVE Scripts on a shared folder

[Adam Tauno Williams]

On Tue, 2011-02-15 at 09:50 -0600, Dan White wrote: 
> On 15/02/11 09:58 -0500, Adam Tauno Williams wrote:
> >cyrus-imapd-2.3.14-8
> >Now when I send the message to the folder no IOERROR. Woo Hoo! ... only
> >the script doesn't seem to do anything.
> Are you sending the message via LMTP or IMAP? IMAP does not support sieve.

LMTP via Postfix [via SMTP].  I am e-mailing a message to the folder.



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

Re: SIEVE Scripts on a shared folder

[Dan White]

On 15/02/11 09:58 -0500, Adam Tauno Williams wrote:
>cyrus-imapd-2.3.14-8
>
>I've done this before, but now I'm stumped [possibly Friday induced
>brain fade].  I'm trying to set a SIEVE script on a shared folder.
>
>
>I annotate the folder in cyradm -
>
>sardine.mormail.com> mboxcfg departments.cis sieve deletetestsubject
>sardine.mormail.com> info departments.cis
>{departments.cis}:
>  condstore: false
>  duplicatedeliver: false
>  lastpop:
>  lastupdate:  7-Jan-2011 15:58:37 -0500
>  partition: default
>  pop3newuidl: true
>  sharedseen: false
>  sieve: deletetestsubject
>  size: 82176367
>

>So I upload the script -
>
>sieveshell --user=cyrus --authname=cyrus 
>> put deleteTestSubject
>> quit

>Now when I send the message to the folder no IOERROR. Woo Hoo! ... only
>the script doesn't seem to do anything.

Are you sending the message via LMTP or IMAP? IMAP does not support sieve.

-- 
Dan White

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

IOERROR during sync_client -m [Was: Adding a 2.3.x replica]

[Adam Tauno Williams]

> >> >> Is there a recommended Method for bringing up a new replica for an
> >> >> active master (with 1.4 million messages in its mailstore)
> >> If the replica is running, you have to run the following command
> >> to initialise the replica:
> >> sync_client -u -f userlist.txt
> >> userlist.txt is a file containing all users.
> >> This can be done while the master and rolling replication
> >> is running
> > I assume the same can be applied for "-m" mode.
> > 1. Dump a mailbox list using:
> >   /usr/lib/cyrus-imapd/ctl_mboxlist -d | cut -f1 > /tmp/mailbox_list.txt
> > 2.) Run the sync for that mailbox list
> >   /usr/lib/cyrus-imapd/sync_client  -m -v -l -f /tmp/mailbox_list.tx
> this will not bring the sieve scripts in sync. The rolling replication
> will sync them if they change, but it may take a very long time till
> all scripts have been changed by the users.
> > This seems to just-die; but is working if I break-up the mailbox list
> > into units-of-work [rather than all at once].
> did you see errors in your logfiles?

I do see it bailing out on certain mailboxes


Feb 15 10:42:28 sardine sync_client[20764]: MAILBOX
user.cconklin.Monticello
Feb 15 10:42:28 sardine sync_client[20764]: MAILBOX
user.cconklin.Nienhuis - Quotes
Feb 15 10:42:28 sardine sync_client[20764]: IOERROR: opening message
file 10 of user.cbaumann.Sent: No such file or directory
Feb 15 10:42:28 sardine sync_client[20764]: UPLOAD received BAD
response: Syntax error in Append at item 10: Invalid flags or missing
message
Feb 15 10:42:28 sardine sync_client[20764]: Error in do_mailboxes():
bailing out!


I assume this represents an inconsistency in the mailstore of the
master.


I put together a little shell script to page through a dump of the
mailbox list.


#!/bin/bash

START=0
END=`wc -l /tmp/mailbox_list.txt | cut -f1 -d" "`
COUNTER=$START
while [ "$COUNTER" -lt "$END" ];
  do
COUNTER=`expr $COUNTER + 100`
head -$COUNTER /tmp/mailbox_list.txt | tail -100
> /tmp/mailbox_list_50.txt
echo "Starting replication at index $COUNTER : "`head
-1 /tmp/mailbox_list_50.txt`
echo "Ending replication at "`tail -1 /tmp/mailbox_list_50.txt`
/usr/lib/cyrus-imapd/sync_client  -m -v -l
-f /tmp/mailbox_list_50.txt
RESULT="$?"
echo "Sync exit status is: $RESULT"
if [ "$RESULT" -ne "0" ]
 then
   echo "NON-ZERO EXIT STATUS"
   tail -100 /var/log/maillog
   exit
 fi
COUNTER=`expr $COUNTER + 100`
  done



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

Re: Adding a 2.3.x replica [Documentation Bug]

[Michael Menge]

Quoting Adam Tauno Williams :


On Tue, 2011-02-15 at 13:28 +0100, Michael Menge wrote:

Quoting Adam Tauno Williams :
> On Mon, 2011-02-14 at 16:37 -0500, Adam Tauno Williams wrote:
>> Looking at
>>  


> Documentation Bug:
> "Add a line similar to the following in the STARTUP section of
> cyrus.conf"
> There is no "STARTUP" section, it is the "START" section.
> START {
>   # do not delete this entry!
>   recover   cmd="ctl_cyrusdb -r"
>   # this is only necessary if using idled for IMAP IDLE
>   idled cmd="idled"
>   # Start the replication client (this is the master)
>   syncclient   cmd="sync_client -r"
If this method is used the master will wait till the syncclient can
reach the replica. This can cause unnessesary delays it the replica
is not running or can't be reached.


Won't this also mean that the sync will stop, and not resume, if
sync_client abends/stops/aborts?



Proceses in the STRAT section will not be restarted if the stop.
You need to monitor the sync_client and/or the synclog.



>> Reading the quote -
>> "Rolling" replication means that the "master" server continuously
>> synchonizes itself with the replica.
>> - I take this to mean that the master continuously *pushes* changes to
>> the replica [secondary]?
> Yep.
>> Is there a recommended/suggested value for sync_repeat_interval other
>> than the default of "1"?
> ?
>> Is there a recommended Method for bringing up a new replica for an
>> active master (with 1.4 million messages in its mailstore)
If the replica is running, you have to run the following command
to initialise the replica:
sync_client -u -f userlist.txt
userlist.txt is a file containing all users.
This can be done while the master and rolling replication
is running.


I assume the same can be applied for "-m" mode.

1.) Dump a mailbox list using:
  /usr/lib/cyrus-imapd/ctl_mboxlist -d | cut -f1 > /tmp/mailbox_list.txt
2.) Run the sync for that mailbox list
  /usr/lib/cyrus-imapd/sync_client  -m -v -l -f /tmp/mailbox_list.txt



this will not bring the sieve scripts in sync. The rolling replication
will sync them if they change, but it may take a very long time till
all scripts have been changed by the users.



This seems to just-die; but is working if I break-up the mailbox list
into units-of-work [rather than all at once].



did you see errors in your logfiles?






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

smime.p7s
Description: S/MIME Signatur

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

Re: XFER problems with 2.4.6

[Simon Amor]

On 15 Feb 2011, at 13:42, karave...@mail.bg wrote:
>
> Feb 11 14:41:10 stor5 cyrus/imap[11569]: LOSTQUOTA: unable to record  
> quota file .xx!user.000
> Feb 11 13:23:47 stor5 cyrus/imap[11445]: Deleted mailbox ^xx! 
> user^000^pay


This looks similar to when I tried to migrate a mailbox from 2.4.6  
back to 2.3.12, there were some weird log entries that had mismatched  
'.' vs '^' substitutions. unixhierarchysep is set to on for both  
servers.

In your example, it says .xx!user.000 for the quota, but then  
deleting ^xx!user^000 - this is the same thing that I had. After  
the XFER failed, dumping the mailboxes.db on the mupdate server  
revealed that there were duplicated mailboxes - one in each format.

The mailbox in question was xx...@.co.uk (masked of course)

cyrus@mupdate $ /usr/lib/cyrus-imapd/cyr_dbtool /var/lib/imap/ 
mailboxes.db skiplist show

^co^uk!user^xx^yy
^co^uk!user^xx^yy^Sent
^co^uk!user^xx^yy^Trash

.co.uk!user.xx^yy
.co.uk!user.xx^yy.Sent
.co.uk!user.xx^yy.Trash

The two different formats were associated with different servers, the  
first set was shown as being on the 2.3.12 server where it had failed  
to move it, tried to back out the move, and failed with that too. The  
second (correctly formatted) ones were shown as being on the 2.4.6  
server. The mailbox contents were actually still on the 2.4.6 server  
so it was a matter of removing the broken entries using cyr_dbtool.

This was 2.4.6 -> 2.3.12 so maybe there's some discrepancy in what  
2.4.6 sends vs what 2.3 and 2.4 expect?

Simon
-- 
Simon Amor


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

Re: custom notifications

[Jeroen van Meeuwen (Kolab Systems)]

Wolfgang Hennerbichler wrote:
> On Tue, Feb 15, 2011 at 07:33:41AM -0500, Dave McMurtrie wrote:
> > > * does notifyd need to be running in order to make the notify-socket
> > > readable, or is the notify-socket filled by the cyrus-master process?
> > > * where would I find instructions on that?
> > 
> > You want to set the notify_external option in imapd.conf and point that
> > at a program (script, binary, whatever) that you write.  notifyd will
> > fork/exec your program and pass it -c, -p, -u and -m command line
> > arguments.  Your program can then to whatever custom notification you
> > want it to.
> > 
> > This was added in the 2.4.x series.  The imapd.conf option is documented
> > in the imapd.conf manpage ...
> 
> thanks! too bad I do still have 2.2 running (debian squeeze), and I was too
> lazy for now to find a good package maintainer or compile by myself. So I
> guess I'm stuck by now.
> 

I have some vanilla packaging effort for Debian ongoing on 
http://git.kolabsys.com/apt/cyrus-imapd/log/?h=cyrus-imapd-2.4, in case you're 
interested.

Though I'm dealing with a small backlog, compiled packages may be found at 
http://mirror.kolabsys.com/pub/debian/kolab-3.0/pool/development/c/cyrus-
imapd/

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com

pgp: 9342 BF08

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

SIEVE Scripts on a shared folder

[Adam Tauno Williams]

cyrus-imapd-2.3.14-8

I've done this before, but now I'm stumped [possibly Friday induced
brain fade].  I'm trying to set a SIEVE script on a shared folder.


I annotate the folder in cyradm -

sardine.mormail.com> mboxcfg departments.cis sieve deletetestsubject
sardine.mormail.com> info departments.cis
{departments.cis}:
  condstore: false
  duplicatedeliver: false
  lastpop:  
  lastupdate:  7-Jan-2011 15:58:37 -0500
  partition: default
  pop3newuidl: true
  sharedseen: false
  sieve: deletetestsubject
  size: 82176367

Then when I send a message to the folder I see in the message log -

IOERROR: fstating sieve
script /var/lib/imap/sieve/global/deletetestsubject.bc: No such file or
directory

Awesome!  It is looking for the script.  The message is delivered to the
folder [of course, there is no script]

So I upload the script -

sieveshell --user=cyrus --authname=cyrus 
> put deleteTestSubject
> quit

And, it is there -
[root@sardine ~]# ls -l /var/lib/imap/sieve/global/deletetestsubject.bc
-rw--- 1 cyrus mail 124 Jan  7
15:57 /var/lib/imap/sieve/global/deletetestsubject.bc

Now when I send the message to the folder no IOERROR. Woo Hoo! ... only
the script doesn't seem to do anything.

[root@sardine ~]#
cat /var/lib/imap/sieve/global/deletetestsubject.script 
require ["imapflags"];
if header :comparator "i;ascii-casemap" :is "Subject" "TEST"  {
addflag "\\Deleted";
keep;
stop;
}

I sent a message with a Subject of "TEST".

What am I missing?


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

RE: Adding a 2.3.x replica [Documentation Bug]

[Simpson, John R]

> -Original Message-
> From: info-cyrus-bounces+john_simpson=reyrey@lists.andrew.cmu.edu 
> [mailto:info-
> cyrus-bounces+john_simpson=reyrey@lists.andrew.cmu.edu] On Behalf Of 
> Michael
> Menge
> Sent: Tuesday, February 15, 2011 7:29 AM
> To: awill...@whitemice.org
> Cc: cyrus-users
> Subject: Re: Adding a 2.3.x replica [Documentation Bug]
> 
> Quoting Adam Tauno Williams :
> 
> > On Mon, 2011-02-14 at 16:37 -0500, Adam Tauno Williams wrote:
> >> Looking at
> >> 
> >
> > Documentation Bug:
> >
> > "Add a line similar to the following in the STARTUP section of
> > cyrus.conf"
> >
> > There is no "STARTUP" section, it is the "START" section.
> >
> > START {
> >   # do not delete this entry!
> >   recover   cmd="ctl_cyrusdb -r"
> >   # this is only necessary if using idled for IMAP IDLE
> >   idled cmd="idled"
> >   # Start the replication client (this is the master)
> >   syncclient   cmd="sync_client -r"
> > }
> >
> 
> If this method is used the master will wait till the syncclient can
> reach the replica. This can cause unnessesary delays it the replica
> is not running or can't be reached.
> 
> 

You can avoid the delays with "sync_client -r -o" (-o == try once
and exit).  You'll need an external method to make sure that 
sync_client is running and to process any abandoned replication 
logs in configdirectory/sync (usually /var/lib/imap/sync).  You 
should be able to find an old version of Brom's monitorsync.pl for
inspiration.

John

> 
> >> Reading the quote -
> >> "Rolling" replication means that the "master" server continuously
> >> synchonizes itself with the replica.
> >> - I take this to mean that the master continuously *pushes* changes to
> >> the replica [secondary]?
> >
> > Yep.
> >
> >> Is there a recommended/suggested value for sync_repeat_interval other
> >> than the default of "1"?
> >
> > ?
> 
> >> Is there a recommended Method for bringing up a new replica for an
> >> active master (with 1.4 million messages in its mailstore)
> >
> 
> If the replica is running, you have to run the following command
> to initialise the replica:
> 
> sync_client -u -f userlist.txt
> 
> userlist.txt is a file containing all users.
> This can be done while the master and rolling replication
> is running.
> 
> 
> 
> 
> 
> 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



John Simpson 
Senior Software Engineer, I. T. Engineering and Operations

Reynolds and Reynolds 
One Reynolds Way | Kettering, Ohio 45430 
office 937.485.8304 
john_simp...@reyrey.com 

MAKING BUSINESS BETTER. 

NOTE: The information contained in this e-mail is personal and confidential and 
may be protected by the attorney-client privilege and/or the work product 
doctrine. It is for the sole use of the intended recipient. Any review, 
reliance, or distribution by others or forwarding without express permission is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.

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

Re: Adding a 2.3.x replica [Documentation Bug]

[Adam Tauno Williams]

On Tue, 2011-02-15 at 13:28 +0100, Michael Menge wrote: 
> Quoting Adam Tauno Williams :
> > On Mon, 2011-02-14 at 16:37 -0500, Adam Tauno Williams wrote:
> >> Looking at
> >> 
> > Documentation Bug:
> > "Add a line similar to the following in the STARTUP section of
> > cyrus.conf"
> > There is no "STARTUP" section, it is the "START" section.
> > START {
> >   # do not delete this entry!
> >   recover   cmd="ctl_cyrusdb -r"
> >   # this is only necessary if using idled for IMAP IDLE
> >   idled cmd="idled"
> >   # Start the replication client (this is the master)
> >   syncclient   cmd="sync_client -r"
> If this method is used the master will wait till the syncclient can
> reach the replica. This can cause unnessesary delays it the replica
> is not running or can't be reached.

Won't this also mean that the sync will stop, and not resume, if
sync_client abends/stops/aborts?

> >> Reading the quote -
> >> "Rolling" replication means that the "master" server continuously
> >> synchonizes itself with the replica.
> >> - I take this to mean that the master continuously *pushes* changes to
> >> the replica [secondary]?
> > Yep.
> >> Is there a recommended/suggested value for sync_repeat_interval other
> >> than the default of "1"?
> > ?
> >> Is there a recommended Method for bringing up a new replica for an
> >> active master (with 1.4 million messages in its mailstore)
> If the replica is running, you have to run the following command
> to initialise the replica:
> sync_client -u -f userlist.txt
> userlist.txt is a file containing all users.
> This can be done while the master and rolling replication
> is running.

I assume the same can be applied for "-m" mode.

1.) Dump a mailbox list using: 
  /usr/lib/cyrus-imapd/ctl_mboxlist -d | cut -f1 > /tmp/mailbox_list.txt
2.) Run the sync for that mailbox list 
  /usr/lib/cyrus-imapd/sync_client  -m -v -l -f /tmp/mailbox_list.txt

This seems to just-die; but is working if I break-up the mailbox list
into units-of-work [rather than all at once].


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

Re: LMTP bounces with invalid chars in MAIL FROM adress

[Simon Matter]

> On Mon, 2011-02-14 at 17:11 +0100, Simon Matter wrote:
>
> 
>> >
>> > is this related?
>>
>> Your mail contains another error but the problem is the same in the end,
>> your MTA accepts a mail which is later refused by Cyrus-IMAPd.
>>
>> Both cases are bad because it creates backscatter.
>>
>> Would be nice to know what exactly is wrong with the mail in your case.
>
> hi simon,
>
> so -- i forgot that following the first error i upgraded to 2.3.16 and
> made no changes to the imapd.conf. need more sleep and less coffee :-)
>
> i have just successfully received a mail that had previously bounced (in
> a tcpdump file)
>
> would it be of use to you to see the message contents?

If the mail is not too big, could you post it here?

Simon


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

Re: LMTP bounces with invalid chars in MAIL FROM adress

[mayak-cq]

On Mon, 2011-02-14 at 17:11 +0100, Simon Matter wrote:


> >
> > is this related?
> 
> Your mail contains another error but the problem is the same in the end,
> your MTA accepts a mail which is later refused by Cyrus-IMAPd.
> 
> Both cases are bad because it creates backscatter.
> 
> Would be nice to know what exactly is wrong with the mail in your case.

hi simon,

so -- i forgot that following the first error i upgraded to 2.3.16 and
made no changes to the imapd.conf. need more sleep and less coffee :-)

i have just successfully received a mail that had previously bounced (in
a tcpdump file)

would it be of use to you to see the message contents?

thanks
m



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

Re: LMTP bounces with invalid chars in MAIL FROM adress

[Simon Matter]

> Hi,
>
> I've seen a growing number of bounced mails from Cyrus LMTP where Postfix
> logs "501 5.5.4 Syntax error in parameters (in reply to MAIL FROM
> command))"
>
> The problem is that those messages really have invalid from adresses, like
> "RosaSánc...@something.com", but Postfix still accepts them. Later, Cyrus
> runs parseaddr() on it ans correctly refuses to accept the mail.
>
> Now, I'm interested to hear how others handle this case, if possible how
> they handle it with postfix. I know that enabling strict_rfc821_envelopes
> would possibly help but that seem to be a bad idea.

I've searched the postfix-users list and as expected I'm not the only one
to see this issue:

http://marc.info/?l=postfix-users&m=120168533827364&w=2

Since postfix (and I think also other MTA's) are a bit relaxed on what
they accept as "MAIL FROM:" addresses, is there a very good reason for
Cyrus to be so strict?

Simon


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

RE: XFER problems with 2.4.6

[karavelov]

- Цитат от karave...@mail.bg, на 11.02.2011 в 15:14 -  
Hello 
This week I have installed a second server with Cyrus 2.4.6 (from
git.debian.org package) and I have found some unexpected behavior - I could
move users from old installations (2.3.16) to the new servers but I could
not move users between 2.4.6 servers. Here is an example session: 


stor1.internal> info user/0...@.xx 
{user/0...@.xx}: 
 duplicatedeliver: false 
 lastpop: 
 lastupdate: 11-Feb-2011 11:32:26 +0200 
 partition: default 
 pop3newuidl: true 
 sharedseen: false 
 size: 96470220 
stor1.internal> xfer user/0...@.xx stor5 default 
xfermailbox: The remote Server(s) denied the operation 
stor1.internal> quit 


the log file on the source server has this entry: 
Feb 11 14:40:44 stor1 cyrus/imap[16158]: Could not set remote acl on
mail.bg!user.0666.pay 


the log file on the destination server has this: 
Feb 11 14:41:09 stor5 cyrus/imap[11569]: login: [10.0.0.130] murder PLAIN
User logged in 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: LOSTQUOTA: unable to record add of
256951 bytes in quota .xx!user.000 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: LOSTQUOTA: unable to record quota
file .xx!user.000 
Feb 11 13:23:47 stor5 cyrus/imap[11445]: Deleted mailbox
^xx!user^000^pay 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: Deleted mailbox
^xx!user^000^Sent 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: Deleted mailbox
^xx!user^000^SPAM 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: Deleted mailbox
^xx!user^000^Facebook 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: Deleted mailbox
^xx!user^000^Drafts 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: Deleted mailbox
^xx!user^000^D^V^ 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: Deleted mailbox ^xx!user^000 
Feb 11 14:41:10 stor5 cyrus/imap[11569]: USAGE murder user: 0.00 sys:
0.05 


I do not know if this is a bug or misconfiguration (it's the same with the
old servers) so I have attached the config file. 


Thanks in advance for any suggestions 


luben 


Is this a bug or some fault from my side (system ot cyrus-imapd
misconfiguration)? Whan can I do in order to debug the problem? 


Thanks in advance for any help 


luben 


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

Re: custom notifications

[Simon Matter]

> On Tue, 2011-02-15 at 10:37 +0100, Wolfgang Hennerbichler wrote:
>> Hi,
>> I'd like to write a custom notification system (using xmmp or
>> something like that, I don't know yet :)) for cyrus.
>
> +1, same here.
>
>> I've had a look at the notify_unix/simple_notify - file in the
>> contrib-directory. It doesn't seem to work in my installation (the
>> script doesn't log any notifications, although notifyd does for
>> example notify zephyr, which works), or maybe I don't understand the
>> concept of notifications. So I'd like to ask a couple of questions:
>
> I believe notifications have to be pushed by SIEVE.  At least that is
> what I recall from the last time I looked at it [quite some time ago].
>
>> * does anybody have custom notifications up and running by reading the
>> notification-socket of cyrus?
>
> Not me.  I've tried.  The documentation is beyond "thin".
>
>> * does notifyd need to be running in order to make the notify-socket
>> readable, or is the notify-socket filled by the cyrus-master process?
>
> The socket won't exist unless the notify server is defined.
>
>> * where would I find instructions on that?
>
> There is very little beyond the man page and the one perl script you
> found.

Despite the new feature in 2.4 (which I didn't know before) I've included
my notify_sms patch into the RPM and IIRC it has even worked when I tested
it :) It can be used to notify using any kind of script and it even comes
with a README.
Maybe I should remove it now that 2.4 seems to have builtin functionality
for it.

Simon


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

Re: custom notifications

[Wolfgang Hennerbichler]

On Tue, Feb 15, 2011 at 07:33:41AM -0500, Dave McMurtrie wrote:
> > * does notifyd need to be running in order to make the notify-socket 
> > readable, or is the notify-socket filled by the cyrus-master process?
> > * where would I find instructions on that?
> 
> You want to set the notify_external option in imapd.conf and point that
> at a program (script, binary, whatever) that you write.  notifyd will
> fork/exec your program and pass it -c, -p, -u and -m command line
> arguments.  Your program can then to whatever custom notification you
> want it to.
>
> This was added in the 2.4.x series.  The imapd.conf option is documented
> in the imapd.conf manpage ...

thanks! too bad I do still have 2.2 running (debian squeeze), and I was too 
lazy for now to find a good package maintainer or compile by myself. So I guess 
I'm stuck by now. 

> Let me know if you need any additional information.

Thank you for your help! 
 
> Thanks!
> 
> Dave

Wolfgang

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

-- 
http://www.wogri.com

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

Re: custom notifications

[Dave McMurtrie]

...initially forgot to send to the list.  sorry.

On 02/15/2011 04:37 AM, Wolfgang Hennerbichler wrote:
> Hi,
>
> I'd like to write a custom notification system (using xmmp or something like 
> that, I don't know yet :)) for cyrus.
> I've had a look at the notify_unix/simple_notify - file in the 
> contrib-directory. It doesn't seem to work in my installation (the script 
> doesn't log any notifications, although notifyd does for example notify 
> zephyr, which works), or maybe I don't understand the concept of 
> notifications. So I'd like to ask a couple of questions:
> * does anybody have custom notifications up and running

Yes.

> by reading the notification-socket of cyrus?

No.

> * does notifyd need to be running in order to make the notify-socket 
> readable, or is the notify-socket filled by the cyrus-master process?
> * where would I find instructions on that?

You want to set the notify_external option in imapd.conf and point that
at a program (script, binary, whatever) that you write.  notifyd will
fork/exec your program and pass it -c, -p, -u and -m command line
arguments.  Your program can then to whatever custom notification you
want it to.

This was added in the 2.4.x series.  The imapd.conf option is documented
in the imapd.conf manpage here:

http://cyrusimap.org/docs/cyrus-imapd/2.4.6/man/imapd.conf.5.php

Let me know if you need any additional information.

Thanks!

Dave

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

Re: Adding a 2.3.x replica [Documentation Bug]

[Michael Menge]

Quoting Adam Tauno Williams :


On Mon, 2011-02-14 at 16:37 -0500, Adam Tauno Williams wrote:

Looking at



Documentation Bug:

"Add a line similar to the following in the STARTUP section of
cyrus.conf"

There is no "STARTUP" section, it is the "START" section.

START {
  # do not delete this entry!
  recover   cmd="ctl_cyrusdb -r"
  # this is only necessary if using idled for IMAP IDLE
  idled cmd="idled"
  # Start the replication client (this is the master)
  syncclient   cmd="sync_client -r"
}



If this method is used the master will wait till the syncclient can
reach the replica. This can cause unnessesary delays it the replica
is not running or can't be reached.




Reading the quote -
"Rolling" replication means that the "master" server continuously
synchonizes itself with the replica.
- I take this to mean that the master continuously *pushes* changes to
the replica [secondary]?


Yep.


Is there a recommended/suggested value for sync_repeat_interval other
than the default of "1"?


?



Is there a recommended Method for bringing up a new replica for an
active master (with 1.4 million messages in its mailstore)




If the replica is running, you have to run the following command
to initialise the replica:

sync_client -u -f userlist.txt

userlist.txt is a file containing all users.
This can be done while the master and rolling replication
is running.





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

smime.p7s
Description: S/MIME Signatur

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

Re: custom notifications

[Adam Tauno Williams]

On Tue, 2011-02-15 at 10:37 +0100, Wolfgang Hennerbichler wrote:
> Hi, 
> I'd like to write a custom notification system (using xmmp or
> something like that, I don't know yet :)) for cyrus. 

+1, same here.

> I've had a look at the notify_unix/simple_notify - file in the
> contrib-directory. It doesn't seem to work in my installation (the
> script doesn't log any notifications, although notifyd does for
> example notify zephyr, which works), or maybe I don't understand the
> concept of notifications. So I'd like to ask a couple of questions: 

I believe notifications have to be pushed by SIEVE.  At least that is
what I recall from the last time I looked at it [quite some time ago].

> * does anybody have custom notifications up and running by reading the
> notification-socket of cyrus?

Not me.  I've tried.  The documentation is beyond "thin".

> * does notifyd need to be running in order to make the notify-socket
> readable, or is the notify-socket filled by the cyrus-master process? 

The socket won't exist unless the notify server is defined.

> * where would I find instructions on that? 

There is very little beyond the man page and the one perl script you
found.


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

Re: Adding a 2.3.x replica [Documentation Bug]

[Adam Tauno Williams]

On Mon, 2011-02-14 at 16:37 -0500, Adam Tauno Williams wrote: 
> Looking at
> 

Documentation Bug:

"Add a line similar to the following in the STARTUP section of
cyrus.conf"

There is no "STARTUP" section, it is the "START" section.

START {
  # do not delete this entry!
  recover   cmd="ctl_cyrusdb -r"
  # this is only necessary if using idled for IMAP IDLE
  idled cmd="idled"
  # Start the replication client (this is the master)
  syncclient   cmd="sync_client -r"
}


> Reading the quote -
> "Rolling" replication means that the "master" server continuously
> synchonizes itself with the replica.
> - I take this to mean that the master continuously *pushes* changes to
> the replica [secondary]?

Yep.

> Is there a recommended/suggested value for sync_repeat_interval other
> than the default of "1"?

?

> Is there a recommended Method for bringing up a new replica for an
> active master (with 1.4 million messages in its mailstore)

?


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

Re: Duplicate elimination causing loss of legitimate mails

[Ramprasad]

> There is a possible workaround. You can configure a separate smtp server
> which is used by the broken clients to submit messages, and there you
> configure the MTA to always replace the Message-ID by a newly created one.
> 
> Simon



But the second instance of MTA ( postfix  in my case )  must do no
delivery of its own except forwarding to the first instance or else it
will cause mail duplication. 


I had done this ( for all users globally not for just those clients)  ..
but the problem is it breaks threads on decent email clients. 
So I had to revert back. 


Will it not be easier to just expire records sooner on deliver.db. 
Also this will cause lmtp to run faster I believe .. since it will have
a smaller lookup to do. 



Thanks
Ram












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

custom notifications

[Wolfgang Hennerbichler]

Hi, 

I'd like to write a custom notification system (using xmmp or something like 
that, I don't know yet :)) for cyrus. 
I've had a look at the notify_unix/simple_notify - file in the 
contrib-directory. It doesn't seem to work in my installation (the script 
doesn't log any notifications, although notifyd does for example notify zephyr, 
which works), or maybe I don't understand the concept of notifications. So I'd 
like to ask a couple of questions: 
* does anybody have custom notifications up and running by reading the 
notification-socket of cyrus?
* does notifyd need to be running in order to make the notify-socket readable, 
or is the notify-socket filled by the cyrus-master process? 
* where would I find instructions on that? 

thanks a bunch, 
wolfgang
-- 
http://www.wogri.com

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

Re: LMTP bounces with invalid chars in MAIL FROM adress

[mayak-cq]

On Mon, 2011-02-14 at 17:11 +0100, Simon Matter wrote:
> > On Mon, 2011-02-14 at 16:09 +0100, Simon Matter wrote:
> >


> >
> > i have also seen this lately -- coming from LMTP as well -- running your
> > 2.3.16 rpm ...
> >
> > is this related?
> 
> Your mail contains another error but the problem is the same in the end,
> your MTA accepts a mail which is later refused by Cyrus-IMAPd.
> 
> Both cases are bad because it creates backscatter.
> 
> Would be nice to know what exactly is wrong with the mail in your case.

hi simon,

i never found the mail anywhere -- it passed amavis, so no traces there,
and the mail couldn't be delivered via LMTP, so i think it just got
discarded -- postfix didn't have an address to send a bounce to.

the source of the mail (in my logging) is real -- it's HP's licensing
department. i am going to tcpdump -s0 and capture to a file so as to
watch the entire conversation. i'll send you a copy off list.

thanks

m




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

Re: Duplicate elimination causing loss of legitimate mails

[Simon Matter]

> On Tue, February 15, 2011 9:21 am, Ramprasad wrote:
>> Hi,
>>
>>
>> On our cyrus 2.3.7 servers we are seeing legitimate mails getting
>> duplicate eliminated. Some users continue to use non-compliant clients
>> which
>> use duplicate message-ids.
>>
>> Is it  possible to auto-expire records in deliver.db after say 3 hours
>> so that these losses could be minimized ... the current minimum is 1 day
>> AFAIK
>>
>>
>> I cannot switch off duplicate elimination because that would cause
>> problems to all other users too.
>>
>>
>> (I know I should tell users to upgrade email clients .. but that is not
>> going to work in reality )
>
>
> Ram,
>
>
> Correct.
>
> Outlook/Exchange is known for reusing message ids upon a resend action
> by the user. Other mail clients may be equally broken in this area but
> I haven't come across any of those yet.

Now there is a good chance this feature will show up on your next Nokia
phone as well :)

>
> Upgrading your own users (accomplished by switching to most Open Source or
> even Apple products) will do the trick, but this wouldn't help you in this
> particular case because the faulty header line is created by their corres-
> pondants (which is potentially the whole planet's population).

There is a possible workaround. You can configure a separate smtp server
which is used by the broken clients to submit messages, and there you
configure the MTA to always replace the Message-ID by a newly created one.

Simon


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

Re: LMTP bounces with invalid chars in MAIL FROM adress

[Simon Matter]

> On Mon, 14 Feb 2011, Simon Matter wrote:
>> The problem is that those messages really have invalid from adresses,
>> like
>> "RosaSánc...@something.com", but Postfix still accepts them. Later,
>> Cyrus
>> runs parseaddr() on it ans correctly refuses to accept the mail.
>
> Yeah, postfix really should reject that crap.  Do you know which MUA is
> producing this braindamage?

I think those mails are mainly spam, so the MUA is some kind of spam tool
I guess.

>
>> Now, I'm interested to hear how others handle this case, if possible how
>> they handle it with postfix. I know that enabling
>> strict_rfc821_envelopes
>> would possibly help but that seem to be a bad idea.
>
> The problem with strict_rfc821_envelopes is that it also requires one to
> actually speak rfc2821, so "MAIL FROM: whome...@example.com" would cause a
> rejection.
>
> There is the heavy-handed "smtpd_command_filter", though. It is certainly
> capable of doing what you need.

My first idea was to use header_checks to check the From: Reply-To: and
Return-Path: headers but you are right, that's not enough. I'm still
wondering why those messages go through.

Maybe I care too much :)

Simon


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

Re: Duplicate elimination causing loss of legitimate mails

[Eric Luyten]

On Tue, February 15, 2011 9:21 am, Ramprasad wrote:
> Hi,
>
>
> On our cyrus 2.3.7 servers we are seeing legitimate mails getting
> duplicate eliminated. Some users continue to use non-compliant clients which
> use duplicate message-ids.
>
> Is it  possible to auto-expire records in deliver.db after say 3 hours
> so that these losses could be minimized ... the current minimum is 1 day AFAIK
>
>
> I cannot switch off duplicate elimination because that would cause
> problems to all other users too.
>
>
> (I know I should tell users to upgrade email clients .. but that is not
> going to work in reality )


Ram,


Correct.

Outlook/Exchange is known for reusing message ids upon a resend action
by the user. Other mail clients may be equally broken in this area but
I haven't come across any of those yet.

Upgrading your own users (accomplished by switching to most Open Source or
even Apple products) will do the trick, but this wouldn't help you in this
particular case because the faulty header line is created by their corres-
pondants (which is potentially the whole planet's population).


Eric.





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

Duplicate elimination causing loss of legitimate mails

[Ramprasad]

Hi,

On our cyrus 2.3.7 servers we are seeing legitimate mails getting
duplicate eliminated. Some users continue to use non-compliant clients
which use duplicate message-ids. 

Is it  possible to auto-expire records in deliver.db after say 3 hours
so that these losses could be minimized ... the current minimum is 1 day
AFAIK

I cannot switch off duplicate elimination because that would cause
problems to all other users too. 


(I know I should tell users to upgrade email clients .. but that is not
going to work in reality ) 




Thanks
Ram




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