Re: Automatic Sieve Script Subscription
Hi, On Wed, 22 Aug 2007, Peter wrote: Hello. Where can i find the perl module Cyrus::SIEVE::managesieve for download ?? its a part of cyrus imap so you should already have it. ps: please keep the list on the cc. Greetings Christian /Peter Thanks a lot! I will try it. Message du 21/08/07 12:12 De : Christian Kratzer [EMAIL PROTECTED] A : [EMAIL PROTECTED] [EMAIL PROTECTED] Copie à : info-cyrus info-cyrus@lists.andrew.cmu.edu Objet : Re: Automatic Sieve Script Subscription Hi, On Tue, 21 Aug 2007, [EMAIL PROTECTED] wrote: Hy all, Do you know if there's a way for any mailboxes to subscribe automaticaly to a sieve script at creation of the mailbox? I would like for all users to transfert SPAM tagged subject to a SPAM folders, or mailling list mail to mailling list folder without having to explain all users to write it with avelsieve. I tought Autosieve patch was able to do it but it only creates folders if it doesn't exist. we use a perl script to automatically create new accounts, create and subscribe the Spam mailbox and also install and activate a default sieve script. We use following perl modules: use Cyrus::IMAP::Admin; use Cyrus::SIEVE::managesieve; use IMAP::Admin; IMAP::Admin required a patch to allow logging in with separate authentication and authorisation rules for subscribing to the newly created Spam mailbox. Apart from that it was straight forward. Greetings Christian -- Christian Kratzer CK Software GmbH Email: [EMAIL PROTECTED] Schwarzwaldstr. 31 Phone: +49 7452 889 135 D-71131 Jettingen Fax: +49 7452 889 136 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer 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 -- Christian Kratzer CK Software GmbH Email: [EMAIL PROTECTED] Schwarzwaldstr. 31 Phone: +49 7452 889 135 D-71131 Jettingen Fax: +49 7452 889 136 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer 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
could not fetch new headers
hi, i have a strange problem with the inbox of one user. i´m using outlook 2000 as mail client. i created an imap connection to see what happens. the reason to test the account over imap was that the user had 2 passwords with an ''-sign and could login with both of them over horde (just one is allowed). but that´s another problem that will go to the horde list. to exclude this problem i changed the password of the user to a password without any special characters. i created an imap-account in outlook and used an encrypted connection (port 993). this works for all my other accounts except for this special user-account. when i try to check mail on this account i get the following error message in outlook: Could not fetch new headers in the inbox for account. An unknown error has occured. Please save any existing work and restart the program. i don´t know what the problem is. any other account works fine with these settings. regards philippe 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
problem fetching new headers
hi, i have a strange problem with the inbox of one user. i´m using outlook 2000 as mail client. i created an imap connection to see what happens. the reason to test the account over imap was that the user had 2 passwords with an ''-sign and could login with both of them over horde (just one is allowed). but that´s another problem that will go to the horde list. to exclude this problem i changed the password of the user to a password without any special characters. i created an imap-account in outlook and used an encrypted connection (port 993). this works for all my other accounts except for this special user-account. when i try to check mail on this account i get the following error message in outlook: Could not fetch new headers in the inbox for account. An unknown error has occured. Please save any existing work and restart the program. i don´t know what the problem is. any other account works fine with these settings. regards philippe 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
Problem connections cyrus
Sorry for my poor English:
I have problems with cyrus.
it's block 10-20 times a day, all days.
Don't crash, but suddenly don't accept any connections and the mua
display the message the server reject the connection, or max number
of connections reached.
I'm used two hosts:
1- debian sarge with cyrus and postfix
2- debian etch with postfix
The version of cyrus is 2.1.18-1+sarge2
My cyrus.conf is it:
# Debian defaults for Cyrus IMAP server/cluster implementation
# see cyrus.conf(5) for more information
#
# All the tcp services are tcpd-wrapped. see hosts_access(5)
# $Id: cyrus.conf,v 1.16 2003/11/05 01:04:22 hmh Exp $
START {
# do not delete this entry!
recover cmd=/usr/sbin/ctl_cyrusdb -r
# this is only necessary if using idled for IMAP IDLE
# this is NOT to be enabled right now in Debian builds
#idled cmd=idled
# this is useful on backend nodes of a Murder cluster
# it causes the backend to syncronize its mailbox list with
# the mupdate master upon startup
#mupdatepush cmd=/usr/sbin/ctl_mboxlist -m
# this is recommended if using duplicate delivery suppression
delprunecmd=/usr/sbin/ctl_deliver -E 3
# this is recommended if caching TLS sessions
tlsprunecmd=/usr/sbin/tls_prune
}
# UNIX sockets start with a slash and are absolute paths
# you can use a maxchild=# to limit the maximum number of forks of a service
# you can use babysit=true and maxforkrate=# to keep tight tabs on the
service
# most services also accept -U (limit number of reuses) and -T (timeout)
SERVICES {
# --- Normal cyrus spool, or Murder backends ---
# add or remove based on preferences
imapcmd=imapd -U 30 listen=imap prefork=0
maxchild=100
imaps cmd=imapd -s -U 30 listen=imaps prefork=0
maxchild=100
#pop3 cmd=pop3d -U 30 listen=pop3 prefork=0
maxchild=50
#pop3s cmd=pop3d -s -U 30 listen=pop3s prefork=0
maxchild=50
# At least one form of LMTP is required for delivery
# (you must keep the Unix socket name in sync with imap.conf)
lmtpcmd=lmtpd listen=11.0.0.12:lmtp prefork=0
maxchild=20
lmtpunixcmd=lmtpd listen=/var/run/cyrus/socket/lmtp
prefork=0 maxchild=20
# --
# useful if you need to give users remote access to sieve
# by default, we limit this to localhost in Debian
sieve cmd=timsieved listen=localhost:sieve
prefork=0 maxchild=100
# this one is needed for the notification services
notify cmd=notifyd
listen=/var/run/cyrus/socket/notify proto=udp prefork=1
# --- Murder frontends -
# enable these and disable the matching services above,
# except for sieve (which deals automatically with Murder)
# mupdate database service - must prefork at least 1
# (mupdate slaves)
#mupdate cmd=mupdate listen=3905 prefork=1
# (mupdate master, only one in the entire cluster)
#mupdate cmd=mupdate -m listen=3905 prefork=1
# proxies that will connect to the backends
#imap cmd=proxyd listen=imap prefork=0 maxchild=100
#imaps cmd=proxyd -s listen=imaps prefork=0
maxchild=100
#pop3 cmd=pop3proxyd listen=pop3 prefork=0 maxchild=50
#pop3s cmd=pop3proxyd -s listen=pop3s prefork=0
maxchild=50
#lmtp cmd=lmtpproxyd listen=lmtp prefork=1 maxchild=20
# --
}
EVENTS {
# this is required
checkpoint cmd=/usr/sbin/ctl_cyrusdb -c period=30
# this is only necessary if using duplicate delivery suppression
delprunecmd=/usr/sbin/ctl_deliver -E 3 at=0401
# this is only necessary if caching TLS sessions
tlsprunecmd=/usr/sbin/tls_prune at=0401
# para evitar squat failed en log
squattercmd=/usr/sbin/squatter -r * period=240
#squatter_1 cmd=/usr/bin/nice -n 19 /usr/sbin/squatter -s
-r user period=240
}
Any idea?
Thanks
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: better techniques to identify and remove zero-day viruses from cyrus store sought
John Crawford wrote: Sieve is during delivery to the cyrus store though. As we have the capability to identify hazards to our users, I'd like to be able to exercise central strategies improve their quality of life. So I seek tools to leverage after detection to aid with removal or remediation. Maybe would be nice to have a just-in-time scan interface at the cyrus message level just as a message is being accessed. CPU processing is getting cheaper all the time. Hmm, this is an interesting problem. At one extreme, you're changing the mailstore or connection while the user is logged in, which could result in some confusion (and possibly trigger some client software issues). At the other extreme, you may have an account that hasn't been checked for weeks, so it's fine to remove malicious messages that have accumulated due to lack of detection before delivery. You also have to be careful not to remove messages that have been forwarded to your support address, as they will contain strings that may trigger detection. To handle all cases safely, you'd probably want to script using Cyrus::IMAP::Shell, so all changes are performed via IMAP. You can do this safely with Cyrus because it supports concurrent R/W access. Instead of deleting these messages, you'll want to put them in a quarantine account so you can restore them in the case of false positives. I'm still not sure I'd be comfortable doing this beneath the nose of a logged in user. I'd also hesitate to touch anything outside the INBOX (and any quarantine folders you provide), since it can be assumed that the message was moved due to user action. I'd probably test this for a long time only on accounts that aren't being checked regularly (this also has the benefit of reducing the size of abandoned accounts). Have you found that the risks justify this effort? Are your ClamAV scans of the mailstore turning up anything? Are they serious threats? 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: better techniques to identify and remove zero-day viruses from cyrus store sought
Jorey Bump wrote: Have you found that the risks justify this effort? Are your ClamAV scans of the mailstore turning up anything? Are they serious threats? I've just scanned a mailstore with ClamAV, and about 95% of the 'FOUND' infected files were false positives. Here there be dragons. 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: Problem connections cyrus
On Wed, 22 Aug 2007, Sera wrote:
Sorry for my poor English:
I have problems with cyrus.
it's block 10-20 times a day, all days.
Don't crash, but suddenly don't accept any connections and the mua
display the message the server reject the connection, or max number
of connections reached.
I'm used two hosts:
1- debian sarge with cyrus and postfix
2- debian etch with postfix
The version of cyrus is 2.1.18-1+sarge2
My cyrus.conf is it:
# Debian defaults for Cyrus IMAP server/cluster implementation
# see cyrus.conf(5) for more information
#
# All the tcp services are tcpd-wrapped. see hosts_access(5)
# $Id: cyrus.conf,v 1.16 2003/11/05 01:04:22 hmh Exp $
START {
# do not delete this entry!
recover cmd=/usr/sbin/ctl_cyrusdb -r
# this is only necessary if using idled for IMAP IDLE
# this is NOT to be enabled right now in Debian builds
#idled cmd=idled
# this is useful on backend nodes of a Murder cluster
# it causes the backend to syncronize its mailbox list with
# the mupdate master upon startup
#mupdatepush cmd=/usr/sbin/ctl_mboxlist -m
# this is recommended if using duplicate delivery suppression
delprunecmd=/usr/sbin/ctl_deliver -E 3
# this is recommended if caching TLS sessions
tlsprunecmd=/usr/sbin/tls_prune
}
# UNIX sockets start with a slash and are absolute paths
# you can use a maxchild=# to limit the maximum number of forks of a service
# you can use babysit=true and maxforkrate=# to keep tight tabs on the
service
# most services also accept -U (limit number of reuses) and -T (timeout)
SERVICES {
# --- Normal cyrus spool, or Murder backends ---
# add or remove based on preferences
imapcmd=imapd -U 30 listen=imap prefork=0
maxchild=100
imaps cmd=imapd -s -U 30 listen=imaps prefork=0
maxchild=100
#pop3 cmd=pop3d -U 30 listen=pop3 prefork=0
maxchild=50
#pop3s cmd=pop3d -s -U 30 listen=pop3s prefork=0
maxchild=50
The maxchild settings in cyrus.conf above limit the maximum number of
connections allowed for each service. You might want to increase those
numbers to match the number of connections you expect to receive.
Andy
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
