Sieve Problem
Hi Folks,
a few months ago I set up a new server with Cyrus SASL and IMAPD 2.1.16.
Everything runs perfectly fine, but now I want to enable sieve on that
host. So I set up a line in cyrus.conf like
sieve cmd="timsieved" listen="sieve" prefork=0
and now I can telnet like "telnet localhost sieve"
and get the following result:
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
"IMPLEMENTATION" "Cyrus timsieved v2.1.16"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
relational regex"
OK
The thing about it is that I can't login with sieveshell. So I searched
the lists and found that there's a line missing like "SASL PLAIN" in my
output above. One posting said that I should install the sasl libs, but
that is what I did when I installed SASL from source - and the imap
users can log in fine using the running "saslauthd -a shadow" and PLAIN
login.
So I really don't understand what the problem is - please can anybody
help me?
cyrus.conf and imap.conf are included hereby.
Thanks in advance,
Andreas Grimmel
System Administrator
ADDITIVE GmbH
Germany
cyrus.conf:
# standard standalone server implementation
START {
# do not delete this entry!
recover cmd="ctl_cyrusdb -r"
# this is only necessary if using idled for IMAP IDLE
# idledcmd="idled"
}
# UNIX sockets start with a slash and are put into /var/imap/sockets
SERVICES {
# add or remove based on preferences
imap cmd="imapd" listen="imap" prefork=0
pop3 cmd="pop3d" listen="pop3" prefork=0
sieve cmd="timsieved" listen="sieve" prefork=0
# LMTP is required for delivery
lmtpunix cmd="lmtpd" listen="/usr/cyrus/var/socket/lmtp" prefork=0
# this is only necessary if using notifications
# notify cmd="notifyd" listen="/usr/cyrus/var/socket/notify"
proto="udp" prefork=1
}
EVENTS {
# this is required
checkpointcmd="ctl_cyrusdb -c" period=30
# this is only necessary if using duplicate delivery suppression
delprune cmd="ctl_deliver -E 3" period=1440
# this is only necessary if caching TLS sessions
tlsprune cmd="tls_prune" period=1440
}
imapd.conf:
configdirectory: /usr/cyrus/var
partition-default: /usr/cyrus/var/spool
altnamespace: yes
unixhierarchysep: yes
defaultacl: anyone lrswipcda
admins: cyrus root
allowplaintext: yes
allowanonymouslogin: no
sasl_mech_list: PLAIN
#autocreatequota: 1
#reject8bit: no
#quotawarn: 90
#timeout: 30
#poptimeout: 10
#dracinterval: 0
#drachost: localhost
sasl_pwcheck_method: saslauthd
sendmail: /usr/sbin/sendmail
sievedir: /usr/cyrus/sieve
---
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: Problem with cyrus and deleting a message with a virus.
Mark London schrieb: Hi - We are running uvscan, and it will delete a cyrus message file that contains a virus. Of course, cyrus doesn't know that the message is deleted, so it still shows that message, albeit it shows up as being from Unknown with (no subject). The problem is that this message can't be deleted, no matter what method the user tries. The only solution we have found is to replace the deleted message with a dummy file, and then it can be deleted. We can't be the only one having this problem. Do other people run virus scanning software, like uvscan, on their server? Thanks. - Mark If you're messing around with the internal data stores of a program, and then you get upset when the program doesn't work, I'd say that you've created your own problem. I'm not messing with it, uvscan is doing it. Is there a better software alternative that will delete viruses on the server? Are we the only people using cyrus that are running virus scanning software on the server? Btw, I would think cyrus should be able to handle the simple case of a missing single file. I should be able to delete a message for which the message file is already missing. We're not talking about a complex database file structure here. It's a single file with a single message. Did I get you right that you simply run the scanner via cron to delete infected files? Why - if you don't want to put it on a proxy - don't you run amavis together with uvscan when sendmail attempts to deliver the mail locally via cyrus-deliver? This is what we're doing here, and it works really fine. Infected Mails won't reach the cyrus spool area and therefore cause no problem. One thing left: when a user moves a mail into the imap folders from his email client, it could possibly be infected. So we do two things about that: Every user has a server-controlled Anti-Virus System (Symatec AV Corporate) running that makes sure the clients itself are clean. Second is, we run uvscan via cronjob also, but don't let it quarantine oder delete infected files automatically. If it really should find a virus that has stolen itself into a client or the cyrus spool, we delete it manually. This never happened up till now, it's just a second 'Line of Defense' for absolute safety. Running this system really works quite perfect, never had any problem up till now. Regards, Andreas Grimmel
