Re: automated delivery of sieve scripts for new users

2005-02-03 Thread Christos Soulios
Craig White wrote:

I believe that you are correct on the patch level but interestingly
enough, it doesn't complain if I include any of the following directives
in /etc/imapd.conf
autocreate_sieve_script: /etc/default_sieve_script
autocreate_sieve_compiledscript: /etc/default_sieve_script.bc
generate_compiled_sieve_script: 1
Cyrus would not complain neither if it supported these options, nor if 
it did not supported them.


I don't think I've tried all of the combinations of them yet but they
don't appear to work.
The above configuration is correct as long as the files are valid sieve 
scripts and readable by cyrus. Moreover, the patch is executed only when 
there is no user mailbox and the user logs into the system. And not when 
 you create the mailbox using cyradm or other administering tool.

and in /usr/share/doc/cyrus-imapd-2.2.10/README.autosievefolder
there is no mention of those items.
Autosieve folder patch is a different patch from autocreate inbox/sieve. 
It implements the creation of a folder upon file_into command from a 
sieve script. Perhaps you should read the README.autocreate file for 
more information in these options or read the following links :

http://email.uoa.gr/projects/cyrus/autocreate
http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2

I appreciate your offer of the packages and note that apparently
fedora-3 is using some derivative of your packages since I recall seeing
the name on some file they distribute.
I am going to try to stick with that which is distributed by fedora
package for automated updates, etc. and so that really leaves me option
2 - which isn't so terrible since I have the bytecoded script in hand
and I will script new users anyway.
I believe that Simon's patches are very stable and always uptodate 
against security and bug fixes. So I am sure, you should try them.


I might put in a bugzilla entry into fedora though...
Regards,
Christos
---
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: automated delivery of sieve scripts for new users

2005-02-03 Thread Craig White
On Thu, 2005-02-03 at 12:24 +0200, Christos Soulios wrote:
 Craig White wrote:
 
 
  I believe that you are correct on the patch level but interestingly
  enough, it doesn't complain if I include any of the following directives
  in /etc/imapd.conf
  
  autocreate_sieve_script: /etc/default_sieve_script
  autocreate_sieve_compiledscript: /etc/default_sieve_script.bc
  generate_compiled_sieve_script: 1
  
 
 Cyrus would not complain neither if it supported these options, nor if 
 it did not supported them.
 
 
  I don't think I've tried all of the combinations of them yet but they
  don't appear to work.
  
 
 The above configuration is correct as long as the files are valid sieve 
 scripts and readable by cyrus. Moreover, the patch is executed only when 
 there is no user mailbox and the user logs into the system. And not when 
   you create the mailbox using cyradm or other administering tool.
 
  and in /usr/share/doc/cyrus-imapd-2.2.10/README.autosievefolder
  there is no mention of those items.
  
 
 Autosieve folder patch is a different patch from autocreate inbox/sieve. 
 It implements the creation of a folder upon file_into command from a 
 sieve script. Perhaps you should read the README.autocreate file for 
 more information in these options or read the following links :
 
 http://email.uoa.gr/projects/cyrus/autocreate
 http://email.uoa.gr/projects/cyrus/autocreate/README.autocreate-cyrus-2.2
 
 
  I appreciate your offer of the packages and note that apparently
  fedora-3 is using some derivative of your packages since I recall seeing
  the name on some file they distribute.
  
  I am going to try to stick with that which is distributed by fedora
  package for automated updates, etc. and so that really leaves me option
  2 - which isn't so terrible since I have the bytecoded script in hand
  and I will script new users anyway.
  
 
 I believe that Simon's patches are very stable and always uptodate 
 against security and bug fixes. So I am sure, you should try them.

thanks - I am certain that fedora is using Simon's patches...just not
this one...yet.

I put in a bugzilla @ redhat (fedora) - we'll see.

For my house, it's meaningless. I already have 3 kids and I don't plan
on having any more, certainly not enough to make autosieve a priority.
At one of my clients though, it is significant and if fedora/RHEL
doesn't update, I'll use Simon's so thanks for the heads up.

I love this message base - got a lot of extremely accurate answers.

Thanks everyone

Craig

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


intergrate cyrus and postfix

2005-02-03 Thread Kern, Tom
still trying to intergrate cyru-imap 2.2.10-10 and postfix with no luck.
i keep getting a command died with status 1: /cyrus/bin/deliver.

with my cyrus, the deliver program is in /usr/lib/cyrus-imapd/.
i changed my master.cf to reflect this

here is my master.cf-


# service type  private unpriv  chroot  wakeup  maxproc command + args
#   (yes)   (yes)   (yes)   (never) (100)
# ==
smtp  inet  n   -   n   -   -   smtpd -v
#628  inet  n   -   y   -   -   qmqpd
pickupfifo  n   -   y   60  1   pickup
cleanup   unix  n   -   y   -   0   cleanup
qmgr  fifo  n   -   y   300 1   qmgr
#qmgr fifo  n   -   y   300 1   nqmgr
rewrite   unix  -   -   y   -   -   trivial-rewrite
bounceunix  -   -   y   -   0   bounce
defer unix  -   -   y   -   0   bounce
flush unix  n   -   y   1000?   0   flush
proxymap  unix  -   -   n   -   -   proxymap
smtp  unix  -   -   n   -   -   smtp
relay unix  -   -   y   -   -   smtp
#   -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix  n   -   y   -   -   showq
error unix  -   -   y   -   -   error
local unix  -   n   n   -   -   local
virtual   unix  -   n   n   -   -   virtual
lmtp  unix  -   -   n   -   -   lmtp -v
smtp-amavis unix-   -   y   -   10  smtp
-o smtp_data_done_timeout=1200
-o disable_dns_lookups=yes
127.0.0.1:10025 inetn   -   y   -   -   smtpd
-o content_filter=
-o local_recipient_maps=
-o relay_recipirnt_maps=
-o smtpd_restriction_classes=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks=127.0.0.0/8
-o strict_rfc821_envelopes=yes
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# maildrop. See the Postfix MAILDROP_README file for details.
#
maildrop  unix  -   n   n   -   -   pipe
  flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
#
# The Cyrus deliver program has changed incompatibly, multiple times.
#
#old-cyrus unix  -   n   n   -   -   pipe
 # flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
# Cyrus 2.1.5 (Amos Gouaux)
cyrus unix  -   n   n   -   -   pipe
  user=cyrus argv=/usr/lib/cyrus-imapd/deliver -r ${sender} -m ${extension} 
${user}
uucp  unix  -   n   n   -   -   pipe
  flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
ifmailunix  -   n   n   -   -   pipe
  flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp unix  -   n   n   -   -   pipe
  flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
trace unix  -   -   n   -   0   bounce
verifyunix  -   -   n   -   1   verify






what should i change?
cyrus seems to keep changing and i can't find a doc stating how master.cf 
should be with cyrus 2.2.10-10.


thanks

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


error message message contains invalid header

2005-02-03 Thread Stefan Palme

hi,

since no one replyed to the bugtracker entry, i will post the
question here too 
(see https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2613):



I am migrating my mailboxes to an account on:
name   : Cyrus IMAPD
version: v2.2.10 2004/11/23 17:52:52
vendor : Project Cyrus
support-url: http://asg.web.cmu.edu/cyrus
os : Linux
os-version : 2.6.9
environment: Built w/Cyrus SASL 2.1.20
 Running w/Cyrus SASL 2.1.20
 Built w/Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003)
 Running w/Sleepycat Software: Berkeley DB 4.2.52: (December  3, 
2003)
 Built w/OpenSSL 0.9.7d 17 Mar 2004
 Running w/OpenSSL 0.9.7d 17 Mar 2004
 CMU Sieve 2.2
 TCP Wrappers
 mmap = shared
 lock = fcntl
 nonblock = fcntl
 auth = unix
 idle = idled

When moving some messages, the mail-client responds with a error. We have
enabled per account log files from the imap-server. But in there is the same
non-sense error:
  [Message contains invalid header]

If you belive a header is invalid, then why don't you include the name in the
error message?

Here are the headers:
11062337522 append INBOX/Development (\Seen) {2235+}
From [EMAIL PROTECTED] Fri Apr 26 00:50:52 2002
Return-Path: [EMAIL PROTECTED]
Received: from host55.syd.nuix.com.au (250.d.005.syd.iprimus.net.au
[210.50.55.250] (may be forged)) by mail.stock-world.de (8.10.1/8.10.1)
with ESMTP id g3PMop009523 for [EMAIL PROTECTED]; Fri, 26 Apr 2002
00:50:52 +0200
Received: from host55.syd.nuix.com.au (localhost.localdomain [127.0.0.1])
by host55.syd.nuix.com.au (Postfix) with SMTP id 42ECF145EA2 for
[EMAIL PROTECTED]; Fri, 26 Apr 2002 08:53:23 +1000 (EST)
Content-Type: text/plain; charset=iso-8859-1
From: David Sitsky [EMAIL PROTECTED]
To: Stefan Kost [EMAIL PROTECTED]
Subject: Re: cvsplot
Date: Fri, 26 Apr 2002 08:43:27 +1000
X-Mailer: KMail [version 1.2]
References: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
In-Reply-To: [EMAIL PROTECTED]
MIME-Version: 1.0
Message-Id: [EMAIL PROTECTED]
Content-Transfer-Encoding: 8bit
X-Evolution-Source: pop://[EMAIL PROTECTED]/inbox
X-Evolution: 004c-0010

 mail message text 


thank for you help
-stefan-


-- 
---
Dipl. Inf. (FH) Stefan Palme
 
email: [EMAIL PROTECTED]
icq:   36376278
phon:  +49 341 3910484
fax:   +49 1212 517956219
mobil: +49 178 3227887
 
key fingerprint: 1BA7 D217 36A1 534C A5AD  F18A E2D1 488A E904 F9EC
---

---
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: intergrate cyrus and postfix

2005-02-03 Thread Kern, Tom
I already have that in main.cf
its my understanding that i need the path to the deliver program in master.cf 
for cyrus to work with postfix.

thanks

-Original Message-
From: Carl P. Corliss [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2005 2:06 PM
To: Kern, Tom
Subject: Re: intergrate cyrus and postfix


try using lmtp as it incurs less overhead than using deliver. In your main.cf 
use something like:

mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
or
virtual_transport = lmtp:unix:/var/imap/socket/lmtp

you'll need to read up on the postfix site to determine exactly which one 
should 
should use (a good start would be:  http://www.postfix.org/VIRTUAL_README.html).

Cheers,

--
Carl


---
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: intergrate cyrus and postfix

2005-02-03 Thread Carl P. Corliss
You already know this to be untrue - as posted by Magnus Bäck on the 
postfix-users mailing list (to your exact same question there), you only need 
deliver if that's the method in which you want to have messages passed off to 
cyrus.

The people over on postfix-users mailing list have also already explained 
that you should be using LMTP (not cyrus' deliver). Perhaps it might be a good 
idea to read the README.postfix.gz that Hans Van Kranenburg was kind enough to 
send you. Might also be a good idea to follow his suggestions in his most recent 
posting on the postfix-users mailing list - or those of Magnus Bäck and Matt, etc.

Also, I still haven't seen you post a link to any logs with errors that you 
recv (both here or on the postfix-users mailing list)...

--
Carl
Kern, Tom wrote:
I already have that in main.cf
its my understanding that i need the path to the deliver program in master.cf 
for cyrus to work with postfix.
thanks
-Original Message-
From: Carl P. Corliss [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 03, 2005 2:06 PM
To: Kern, Tom
Subject: Re: intergrate cyrus and postfix
try using lmtp as it incurs less overhead than using deliver. In your main.cf 
use something like:

mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
or
virtual_transport = lmtp:unix:/var/imap/socket/lmtp
you'll need to read up on the postfix site to determine exactly which one should 
should use (a good start would be:  http://www.postfix.org/VIRTUAL_README.html).

Cheers,
--
Carl
---
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


Sieve Authentication Fails

2005-02-03 Thread Dan Perez
Hi All,
I see that this question has been posted before, but I don't see a clear 
answer, so forgive me.  Any leads would be appreciated.

I'm running cyrus 2.2.10, on RHEL 3.0.  It works great.  Now I want to start 
using sieve... but I can't get sieveshell to connect to the server and I 
don't understand why.

[EMAIL PROTECTED] log]# sieveshell -u cyrus localhost
connecting to localhost
Please enter your password:
unable to connect to server at /usr/bin/sieveshell line 169, STDIN line 1.


my imapd conf:
configdirectory: /var/lib/imap
partition-default: /var/spool/imap
admins: cyrus
sievedir: /var/lib/imap/sieve
sendmail: /usr/sbin/sendmail
hashimapspool: true
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
tls_cert_file: /usr/share/ssl/certs/cyrus-imapd.pem
tls_key_file: /usr/share/ssl/certs/cyrus-imapd.pem
tls_ca_file: /usr/share/ssl/certs/ca-bundle.crt
saslauthd is running w/ -a pam
Authentication works fine for the IMAP server, cyradm.
Sieve is listening...
[EMAIL PROTECTED] log]# telnet localhost sieve
Trying 127.0.0.1...
Connected to localhost (127.0.0.1).
Escape character is '^]'.
IMPLEMENTATION Cyrus timsieved v2.2.10-Invoca-RPM-2.2.10-8
SASL PLAIN
SIEVE fileinto reject envelope vacation imapflags notify subaddress 
relational comparator-i;ascii-numeric regex
STARTTLS
OK

Heck, I even get sieve headers in my emails...
X-Sieve: CMU Sieve 2.2
Any ideas?
Thanks,
Dan
---
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


Unusual Problem w/ Quota

2005-02-03 Thread Bill Martin
Anyone seem problem w/ cyrus 2.2.10 and quotas on RedHat 3.0 AS -
2.4.21-27.0.2.ELsmp?  


Starting a couple days ago, after an update from RHN which updated the
following:
krb5-devel  1.2.7  38  
 i386  
krb5-libs   1.2.7  38  
 i386  
less37812  
 i386  
libtiff 3.5.7  22.el3  
 i386  
libtiff-devel   3.5.7  22.el3  
 i386  

After taking the box offline, we have tried to run the quota -f on all
those who had reported quota issues.  About half of them were actually
over quota.  The other half were touched and corrected, so we though.  
Every person who was touched by quota -f reflected something similar
to the following:

user.sroth1: usage was 55080912, now 27540456
   Quota  % UsedUsed Root
   51200  52   26894 user.sroth1
user.srahma1: usage was 76701988, now 38350994
   Quota  % UsedUsed Root
   51200  73   37452 user.srahma1
user.sraggi: usage was 70626754, now 34986281
   Quota  % UsedUsed Root
   51200  66   34166 user.sraggi
user.spebels: usage was 74474780, now 37237390


If you notice, the space being occupied reports as DOUBLE what is
actually there.  These were verified vi du as well.

Ideas, suggestion?  Anything would be appreciated.

-bill-


---
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: Sieve Authentication Fails

2005-02-03 Thread Craig White
On Thu, 2005-02-03 at 14:24 -0800, Dan Perez wrote:
 Hi All,
 
 I see that this question has been posted before, but I don't see a clear 
 answer, so forgive me.  Any leads would be appreciated.
 
 I'm running cyrus 2.2.10, on RHEL 3.0.  It works great.  Now I want to start 
 using sieve... but I can't get sieveshell to connect to the server and I 
 don't understand why.
 
 [EMAIL PROTECTED] log]# sieveshell -u cyrus localhost
 connecting to localhost
 Please enter your password:
 unable to connect to server at /usr/bin/sieveshell line 169, STDIN line 1

saslpasswd cyrus

#add password for cyrus to sasldb

Craig

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