Answer: Sendmail configuration on Debian using Mailscanner

[Harry Hanson]

Oh.. Could you do me a favor and do a diff between the modified
/usr/share/sendmail/sendmail and your original? Thanks a lot. 

-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On Behalf
Of Andreas Kasa
Sent: Monday, September 29, 2003 6:15 AM
To: MAILSCANNER at JISCMAIL.AC.UK
Subject: Re: Answer: Sendmail configuration on Debian using Mailscanner

A diff from my working sendmail.conf to a stock sendmail.conf give me the
following results.

[root at qtip /home/kasa] # diff /etc/mail/sendmail.conf
/home/kasa/sendmail.conf
62c62
< DAEMON_PARMS=" -OPrivacyOptions=noetrn -ODeliveryMode=queueonly
-OQueueDirectory=/var/spool/mqueue.in";
---
> DAEMON_PARMS="";
80c80
< DAEMON_MAILSTATS="Yes";
---
> DAEMON_MAILSTATS="No";
100c100
< QUEUE_INTERVAL="2";
---
> QUEUE_INTERVAL="10";
145c145
< MSP_MAILSTATS="${DAEMON_MAILSTATS}";
---
> MSP_MAILSTATS="No";

And yes, on my debian stable woody all is running fine.

A quote from a old mail on this list

Am 06.03.2003 21:06 Uhr schrieb "Hancock, Scott" unter
<HancockS at MORGANCO.COM>:

> Okay... Just typing off the cuff here so don't expect too much <G>
> 
> In order to get sendmail in Debian to run in a separate listener/queue 
> runner mode all you need to do is change the DAEMON_PARMS line from
> 
> DAEMON_PARMS="";
> 
> to
> 
> DAEMON_PARMS="-OPrivacyOptions=noetrn -ODeliveryMode=queueonly 
> -OQueueDirectory=/var/spool/mqueue.in";
> 
> And create the /var/spool/mqueue.in directory of course... but that's 
> really all you need to do.
> 
> I haven't tested it in woody, only in sarge but I did write a brief 
> note to the sendmail maintainer who said that it should be fine. He 
> also mentioned that the fact that splitting the sendmail process into 
> a listener and queue runner is included in the conf file at all is due 
> to an early user of mailscanner asking for the feature.
>
> The details of how/why it does what it does are in the file 
> /usr/share/sendmail/sendmail. That's really what gets run when the 
> /etc/init.d/sendmail script gets fired off. In there is a bit of logic 
> that just looks to see if parameters are common between the listener 
> and queue runner daemon and either creates one or two daemons to suit.
> Here's the operative bit:
> 
>       # See if we can share the listener and queue-runner daemon:
>       #       * Both must be in daemon mode
>       #       * They must have the same (possibly empty) parameters
>       if [ "$DAEMON_MODE" = "daemon" \
>               -a "$QUEUE_MODE" = "daemon" \
>               -a "$DAEMON_PARMS" = "$QUEUE_PARMS" ]; then
>               SPLIT_DAEMON=0;
>       else
>               SPLIT_DAEMON=1;
>               fi;
> 
> So, by changing the DAEMON_PARMS to anything other than the 
> QUEUE_PARMS a second process gets spawned by the startup script and 
> everybody is happy (or at least I was).


Am 27.09.2003 0:41 Uhr schrieb "Harry Hanson" unter <harryh at CET.COM>:

> Yes, it has:
> 
> #:/var/spool# ls -l
> total 888
> drwxr-xr-x    3 root     root         4096 Aug 23  2002 cron
> drwxrwsr-x    4 lp       lp           4096 Mar 20  2003 lpd


Mit freundlichen Grüßen aus Frankfurt

--
Andreas Kasa
Systemadministrator

PMG public media group GmbH     andreas.kasa at publicmediagroup.de
Hanauer Landstrasse 136                    Telefon 069-40567-560
60314 Frankfurt                            Telefax 069-40567-499
http://www.publicmediagroup.de             Mobil    0163-4056113
Geschaeftsfuehrer: Inge Marx-Jansen, Kai Uwe Petry, Manfred Frey
HRB-Frankfurt 25680
> lrwxrwxrwx    1 root     root            7 Jul 11  2002 mail -> ../mail
> drwxr-x---    5 mail     mail         4096 Sep 26 02:35 mailscanner
> drwxr-s---    2 root     smmsp      872448 Sep 26 15:26 mqueue
> drwxrws---    2 smmsp    smmsp        4096 Sep 26 15:25 mqueue-client
> drwxr-x---    2 root     smmsp        4096 Sep 23 13:43 mqueue.in
> drwxr-xr-x    3 root     root         4096 Mar 20  2003 squirrelmail
> 
> Could you tell me what config files actually changed from the 
> sendmail.conf entry?
> 
> -----Original Message-----
> From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK] On 
> Behalf Of James A. Pattie
> Sent: Friday, September 26, 2003 1:26 PM
> To: MAILSCANNER at JISCMAIL.AC.UK
> Subject: Re: Answer: Sendmail configuration on Debian using 
> Mailscanner
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Harry Hanson wrote:
> | very true :)
> |
> | However my problem was that updating sendmail.conf as advised in the 
> | faq
> |
> | (DAEMON_PARMS="-bd -OPrivacyOptions=noetrn -ODeliveryMode=queueonly
> | -OQueueDirectory=/var/spool/mqueue.in";)
> |
> | Does not work for me, regardless of how I choose to update sendmail
> configs.
> | Has this actually worked for someone? Is this affecting anyone other 
> | than me, and if so, what was the method used to get sendmail to 
> | start in dual daemon mode?
> 
> It works for me on Debian Testing.  Make sure the /var/spool/mqueue.in 
> directory has been created otherwise the instance being spawned will 
> die with an error. :)
> 
> - --
> James A. Pattie
> james at pcxperience.com
>