Request 177 was acted upon.
_________________________________________________________________________
URL: https://rt.openpkg.org/id/177
Ticket: [OpenPKG #177]
Subject: fsl and LOG_MAIL facility issue in MTAs and procmail
Requestors: [EMAIL PROTECTED]
Queue: openpkg
Owner: Nobody
Status: new
Transaction: Ticket created by thl
Time: Mon Jul 07 17:06:22 2003
_________________________________________________________________________
Date: Mon, 7 Jul 2003 09:36:00 +0200
From: Thomas Lotterer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [CVS] OpenPKG: openpkg-src/ssmtp/ fsl.ssmtp rc.ssmtp ssmtp.spec openpk...
Reply-To: [EMAIL PROTECTED]
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.4i
Organization: Cable & Wireless Deutschland GmbH, Munich, Germany.
On Thu, Jul 03, 2003, Ralf S. Engelschall wrote:
> On Thu, Jul 03, 2003, Thomas Lotterer wrote:
>
> > [...]
> > +ident (.+)/mail q{
> > [...]
>
> Isn't this too generic? This way perhaps also procmail's or whatever
> messages are written to ssmtp.log if they are of facility "mail", aren't
> they? Doesn't ssmtpd use a reasonable openlog(3) with its name?
>
I knew what i did when i decided to commit this. The issue is documented
in OpenPKG ticket #117, search for LOG_MAIL and currently find that
topic for procmail and ssmtp, also see checkin 10179. Excerpt/ summary
here:
https://rt.openpkg.org/Ticket/Display.html?id=117
[...]
Note the interesting LOG_MAIL issue!
procmail http://cvs.openpkg.org/chngview?cn=10179
[...]
Note that LOG_MAIL is not an issue because ssmtp conflicts with other MTAs.
ssmtp http://cvs.openpkg.org/chngview?cn=10181
http://cvs.openpkg.org/chngview?cn=10179 [procmail]
[...] avoid log duplication by sendmail (and probably any MTA) whose
fsl is catching all logs being tagged with LOG_MAIL facility
The problem is that sendmail has no single ident and the fsl.sendmail
catches (.+)/mail. So i decided to let all MTAs, including ssmtp, to use
exacly this regex. The drawback is that third party applications like
procmail need to be patched to never use the LOG_MAIL facility.
If you don't like this, let me say i don't like this either. But the
alternatives are likekly to open a can of worms.
We could try to patch sendmail, but it uses variables for creating the
ident and it has a dozend or so calls to openlog(3).
An other alternative would be to act more like the orginal syslog and
create logfiles not for a single application but for a facility. This
would intermix sendmail and procmail log information into a LOG_MAIL
file.
Both approaches were too heavy for me to be introduced on the fly so i
patched procmail. Having fsl'ized all CORE, BASE and PLUS packages now,
it is the only application that used the LOG_MAIL facility so far.
A politician in our beginning 21st century would describe this incident
as "collateral damage". In public words it means "we targeted sendmail
but accidentally hit procmail".
--
[EMAIL PROTECTED]
Development Team, Operations Northern Europe, Cable & Wireless
