>> Here are all the sendmail and postfix entries in rc.conf:
>>
>> sendmail_enable="NO"
>> sendmail_submit_enable="NO"
>> sendmail_outbound_enable="NO"
>> sendmail_msp_queue_enable="NO"
>> postfix_enable="YES"
>> dovecot_enable=YES
On Fri, Feb 10, 2012 at 4:44 PM, CSS <c...@morefoo.com> wrote:
>
> Drop all that and put in sendmail_enable="NONE"
>
> That will disable the client queue and all that other junk.
>
> When set to "NO", that just disables the main port 25 listener. Setting
> it to "NONE" kills everything and lets an alternate MTA handle everything.
>
> The handbook seems to contradict this, but in my experience, "NONE" works
> while setting all the individual sendmail_* stuff to "NO" generally
> doesn't.
>
> Charles
Thanks, Charles.
Setting 'sendmail_enable="NONE" (and removing the other entries) has
no effect on my system (FreeBSD 8.0).
I still get the following error from command-line maill:
[satyr ~]$ mail -s test jorge
test
.
[satyr ~]$ WARNING: RunAsUser for MSP ignored, check group id
(egid=1002, want=25) can not chdir(/var/spool/clientmqueue/): Permission denied
Program mode requires special privileges, e.g., root or TrustedUser.
satyr# tail /var/log/maillog
Feb 9 09:16:00 satyr sendmail[63415]: NOQUEUE: SYSERR(jorge): can not
chdir(/var/spool/clientmqueue/): Permission denied
Here are the permissions and owners of the queue:
satyr# ls -ld /var/spool/clientmqueue/
drwxrwx--- 2 smmsp smmsp 512 Feb 9 06:57 /var/spool/clientmqueue/
clientmqueue is a sendmail queue. It seems that, at some point, even
though there's not a sendmail MTA listening on port 25, some vestige
of sendmail's MSP still directs the email toward clientmqueue and then
pulls out, leaving postfix to unsuccessfully try to drop it into
clientmqueue, which is owned by smmsp. smmsp is definitely a sendmail
user/group. The mail ordinarily sits in clientmqueue waiting to be
piped to the sendmail MTA. But, of course, I've disabled sendmail in
rc.conf and mailer.conf, and postfix has no facility for entering or
processing clientmqueue, so the mail is lost.
It looks like FreeBSD has the user over a barrel: the last troublesome
bits of sendmail's MSP appear to be ineradicable. You either live
with sendmail for local mail (postfix still works for Internet mail),
or you try to kill sendmail and lose the local messages. If anyone
has successfully gotten around this, I'd appreciate hearing how it was
done.
I did find this one explanatory post that offers a partial solution
that I may try:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Matthew Seaman m.seaman at infracaninophile.co.uk
Thu Sep 2 06:02:43 PDT 2004
That's part of the workings of sendmail. /var/spool/clientmqueue is
the holding area used by the MSP (Mail Submission Protocol) sendmail
instance before it injects the messages into the main MTA (Mail
Transport Agent) sendmail instance.
You'll get the effect you see by not running any sendmail daemons:
unix mailers will send e-mail by piping the message into the stdin of
sendmail, and sendmail will save the message in
/var/spool/clientmqueue for safe keeping before trying to connect to
the MTA to get the message delivered. Normally there would be a
'queue runner' MSP sendmail instance which every half hour would retry
sending any message that couldn't be sent immediately. Each message
will generate a 'df' (message routing info) and 'qf' (message headers
and body) file. You can list out all of the messages and their status
by:
# mailq -v -Ac
A FreeBSD system basically assumes that it has e-mail connectivity
available to it: eg. any output from cron jobs will be e-mailed back
to the job's owner. There will also be the daily, weekly and monthly
periodic script output. You can modify /etc/periodic.conf to redirect
the periodic script output to log files rather than e-mail. See
periodic.conf(5).
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Jorge Luis Gonzalez <jlg.in...@gmail.com>
This email optimized for teletypes.
