Murder + Sieve + multiple backends problem
Hi
currently, I test a Cyrus IMAP Murder v2.3.13-openpkg on a solaris
sparc host. While the murder setup went all fine and mail comes in and
can be read by users, there is one thing left I could not fix.
If a user has a sieve script like
#Mail filter rules for wolf
#Generated by wolf using SmartSieve 1.0.0-RC2 2008/11/25 09:02:43
require [fileinto];
if allof (header :contains X-Spam-Status Yes,) {
fileinto INBOX.Spam-Tagged;
}
and the Folder INBOX.Spam-Tagged is located on a different backend
server as the INBOX folder, the sieve script does not work. I get the
following errors on the backend server where the INBOX is located:
lmtp[27859]: sieve runtime error for wolf id
[EMAIL PROTECTED]: Fileinto: Mailbox
does not exist
Is there any way to tell sieve to move mails to the correct backend
server ?
Regards,
Jürgen Wolf
--
email: [EMAIL PROTECTED]
gilb: Fraunhofer-Institut fuer Digitale Medientechnologie IDMT
98693 Ilmenau, Ehrenbergstr. 31
Tel.: +49 3677 467-234 Fax: +49 3677 467-467
smime.p7s
Description: S/MIME cryptographic signature
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: Murder + Sieve + multiple backends problem
Juergen Wolf wrote:
Hi
currently, I test a Cyrus IMAP Murder v2.3.13-openpkg on a solaris
sparc host. While the murder setup went all fine and mail comes in and
can be read by users, there is one thing left I could not fix.
If a user has a sieve script like
#Mail filter rules for wolf
#Generated by wolf using SmartSieve 1.0.0-RC2 2008/11/25 09:02:43
require [fileinto];
if allof (header :contains X-Spam-Status Yes,) {
fileinto INBOX.Spam-Tagged;
}
and the Folder INBOX.Spam-Tagged is located on a different backend
server as the INBOX folder, the sieve script does not work. I get the
following errors on the backend server where the INBOX is located:
lmtp[27859]: sieve runtime error for wolf id
[EMAIL PROTECTED]: Fileinto: Mailbox
does not exist
Is there any way to tell sieve to move mails to the correct backend
server ?
From the web site [http://cyrusimap.web.cmu.edu/ag.html section 2.3]:
If a SIEVE http://www.cyrusoft.com/sieve script is present, the
lmtp proxy server must do the processing as the end result of the
processing may result in the mail message going to a different back
end server than where the user's INBOX is. /Note that the current
implementation runs SIEVE on the backend servers, and holds the
requirement that all of a user's mailboxes live on the same backend./
So, you should heed this warning.
-nic
--
Nic Bernstein [EMAIL PROTECTED]
Onlight llc. www.onlight.com
2266 North Prospect Avenue #610 v. 414.272.4477
Milwaukee, Wisconsin 53202-6306 f. 414.290.0335
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: Murder + Sieve + multiple backends problem
On 01 Dec 2008, at 10:17, Nic Bernstein wrote: From the web site [http://cyrusimap.web.cmu.edu/ag.html section 2.3]: If a SIEVE script is present, the lmtp proxy server must do the processing as the end result of the processing may result in the mail message going to a different back end server than where the user's INBOX is. Note that the current implementation runs SIEVE on the backend servers, and holds the requirement that all of a user's mailboxes live on the same backend. So, you should heed this warning. While the code is written this way, in an environment where the backends are able to talk to each other, it wouldn't take a ton of work to remove this restriction. :wes 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: Murder + Sieve + multiple backends problem
Wesley Craig wrote: Note that the current implementation runs SIEVE on the backend servers, and holds the requirement that all of a user's mailboxes live on the same backend. WC While the code is written this way, in an environment where the WC backends are able to talk to each other, it wouldn't take a ton of WC work to remove this restriction. Cross-store SIEVE is theoretically the sort of thing that ought to favour the unified murder design over a conventional layered one... [light the blue touchpaper and retreat to a safe distance] But the answer to the original question is that this is known not to work - and yes, that is both counter-intuitive for users and inconvenient for administrators. /* FIXME */ Duncan -- Duncan Gibb, Technical Director Sirius Corporation plc - The Open Source Experts http://www.siriusit.co.uk/ Tel: +44 870 608 0063 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: Murder + Sieve + multiple backends problem
On 01 Dec 2008, at 12:18, Duncan Gibb wrote: Cross-store SIEVE is theoretically the sort of thing that ought to favour the unified murder design over a conventional layered one... Absolutely, the backend with the INBOX and SIEVE scripts would need to know have to have a listing in mailboxes.db for the remote mailbox. As far as the code goes, sieve_fileinto() would probably work as-is. deliver_mailbox() on the other hand would have to do an mlookup() and behave more like cmd_append() does if the mailbox was remote. Not a large undertaking, tho. :wes 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
Combination of postfix + cyrus (virtdomains) problems
Hello,
I want to be able to run all of these IMAP mailboxes on one machine:
* [EMAIL PROTECTED]
* [EMAIL PROTECTED]
At a later stage, I want to run mailboxes like [EMAIL PROTECTED]
All with their distinct login ID through ptloader/LDAP.
So I'm testing with [EMAIL PROTECTED] as this account is not normally
receiving emails so far.
I've got a general postfix SMTP server that is capable of redirecting emails
for [EMAIL PROTECTED] to the correct server (imap4).
On imap4 I have been playing around with virtdomains (as I am supposed to)
and am currently giving up, because I don't see anymore why it doesn't work
:D
Here's my (imap4) postconf -n:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debug_peer_list = option-d.co.uk
html_directory = no
inet_interfaces = 192.168.123.17
local_recipient_maps = ldap:ldaplocal
mail_owner = postfix
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = option-d.co.uk, tenantvet.net mydomain =
chiswick.itpassion.com myhostname = imap4.chiswick.itpassion.com
mynetworks_style = subnet newaliases_path = /usr/bin/newaliases
queue_directory = /var/spool/postfix readme_directory =
/usr/share/doc/postfix-2.4.5/README_FILES
relayhost = smtp.chiswick.itpassion.com
sample_directory = /usr/share/doc/postfix-2.4.5/samples
sender_canonical_maps = ldap:ldapsender
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpd_helo_required = yes
smtpd_recipient_restrictions = reject_invalid_hostname,
reject_non_fqdn_sender, reject_non_fqdn_recipient,
reject_unknown_sender_domain, reject_unknown_recipient_domain,
reject_unauth_pipelining, permit_mynetworks, permit_sasl_authenticated,
reject_unauth_destination, reject_rbl_client zombie.dnsbl.sorbs.net,
reject_rbl_client list.dsbl.org, reject_rbl_client sbl.spamhaus.org, permit
smtpd_sasl_auth_enable = yes virtual_alias_maps = ldap:ldapvirtual
and here's my master.cf
#
# Postfix master process configuration file. For details on the format # of
the file, see the master(5) manual page (command: man 5 master).
#
# ==
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==
smtp inet n - n - - smtpd
smtps inet n - n - - smtpd
-o smtpd_sasl_auth_enable=yes
pickupfifo n - n 60 1 pickup
cleanup unix n - n - 0 cleanup
qmgr fifo n - n 300 1 qmgr
tlsmgrunix - - n 1000? 1 tlsmgr
rewrite unix - - n - - trivial-rewrite
bounceunix - - n - 0 bounce
defer unix - - n - 0 bounce
trace unix - - n - 0 bounce
verifyunix - - n - 1 verify
flush unix n - n 1000? 0 flush
proxymap unix - - n - - proxymap
smtp unix - - n - - smtp
relay unix - - n - - smtp
-o fallback_relay=
showq unix n - n - - showq
error unix - - n - - error
retry unix - - n - - error
discard unix - - n - - discard
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
anvil unix - - n - 1 anvil
scacheunix - - n - 1 scache
cyrus unix - n n - - pipe
flags= user=cyrus argv=/usr/lib/cyrus-imapd/deliver -r ${sender} -m
${extension} ${recipient}
This all pretty standard, as I use that across 3 other mailservers (where I
serve one domain each).
Here's my 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
idled cmd=idled
}
# UNIX sockets start with a slash and are put into /var/lib/imap/sockets
SERVICES {
# add or remove based on preferences
imap cmd=imapd listen=imap prefork=5
imaps cmd=imapd -s listen=imaps prefork=1
pop3 cmd=pop3d listen=pop3 prefork=3
pop3s cmd=pop3d -s listen=pop3s prefork=1
sieve cmd=timsieved listen=sieve prefork=0
ptloader cmd=ptloader listen=/imap/ptclient/ptsock prefork=1
# these are only
Re: plus addressing over lmtp not working / sam [box] anyone p set
On Thu, Nov 27, 2008 at 10:14 AM, Stefan Pampel [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, it seems that plus addressing not work in my case: postfix configured correctly: main.cf: recipient_delimiter = + master.cf: lmtp unix - - n - - lmtp Mails basically reach the INBOX, but not the folder itself cyrus config: snip altnamespace: yes # even with no does not work virtdomains: userid defaultdomain: foo.bar.org unixhierarchysep: no /snip The folder lam user.user1.spam user1 lrswipcda anyone p The mail header contains To: user1 [EMAIL PROTECTED] Any hints? Does the email goes in the user INBOX at least ? Did you look into the lmtpd.log and postfix.log to check if the delivery looks ok .? Regards Thanks in advance. Stefan Pampel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkuZQgACgkQXXT1nfS2Z+HQZACePaK8zDCOamVl91z+hIhnK8b6 XkMAn2iwps/ZU1Oet+Vg1g+uXWi/uAqM =6YOr -END PGP SIGNATURE- -- / polyformal/ | http://www.polyformal.de / |_/ GPG KEY: 11678845 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 -- Alain Spineux aspineux gmail com May the sources be with you 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
