Re: Vacation Not Working...

2011-05-16 Thread Nathanael D. Noblet
On 05/12/2011 11:48 AM, Gary Mills wrote:
> Look what I found in the sieve vacation document
> (draft-ietf-sieve-vacation-07):
>
> "Vacation" is used to respond to a message with another message.
> Vacation's messages are always addressed to the Return-Path address
> (that is, the envelope from address) of the message being responded
> to.
>
> That's your problem.


This indeed was my problem, switched a small portion of our mail system 
to use an lmtp socket instead of a pipe and the Return-Path is filled 
out correctly. This also allows the vacation message to start functioning.

Thanks for all the help everyone.

-- 
Nathanael d. Noblet
t 403.875.4613

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


We are looking for a Cyrus contractor

2011-05-16 Thread Gary Mills
If you are interested in maintaining our Cyrus e-mail system on a
contract basis, please let me know.  I don't know the details of
responsibilities or requirements, but I'll be happy to put you in
touch with my manager for discussion on these matters.

-- 
-Gary Mills--Unix Group--Computer and Network Services-

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


Re: Starting 'delayed message expunge' on a large Cyrus 2.3.16 server.

2011-05-16 Thread Eric Luyten
On Fri, May 13, 2011 3:25 pm, Sebastian Hagedorn wrote:
> --On 13. Mai 2011 14:57:36 +0200 Eric Luyten  wrote:
>
>
>> I currently have the following entry in my cyrus.conf :
>>
>>
>> delprune cmd="cyr_expire -E 1" at=0055
>>
>> which takes about six minutes, every night, to
>>
>> May 13 00:55:11 cyr_expire[21210]: Expunged 0 out of 0 messages from 0
>> mailboxes May 13 00:55:11  cyr_expire[21210]: duplicate_prune: pruning back 1
>>  daysMay 13 01:01:45cyr_expire[21210]: duplicate_prune: purged 205245
>> out of 401016 entries
>>
>>
>> I think I'll have to launch several cyr_expire's one after another or in
>> parallel (will be done during night hours or weekends) to get the job done
>> before production load arrives.
>
> We have a setup similar to yours in size and get by just fine with only
> this entry:
>
> delprune  cmd="cyr_expire -E 3 -X 3 -D 3" at=0400
>
> I just checked our logs. It usually finishes around 7 am.


Sebastian,


I just ran, during office hours, a 'cyr_expire' against our mailboxes
with names starting with 'user.t' (3.3 % of almost 475.000 mailboxes)
and this took under six minutes elapsed time.
Since all it did was detect there are no 'cyrus.expunge' files present,
it did not have to carry out the physical pruning, of course.

We're almost certainly not an order of magnitude off from your figures,
it appears, but more tests are sitting in our pipeline.


Thank you for your earlier feedback,
Eric Luyten, Computing Centre VUB/ULB.



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


Impact of mismatched improved_mboxlist_sort in murder environment?

2011-05-16 Thread Matt Elson
Hey all,

I'm in the middle of moving from a 2.2.13p1 Murder environment to a
2.3.16 Murder, moving the backends first. I've been moving people over
slowly (thousand or so now, I think) and while running a few checks, I
got the following error when I ran ctl_mboxlist -m -w

fatal error: Internal error: assertion failed: ctl_mboxlist.c: 297:
strcmp(realpart, unused_mbdata->server)

Poking around I would get this on certain mailboxes that ctl_mboxlist
would hit, so I shuffled a few of the problematic mailboxes to a test
server, where they would show the same error.

After hitting my head against the wall, I noticed that the new (2.3.16)
backends have improved_mboxlist_sort: 1 set, whereas the
not-yet-upgraded frontends (2.2.13p1)+mupdate servers, well, don't even
have the option ;).  I guessed that this mismatch might be the problem,
and while I've not done any extensive testing since the system is live,
if I shutdown the test server with my problematic mailboxes, dump the
mailboxes.db there, turn off improved_mboxlist_sort, and reload the
dump, I can issue ctl_mboxlist -m -w till my heart is content.

Outside of ctl_mboxlist functions, everything's fine and I haven't
noticed anything amiss, but (obviously) that doesn't mean there isn't
some problem waiting to bite me.

I guess the question is 1) if I'm right that my problems are likely
related to improve_mboxlist_sort, and 2) if anyone has any idea what
sort of other problems I may encounter due to this mismatch.

Due to circumstances beyond my control, getting downtime in my
environment (even for what should be a straight forward dump/reload)
anytime soon is going to be problematic, but I can push for it if
necessary.  On the other hand, if the problem is relatively harmless and
going to sort itself out once I get the mupdate server to 2.3.16, I'm
fine with waiting until then or upgrading the mupdate server sooner.  

Thanks in advance for any thoughts!

Matt,
Wishing he could go straight to 2.4.x.  Sigh.

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


Re: Vacation Not Working...

2011-05-16 Thread Marc Patermann
Hi,

Nathanael D. Noblet schrieb am 12.05.2011 18:05 Uhr:

>I have yet to get it working. I figured I'd give a recap of what has 
> changed since I started asking for help here.
> 
> I've added sieve_extensions: vacations to imap.conf and a
> 'telnet localhost sieve' shows that vacation is supported.
Good so far.

Your sendmail path "sendmail: /usr/sbin/sendmail" is working, I hope!? 
Even for user cyrus?

Here is the simple standard script we use as default:

require "vacation";
require "fileinto";

if header :contains "X-Spam-Flag" "YES" {
fileinto "INBOX.Junk";
stop;
}

vacation
:addresses [ "possible@recipient.address1", possible@recipient.address2" ]
:subject "subject text"
   "Message text";

Pretty straight forward.


Marc

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