7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] filtering and for...
FromSent OnAttachments
sysa...@sunet.com.auOct 27, 2006 3:59 pm 
sysa...@sunet.com.auOct 27, 2006 4:01 pm 
Jay LeeOct 28, 2006 9:23 am 
sysa...@sunet.com.auOct 30, 2006 12:22 am 
Jay LeeOct 30, 2006 6:25 am 
Gordon MessmerOct 30, 2006 4:00 pm 
Alessandro VeselyOct 31, 2006 3:14 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] filtering and forwarding mail to another server helpActions...
From:Jay Lee (jl@pbu.edu)
Date:Oct 28, 2006 9:23:17 am
List:net.sourceforge.lists.courier-users

sysa@sunet.com.au wrote:

Hi all. We're trying to set up a courier mail server that will filter all e-mail, and add SpamAssassin headers, and then forward on to another mail server. We also have all our users in LDAP. We can't get it to work, and any general tips would be appreciated.

General tip, why do you need a second mail system for this? Postfix could just call maildrop itself which would be responsible for calling SA and filtering. The simpler your system is, the fewer problems you'll have, but you may have your reasons for having 2 servers...

The way we've approached the problem so far is to use courierlocal to push the messages through maildrop, which adds the SpamAssassin headers, and then forwards the message to an installation of the "postfix" mail server. The problem with this approach is that it keeps saying:

Oct 27 17:30:59 jupiter courierlocal: No such file or directory Oct 27 17:30:59 jupiter courierlocal: id=008C805D.4541B5AE.00003E20,from=<sysa@sunet.com.au>,addr=<pb@sunet.com.au>,status: deferred

Basically, if we create home directories for all our users on this machine, then it will work. But we don't *want* them to have home directories here.

Why not? If they don't have accounts they can't do anything with them anyway. I have some users forwarding on to a old install of Mercury/Pegasus Mail, they exist in LDAP so all Courier has for them is a home directory. I have LDAP_MAILROOT set to /var/maildir and LDAP_HOMEDIR set to the uid attribute. I have a cron script that checks for new or removed LDAP accounts so I don't have to do anything when new users are created in the LDAP directory.

Jay

I looked at using the authldap stuff instead of pam_ldap, but a) this seems to require home directories anyway, and b) I wasn't 100% sure that courier-mta used this, since it seemed to be oriented to courier-imap.

What would be ideal is if we could work out some way to push the e-mail through maildrop, and then into the esmtp output module for remote delivery.

Any ideas on either a different approach or help towards fixing our problems would be appreciated.