Cyrus-IMAPD, Postfix, LDAP, spamc and aliases
Hello!
I'm building an fresh multidomain environment with Debian Lenny. I've
installed and configured postfix, spamc and cyrus-imapd and things are
running almost smoothly.
I can send email everywhere just fine via SMTPS, including my own host.
Since I'm on a testing stage I haven't tried to actually use that as an MX
for any host, so for now I'm stuck at local delivery for incoming mail.
Currently I have only one user, let's call him Jack Doe, and user account
is stored to LDAP. I've manually created the account and folders for cyrus
and I can login and use the service just fine via IMAP. Now when I try to
send mail to jack@myhost.foo it's delivered just fine via local
SMTP(S) and things work as they should.
The problem now is that Jack has fw aliases, let's say j...@myhost.foo and
sa...@myhost.foo. These addresses doesn't work and I'm not sure if this is
an postfix or an cyrus -problem. Postfix recognizes the alias and tries to
deliver it via LMTP, just the same way than it does with 'actual' address.
However since there's no mailbox for 'j...@myhost.foo' cyrus LMTP fails:
cyrus/lmtpunix[12084]: verify_user(myhost.foo!user.jack) failed: Mailbox
does not exist
cyrus/lmtpunix[12084]: telling master 1
Now, based on what I understand, postfix should expand aliases (from the
LDAP) and deliver the mail with 'actual' address, instead of aliased one.
I have these on my conf:
alias_maps = ldap:/etc/postfix/ldap-alias.cf
virtual_alias_maps = ldap:/etc/postfix/ldap-alias.cf
And, again as far as I can understand, aliases itself seem to work. It's
the transport which doesn't work as it should. On master.cf I have this:
cyrus unix - n n - - pipe flags= user=cyrus argv=/usr/sbin/cyrdeliver -r
${sender} -m ${extension} ${recipient}
I've tried to search solution via google and pretty much every other way I
can imagine, but couldn't find any solution. The closest thing I found was
that some other have had this same problem, but most of the solutions were
"Works for me", which isn't really helpful on my case.
Hopefully someone can help me out here, thanks in advance.
--
Take
Re: Cyrus-IMAPD, Postfix, LDAP, spamc and aliases
mouss wrote: > do never say "this does that and that does this". show what things do > instead. With all due respect, we don't trust you judgement. Unjustified > claims are useless. so please try to convince us. tell us what happens. > don't tell us what you think. I'm sorry. I got the welcome mail but didn't read the link as I obviously should have done. The problem however got resolved and it was an pure example of PEBKAC. I've had made too many changes with too many hours awake and things got f*'d. Some sleep and fresh thinking sorted that out quite easily and now I can move on. Sorry again for my incorrect behaviour, next time I promise to read guidelines before writing anything. I should've known better, but obviously I didn't. Thank you for your reply anyways. -- Take
Best practice to drop spam with virtual mailboxes
Hello! I've been trying to figure out the best way to drop/sort spam with virtual users. All documentation I could find didn't fit to our virtual configuration and I'm a bit confused what's the best way to drop spam. Our setup is postfix+cyrus-imapd+spamassassin. Users have access to sieve via roundcube plugin and we'd like to keep sieve out of this anyways. The goal is to apply an filter based on SA's score, so that if the score is > 10 drop the mail and if it's less than 10 but still spam, deliver it to user/myser/INBOX.Junk. The latter is optional step, main priority is to drop "certain spam" (score over 10) so that user won't ever see it. Currently mail goes trough spamassassin (smtp content-filter) and virtual-delivery goes trough cyrus lmtp. I was wondering if I could create another content-filter for lmtp at master.cf (lmtp -o content_filter=maildrop) and drop/sort junk via that. May be that this approach is just plain stupid and I didn't get it to work anyways. The another approach which came to mind was to use maildrop as an virtual_transport and trigger cyrdeliver from maildrop, but didn't have the time to try this one out. Maybe procmail would do better in this scenario, but I'm not sure. Besides the actual goal I'm interested about the efficiency with each method. I'd like to maintain lmtp-like delivery so that postfix doesn't have to spawn processes for each and every mail going trough. Any help is greatly appreciated. Thank you in advance. -- Take
Re: Best practice to drop spam with virtual mailboxes
On 05/12/2010 11:39 AM, Roman Medina-Heigl Hernandez wrote: > I have a similar setup. What I do is using sieve. My script for mailbox > You have an extra advantage with this method: users may choose to edit > his/her filter so he/she could exactly decide whether he/she want junk mail > to be dropped, moved to a spam-folder, and the score threshold too. This is disadvantage in our case. We currently have spam filtering set up like this, and it's of course working like it should. But now, since our users aren't that technically advanced, it happens almost daily basis that someone messes around with the filter rules via managesieve-plugin on roundcube and destroys the spam-adjustment as well. Unfortunately those clueless users are the same people who spread their address to newsletters, questionnaires etc, so they receive most spam as well. This is why we'd need a way to do the rough clean before any user has anything to say about that. If you give the user an possibility to shoot him/herself into the foot they'll pull the trigger immediately. So, thank you for your reply, but that's not the solution we're after. -- Take
Re: Best practice to drop spam with virtual mailboxes
On 05/12/2010 06:55 PM, Dennis Guhl wrote: > I don't know if cyrus can do something similar, but I think you want > something like sieve_before in Dovecot: I wish it could, but it can't. I found this as well, but change to dovecot isn't something we'd like to do. So this doesn't help either. Thanks anyway. -- Take
