6 messages in net.sourceforge.lists.courier-users[courier-users] reformatting of certa...
FromSent OnAttachments
Uwe FrickeMar 30, 2006 4:17 am 
Jay LeeMar 30, 2006 5:33 am 
Jay LeeMar 30, 2006 8:08 am 
Uwe FrickeMar 30, 2006 8:26 am 
Sam VarshavchikMar 30, 2006 3:15 pm 
Uwe FrickeMar 31, 2006 12:27 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:[courier-users] reformatting of certain email adresses - how is it done?Actions...
From:Uwe Fricke (u.fr@unitb.de)
Date:Mar 30, 2006 4:17:40 am
List:net.sourceforge.lists.courier-users

Hello,

coming from qmail, I got a problem with a tiny administration task on an already running courier mta, perhaps someone can point me in the right direction. I have no documentation regarding the server architecture and setup, but here's what i figured out:

The mailserver (let's call him Courier) manages roughly 15.000 mail accounts. A very small percentage of mails arriving at Courier is forwarded to an internal server (let's call him Notes, because a Lotus Notes application sits there), and handled there. All other emails are handled locally, and stored in /home/vmail.

The problem is, a new email adress has been set up on Notes. Now, this person can't retrieve mails from the outside, because courier doesn't know about the new person and doesn't forward his incoming mails to Notes. As Notes already manages about 20 email accounts, I was hoping to find the names of these persons in some courier configuration files, but no luck so far.

Below I pasted the relevant log, showing a successful and an unsuccessful delivery. The logs below show that, right after courieresmtpd receives a new message, it somehow formats acco@company.com to acco@internal.company.com, after virus-checking courierd takes over, and the email get's delivered to Notes. This formatting isn't done with the newly created email account, and right after courieresmtpd receives this message, a lookup with ldap is done - this isn't necessary.

I would appreciate any hints on where this configuration is done (in /usr/lib/courier, a 'grep -ri <validemailaccount> *' returned nothing. in /etc/, there aren't any courier config files.).

Regards, Uwe

An excerpt from the log, when sending a mail to the not-yet-working email account (IP adresses and other identifiers replaced with dummies):

mail courieresmtpd: started,ip=[::ffff:<externalIp>] mail authdaemond: received userid lookup request: newE@company.com mail authdaemond: authldap: trying this module mail authdaemond: using search filter: (uid=newE@company.com) mail authdaemond: number of entries returned: 0 (but we need exactly 1) mail authdaemond: authldap: REJECT - try next module

And here's an excerpt from the log, when sending a mail to working internal email account:

mail courieresmtpd: started,ip=[::ffff:<externalIp>] mail ClamCour[15881]: Listener: Launched Inspector for scan mail ClamCour[16580]: Inspector: Scan under progress... mail courierd: newmsg,id=0193C9AA.442B9DF9.000040C3: dns; mx1.company.com (mx.comp.com [::ffff:<externalIp>]) mail courierd: started,id=0193C9AA.442B9DF9.000040C3,from=<me@myplace.com>,module=esmtp,host=internal.company.com,addr=<vali@internal.company.com> mail courierd: Waiting. shutdown time=none, wakeup time=none, queuedelivering=1, inprogress=1 mail courieresmtp: id=0193C9AA.442B9DF9.000040C3,from=<me@myplace.com>,addr=<vali@internal.company.com>: 250 Message accepted for delivery