Re: latest sendmail on testing

2014-05-19 Thread Curt
On 2014-05-18, Harry Putnam rea...@newsguy.com wrote:

|  rea...@newsguy.com... Deferred: 421 4.3.0 collect: Cannot
|  write ./dfs4IGodqZ004450 (bfcommit, uid=0, gid=122): No such file or
|  directory Closing connection to [127.0.0.1]
 `

 Where is sendmail trying to write?  Why is sendmail trying to write to
 something that does not exist?


Look for QueueDirectory in your sendmail.cf file?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/slrnlnka2q.21q.cu...@einstein.electron.org



Re: latest sendmail on testing

2014-05-19 Thread Harry Putnam
Curt cu...@free.fr writes:

 On 2014-05-18, Harry Putnam rea...@newsguy.com wrote:

|  rea...@newsguy.com... Deferred: 421 4.3.0 collect: Cannot
|  write ./dfs4IGodqZ004450 (bfcommit, uid=0, gid=122): No such file or
|  directory Closing connection to [127.0.0.1]
 `

 Where is sendmail trying to write?  Why is sendmail trying to write to
 something that does not exist?


 Look for QueueDirectory in your sendmail.cf file?

Thank you sir... that was a very succinct pointer, and a direct hit.

Since posting that problem... I tried for the second time, a complete
uninstall of all of sendmail... including repeated --purge on conf
files.  Once all directories all pkgs and all conf were removed.

Reinstalled the whole works again.  This time, after moving the
problematic lines in sendmail.mc... and making a number of
customizations there... that is, I stuck in a configuration from
another debian box that has worked for several years and with fingers
crossed ... restarted sendmail.

By god... it worked.  So sendmail is now sending and receiving quietly
as it ought.

Thank you all for huge amounts of patience and a helpful spirit.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87iop18v07@newsguy.com



Re: latest sendmail on testing

2014-05-18 Thread Harry Putnam
Filip fi...@fbvnet.be writes:

 On Sat, 17 May 2014 17:08:10 -0400
 Harry Putnam rea...@newsguy.com wrote:

 Filip fi...@fbvnet.be writes:
 
 [...]
 
  I would have thought the install of a pkg would also create any
  needed directories for the pkg to operate.
  
  Is it normal for user to create these things?
 
 
  No, it's not normal. The post-install scripts should create a
  working initial configuration where it at least starts up.
 
  Try reinstalling with the --reinstall option.
 
  apt-get install sendmail --reinstall
  apt-get install sendmail-base --reinstall
  apt-get install sendmail-bin --reinstall
 
  Does that give any errors ?

Just those I mentioned that only required moving a few lines in sendmail.mc

However I'm still seeing something in the smtp conversation output about
not being able to write somewhere... The message is too damn cryptic be
very helpful. (see below).

If you are running version 4.14.4-5.. maybe you could post the perms on:

/var/spool/clientmqueue (Its a directory that should be created during
install but is not).  And:
/var/lib/sendmail (There should be another directory here named
/var/lib/sendmail/host_status but it didn't get created during install either)

----   ---=---   -   
Tail of smtp conversation:

250 2.0.0 Verbose mode
 MAIL From:rea...@rdr.local.lan SIZE=289 AUTH=rea...@rdr.local.lan
250 2.1.0 rea...@rdr.local.lan... Sender ok
 RCPT To:rea...@newsguy.com
 DATA
250 2.1.5 rea...@newsguy.com... Recipient ok
354 Enter mail, end with . on a line by itself
 .
421 4.3.0 collect: Cannot write ./dfs4IGodqZ004450 (bfcommit, uid=0, gid=122): 
No such file or directory
 QUIT
rea...@newsguy.com... Deferred: 421 4.3.0 collect: Cannot write 
./dfs4IGodqZ004450 (bfcommit, uid=0, gid=122): No such file or directory
Closing connection to [127.0.0.1]
----   ---=---   -   

I can't figure out where the damn thing is trying to write, perhaps the
root uid should be something else?

----   ---=---   -  

perms on /var/spool stuff:

total 32
drwxr-xr-x 2 rootroot4096 May 16 16:48 anacron

This one I created by hand and took the perms from the similar named
directory mqueue-client which did exist

*** drwxrws--- 2 smmsp   smmsp   4096 May 17 14:41 clientmqueue

drwxr-xr-x 5 rootroot4096 May 16 16:20 cron
drwxr-x--- 5 Debian-exim Debian-exim 4096 May 16 16:35 exim4
drwxr-xr-x 3 rootroot4096 May 16 16:18 libreoffice
lrwxrwxrwx 1 rootroot   7 May 16 15:47 mail - ../mail
drwxrws--- 2 smmta   smmsp   4096 Feb 15 19:32 mqueue
drwxrws--- 2 smmsp   smmsp   4096 May 18 12:50 mqueue-client
drwx-- 2 rootroot4096 Mar 28 08:10 rsyslog

----   ---=---   -  

ls -ld /var/lib/sendmail

I changed this to what you see, from:
  drwxr-s--x

  drwxrws--x 3 smmta smmsp 4096 May 18 12:49 /var/lib/sendmail

ls -l /var/lib/sendmail/
-rw-rw 1 root smmsp0 May 17 21:55 dead.letter
drwxrws--- 2 root smmsp 4096 May 18 12:49 host_status





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/871tvr3tj5@newsguy.com



Re: latest sendmail on testing

2014-05-18 Thread Filip
On Sun, 18 May 2014 13:07:10 -0400
Harry Putnam rea...@newsguy.com wrote:

 Filip fi...@fbvnet.be writes:
 
  On Sat, 17 May 2014 17:08:10 -0400
  Harry Putnam rea...@newsguy.com wrote:
 
  Filip fi...@fbvnet.be writes:
  
  [...]
  
   I would have thought the install of a pkg would also create any
   needed directories for the pkg to operate.
   
   Is it normal for user to create these things?
  
  
   No, it's not normal. The post-install scripts should create a
   working initial configuration where it at least starts up.
  
   Try reinstalling with the --reinstall option.
  
   apt-get install sendmail --reinstall
   apt-get install sendmail-base --reinstall
   apt-get install sendmail-bin --reinstall
  
   Does that give any errors ?
 
 Just those I mentioned that only required moving a few lines in
 sendmail.mc
 
 However I'm still seeing something in the smtp conversation output
 about not being able to write somewhere... The message is too damn
 cryptic be very helpful. (see below).
 
 If you are running version 4.14.4-5.. maybe you could post the perms
 on:
 
 /var/spool/clientmqueue (Its a directory that should be created during
 install but is not).  And:
 /var/lib/sendmail (There should be another directory here named
 /var/lib/sendmail/host_status but it didn't get created during
 install either)
 
 ----   ---=---   -   
 Tail of smtp conversation:
 
 250 2.0.0 Verbose mode
  MAIL From:rea...@rdr.local.lan SIZE=289
  AUTH=rea...@rdr.local.lan
 250 2.1.0 rea...@rdr.local.lan... Sender ok
  RCPT To:rea...@newsguy.com
  DATA
 250 2.1.5 rea...@newsguy.com... Recipient ok
 354 Enter mail, end with . on a line by itself
  .
 421 4.3.0 collect: Cannot write ./dfs4IGodqZ004450 (bfcommit, uid=0,
 gid=122): No such file or directory
  QUIT
 rea...@newsguy.com... Deferred: 421 4.3.0 collect: Cannot
 write ./dfs4IGodqZ004450 (bfcommit, uid=0, gid=122): No such file or
 directory Closing connection to [127.0.0.1] ---
 -   ---=---   -   
 
 I can't figure out where the damn thing is trying to write, perhaps
 the root uid should be something else?
 
 ----   ---=---   -  
 
 perms on /var/spool stuff:
 
 total 32
 drwxr-xr-x 2 rootroot4096 May 16 16:48 anacron
 
 This one I created by hand and took the perms from the similar named
 directory mqueue-client which did exist
 
 *** drwxrws--- 2 smmsp   smmsp   4096 May 17 14:41
 clientmqueue
 
 drwxr-xr-x 5 rootroot4096 May 16 16:20 cron
 drwxr-x--- 5 Debian-exim Debian-exim 4096 May 16 16:35 exim4
 drwxr-xr-x 3 rootroot4096 May 16 16:18 libreoffice
 lrwxrwxrwx 1 rootroot   7 May 16 15:47 mail - ../mail
 drwxrws--- 2 smmta   smmsp   4096 Feb 15 19:32 mqueue
 drwxrws--- 2 smmsp   smmsp   4096 May 18 12:50 mqueue-client
 drwx-- 2 rootroot4096 Mar 28 08:10 rsyslog
 
 ----   ---=---   -  
 
 ls -ld /var/lib/sendmail
 
 I changed this to what you see, from:
   drwxr-s--x
 
   drwxrws--x 3 smmta smmsp 4096 May 18 12:49 /var/lib/sendmail
 
 ls -l /var/lib/sendmail/
 -rw-rw 1 root smmsp0 May 17 21:55 dead.letter
 drwxrws--- 2 root smmsp 4096 May 18 12:49 host_status
 
 
 
 
 

I have this:

drwxr-s--- 2 smmta smmsp 4096 May 18 19:46 /var/spool/mqueue
drwxrws--- 2 smmsp smmsp 4096 Feb 16 01:04 /var/spool/mqueue-client
drwxrwsrwt 2 root mail 4096 May 18 19:46 /var/mail
drwxr-s--x 2 smmta smmsp 4096 May 18 19:40 /var/lib/sendmail

mqueue-client instead of clientmqueue.

# dpkg -L sendmail-bin|grep client
/var/spool/mqueue-client

sendmail package version 8.14.4-5



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140518200525.5648e...@orac.fil



Re: latest sendmail on testing

2014-05-18 Thread Harry Putnam
Filip fi...@fbvnet.be writes:

[...]

 If you are running version 4.14.4-5.. maybe you could post the perms
 on:
 
 /var/spool/clientmqueue (Its a directory that should be created during
 install but is not).  And:
 /var/lib/sendmail (There should be another directory here named
 /var/lib/sendmail/host_status but it didn't get created during
 install either)
 
 ----   ---=---   -   
 Tail of smtp conversation:
 
 250 2.0.0 Verbose mode
  MAIL From:rea...@rdr.local.lan SIZE=289
  AUTH=rea...@rdr.local.lan
 250 2.1.0 rea...@rdr.local.lan... Sender ok
  RCPT To:rea...@newsguy.com
  DATA
 250 2.1.5 rea...@newsguy.com... Recipient ok
 354 Enter mail, end with . on a line by itself
  .
 421 4.3.0 collect: Cannot write ./dfs4IGodqZ004450 (bfcommit, uid=0,
 gid=122): No such file or directory
  QUIT
 rea...@newsguy.com... Deferred: 421 4.3.0 collect: Cannot
 write ./dfs4IGodqZ004450 (bfcommit, uid=0, gid=122): No such file or
 directory Closing connection to [127.0.0.1] ---
 -   ---=---   -   
 
 I can't figure out where the damn thing is trying to write, perhaps
 the root uid should be something else?
 
 ----   ---=---   -  
 
 perms on /var/spool stuff:
 
 total 32
 drwxr-xr-x 2 rootroot4096 May 16 16:48 anacron
 
 This one I created by hand and took the perms from the similar named
 directory mqueue-client which did exist
 
 *** drwxrws--- 2 smmsp   smmsp   4096 May 17 14:41
 clientmqueue
 
 drwxr-xr-x 5 rootroot4096 May 16 16:20 cron
 drwxr-x--- 5 Debian-exim Debian-exim 4096 May 16 16:35 exim4
 drwxr-xr-x 3 rootroot4096 May 16 16:18 libreoffice
 lrwxrwxrwx 1 rootroot   7 May 16 15:47 mail - ../mail
 drwxrws--- 2 smmta   smmsp   4096 Feb 15 19:32 mqueue
 drwxrws--- 2 smmsp   smmsp   4096 May 18 12:50 mqueue-client
 drwx-- 2 rootroot4096 Mar 28 08:10 rsyslog
 
 ----   ---=---   -  
 
 ls -ld /var/lib/sendmail
 
 I changed this to what you see, from:
   drwxr-s--x
 
   drwxrws--x 3 smmta smmsp 4096 May 18 12:49 /var/lib/sendmail
 
 ls -l /var/lib/sendmail/
 -rw-rw 1 root smmsp0 May 17 21:55 dead.letter
 drwxrws--- 2 root smmsp 4096 May 18 12:49 host_status


 I have this:

 drwxr-s--- 2 smmta smmsp 4096 May 18 19:46 /var/spool/mqueue
 drwxrws--- 2 smmsp smmsp 4096 Feb 16 01:04 /var/spool/mqueue-client
 drwxrwsrwt 2 root mail 4096 May 18 19:46 /var/mail
 drwxr-s--x 2 smmta smmsp 4096 May 18 19:40 /var/lib/sendmail

 mqueue-client instead of clientmqueue.

 # dpkg -L sendmail-bin|grep client
 /var/spool/mqueue-client

 sendmail package version 8.14.4-5

If you recall, in the OP that started this thread I posted the output of
my first attempt at running sendmail:

   # service sendmail start

   [] Starting Mail Transport Agent (MTA): sendmailcan not
   chdir(/var/spool/clientmqueue/): No such file or directory

   Warning: Cannot use HostStatusDirectory =
   /var/lib/sendmail/host_status: No such file or directory

I created /var/spool/clientmqueue because of that first part
That is where my interest in /var/spool/clientmqueue began.

Why is sendmail attempting to chdir to a directory that is not part of
its working setup?

Why is sendmail trying to use a non-existent directory in the second bit
above? 

What are those errors about?

Further, could you make any sense of the smtp output I posted:

,
|  421 4.3.0 collect: Cannot write ./dfs4IGodqZ004450 (bfcommit, uid=0,
|  gid=122): No such file or directory
|   QUIT
|  rea...@newsguy.com... Deferred: 421 4.3.0 collect: Cannot
|  write ./dfs4IGodqZ004450 (bfcommit, uid=0, gid=122): No such file or
|  directory Closing connection to [127.0.0.1]
`

Where is sendmail trying to write?  Why is sendmail trying to write to
something that does not exist?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87wqdi3enj@newsguy.com



latest sendmail on testing

2014-05-17 Thread Harry Putnam
Recent install of jessie as vbox guest vm on win 7 64bit

Preferring sendmail to exim I installed the testing package for sendmail
and of course that uninstalled a few things, including exim.

So, my first run at sendmail , just starting the service

   # service sendmail start

   [] Starting Mail Transport Agent (MTA): sendmailcan not
   chdir(/var/spool/clientmqueue/): No such file or directory

   Warning: Cannot use HostStatusDirectory =
   /var/lib/sendmail/host_status: No such file or directory

I would have thought the install of a pkg would also create any needed
directories for the pkg to operate.

Is it normal for user to create these things?





-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87bnuw5qxv@newsguy.com



Re: latest sendmail on testing

2014-05-17 Thread Filip
On Sat, 17 May 2014 12:07:56 -0400
Harry Putnam rea...@newsguy.com wrote:

 Recent install of jessie as vbox guest vm on win 7 64bit
 
 Preferring sendmail to exim I installed the testing package for
 sendmail and of course that uninstalled a few things, including exim.
 
 So, my first run at sendmail , just starting the service
 
# service sendmail start
 
[] Starting Mail Transport Agent (MTA): sendmailcan not
chdir(/var/spool/clientmqueue/): No such file or directory
 
Warning: Cannot use HostStatusDirectory =
/var/lib/sendmail/host_status: No such file or directory
 
 I would have thought the install of a pkg would also create any needed
 directories for the pkg to operate.
 
 Is it normal for user to create these things?
 
 
 
 
 

No, it's not normal. The post-install scripts should create a
working initial configuration where it at least starts up.

Try reinstalling with the --reinstall option.

apt-get install sendmail --reinstall
apt-get install sendmail-base --reinstall
apt-get install sendmail-bin --reinstall

Does that give any errors ?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140517212752.236ac...@orac.fil



Re: latest sendmail on testing

2014-05-17 Thread Harry Putnam
Filip fi...@fbvnet.be writes:

 On Sat, 17 May 2014 12:07:56 -0400
 Harry Putnam rea...@newsguy.com wrote:

 Recent install of jessie as vbox guest vm on win 7 64bit
 
 Preferring sendmail to exim I installed the testing package for
 sendmail and of course that uninstalled a few things, including exim.
 
 So, my first run at sendmail , just starting the service
 
# service sendmail start
 
[] Starting Mail Transport Agent (MTA): sendmailcan not
chdir(/var/spool/clientmqueue/): No such file or directory
 
Warning: Cannot use HostStatusDirectory =
/var/lib/sendmail/host_status: No such file or directory
 
 I would have thought the install of a pkg would also create any needed
 directories for the pkg to operate.
 
 Is it normal for user to create these things?
 
 
 
 
 

 No, it's not normal. The post-install scripts should create a
 working initial configuration where it at least starts up.

 Try reinstalling with the --reinstall option.

 apt-get install sendmail --reinstall
 apt-get install sendmail-base --reinstall
 apt-get install sendmail-bin --reinstall

 Does that give any errors ?

Sounds like a plan... thanks.

One problem... I've diddled around with the files inside of /etc/mail a
fair bit and even though I think I keep original copies of anything I
changed.  It would be easier if I just rm -rf /etc/mail.

So wondering if on a brand new install from the lxde iso, if there would
already be a an /etc/mail If so I'll have to pick thru and try my
best to get it back to original condition.

I'd hate for some awkward ill-advised thing I've done to make the
even a reinstall a non-starter.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8738g85eli@newsguy.com



Re: latest sendmail on testing

2014-05-17 Thread Harry Putnam
Harry Putnam rea...@newsguy.com writes:

 No, it's not normal. The post-install scripts should create a
 working initial configuration where it at least starts up.

 Try reinstalling with the --reinstall option.

 apt-get install sendmail --reinstall
 apt-get install sendmail-base --reinstall
 apt-get install sendmail-bin --reinstall

 Does that give any errors ?

 Sounds like a plan... thanks.

 One problem... I've diddled around with the files inside of /etc/mail a
 fair bit and even though I think I keep original copies of anything I
 changed.  It would be easier if I just rm -rf /etc/mail.

 So wondering if on a brand new install from the lxde iso, if there would
 already be a an /etc/mail If so I'll have to pick thru and try my
 best to get it back to original condition.

 I'd hate for some awkward ill-advised thing I've done to make the
 even a reinstall a non-starter.

Sorry... just a little sniveling... you can scrap that post.

I've done a little research with dpkg -L to find out what all sendmail
pkgs install.

Once I've done what you suggested... I'll try back if there is still a problem.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87tx8o3znk@newsguy.com



Re: latest sendmail on testing

2014-05-17 Thread Harry Putnam
Filip fi...@fbvnet.be writes:

[...]

 I would have thought the install of a pkg would also create any needed
 directories for the pkg to operate.
 
 Is it normal for user to create these things?


 No, it's not normal. The post-install scripts should create a
 working initial configuration where it at least starts up.

 Try reinstalling with the --reinstall option.

 apt-get install sendmail --reinstall
 apt-get install sendmail-base --reinstall
 apt-get install sendmail-bin --reinstall

 Does that give any errors ?

It gives the same errors I saw when I first installed sendmail.

I didn't even mention them in my OP since it was easy enough to fix
(more below on that)

These are not the errors I posted about.

Its not the actual installation but the part when `make' is run in
/etc/mail I think.

But have included the full output at the end since I don't know enough
to know what might help:

----   ---=---   -   

When I saw these comments below the first time, I just moved the lines
indicated in sendmail.mc and reran `make'.  

But those other errors, the ones I posted about concerning missing
directories in /etc/lib/sendamil and /var/spool/ do not come up until
you actually start trying to use sendmail.

Attempting to make things easy for someone to help... I'm putting here
what I think are the only actual errors and fuller output below:

[...]
Creating /etc/mail/sendmail.cf...
*** ERROR: FEATURE() should be before MAILER()
*** MAILER(`local') must appear after FEATURE(`always_add_domain')*** ERROR: 
FEATURE() should be before MAILER()
*** MAILER(`local') must appear after FEATURE(`allmasquerade')*** ERROR: 
FEATURE() should be before MAILER()
[...]

----   ---=---   -   
Full ouput:

Preparing to unpack .../sendmail-bin_8.14.4-5_i386.deb ...
Unpacking sendmail-bin (8.14.4-5) over (8.14.4-5) ...
Processing triggers for man-db (2.6.7.1-1) ...
Setting up sendmail-bin (8.14.4-5) ...
update-alternatives: warning: forcing reinstallation of alternative 
/usr/lib/sm.bin/sendmail because link group sendmail-mta is broken
update-alternatives: warning: forcing reinstallation of alternative 
/usr/lib/sm.bin/sendmail because link group sendmail-msp is broken
Saving old /etc/mail/sendmail.cf as /etc/mail/sendmail.cf.old ...
[ ok ] Stopping Mail Transport Agent (MTA): sendmail.
Updating sendmail environment ...
Reading configuration from /etc/mail/sendmail.conf.
Validating configuration.
Writing configuration to /etc/mail/sendmail.conf.
Writing /etc/cron.d/sendmail.
Reading configuration from /etc/mail/sendmail.conf.
Validating configuration.
Writing configuration to /etc/mail/sendmail.conf.
Writing /etc/cron.d/sendmail.
Could not open /etc/mail/databases(No such file or directory), creating it.
Reading configuration from /etc/mail/sendmail.conf.
Validating configuration.
Creating /etc/mail/databases...

Checking filesystem, this may take some time - it will not hang!
  ...   Done.
 
Checking for installed MDAs...
sasl2-bin not installed, not configuring sendmail support.

To enable sendmail SASL2 support at a later date, invoke 
/usr/share/sendmail/update_auth

 
Creating/Updating SSL(for TLS) information
Creating /etc/mail/tls/starttls.m4...
You already have sendmail certificates
 

*** *** *** WARNING *** WARNING *** WARNING *** WARNING *** *** ***

Everything you need to support STARTTLS (encrypted mail transmission
and user authentication via certificates) is installed and configured
but is *NOT* being used.

To enable sendmail to use STARTTLS, you need to:
1) Add this line to /etc/mail/sendmail.mc and optionally
   to /etc/mail/submit.mc:
  include(`/etc/mail/tls/starttls.m4')dnl
2) Run sendmailconfig
3) Restart sendmail

Checking {sendmail,submit}.mc and related databases...
Reading configuration from /etc/mail/sendmail.conf.
Validating configuration.
Creating /etc/mail/databases...
Reading configuration from /etc/mail/sendmail.conf.
Validating configuration.
Creating /etc/mail/databases...
Reading configuration from /etc/mail/sendmail.conf.
Validating configuration.
Creating /etc/mail/Makefile...
Reading configuration from /etc/mail/sendmail.conf.
Validating configuration.
Writing configuration to /etc/mail/sendmail.conf.
Writing /etc/cron.d/sendmail.
Disabling HOST statistics file(/var/lib/sendmail/host_status).
Creating /etc/mail/sendmail.cf...
*** ERROR: FEATURE() should be before MAILER()
*** MAILER(`local') must appear after FEATURE(`always_add_domain')*** ERROR: 
FEATURE() should be before MAILER()
*** MAILER(`local') must appear after FEATURE(`allmasquerade')*** ERROR: 
FEATURE() should be before MAILER()
 
Creating /etc/mail/submit.cf...
Informational: confCR_FILE file empty: /etc/mail/relay-domains
Informational: confCT_FILE file empty: /etc/mail/trusted-users
Updating /etc/mail/access...
Updating /etc/mail/aliases...
/etc/mail/aliases: 13 aliases, longest 10 bytes, 144 bytes total
 
Warning: These 

Re: latest sendmail on testing

2014-05-17 Thread Filip
On Sat, 17 May 2014 17:08:10 -0400
Harry Putnam rea...@newsguy.com wrote:

 Filip fi...@fbvnet.be writes:
 
 [...]
 
  I would have thought the install of a pkg would also create any
  needed directories for the pkg to operate.
  
  Is it normal for user to create these things?
 
 
  No, it's not normal. The post-install scripts should create a
  working initial configuration where it at least starts up.
 
  Try reinstalling with the --reinstall option.
 
  apt-get install sendmail --reinstall
  apt-get install sendmail-base --reinstall
  apt-get install sendmail-bin --reinstall
 
  Does that give any errors ?
 
 It gives the same errors I saw when I first installed sendmail.
 
 I didn't even mention them in my OP since it was easy enough to fix
 (more below on that)
 
 These are not the errors I posted about.
 
 Its not the actual installation but the part when `make' is run in
 /etc/mail I think.
 
 But have included the full output at the end since I don't know enough
 to know what might help:
 
 ----   ---=---   -   
 
 When I saw these comments below the first time, I just moved the lines
 indicated in sendmail.mc and reran `make'.  
 
 But those other errors, the ones I posted about concerning missing
 directories in /etc/lib/sendamil and /var/spool/ do not come up until
 you actually start trying to use sendmail.
 
 Attempting to make things easy for someone to help... I'm putting here
 what I think are the only actual errors and fuller output below:
 
 [...]
 Creating /etc/mail/sendmail.cf...
 *** ERROR: FEATURE() should be before MAILER()
 *** MAILER(`local') must appear after FEATURE(`always_add_domain')***
 ERROR: FEATURE() should be before MAILER() *** MAILER(`local') must
 appear after FEATURE(`allmasquerade')*** ERROR: FEATURE() should be
 before MAILER() [...]
 
 ----   ---=---   -   
 Full ouput:
 
 Preparing to unpack .../sendmail-bin_8.14.4-5_i386.deb ...
 Unpacking sendmail-bin (8.14.4-5) over (8.14.4-5) ...
 Processing triggers for man-db (2.6.7.1-1) ...
 Setting up sendmail-bin (8.14.4-5) ...
 update-alternatives: warning: forcing reinstallation of
 alternative /usr/lib/sm.bin/sendmail because link group sendmail-mta
 is broken update-alternatives: warning: forcing reinstallation of
 alternative /usr/lib/sm.bin/sendmail because link group sendmail-msp
 is broken Saving old /etc/mail/sendmail.cf
 as /etc/mail/sendmail.cf.old ... [ ok ] Stopping Mail Transport Agent
 (MTA): sendmail. Updating sendmail environment ... Reading
 configuration from /etc/mail/sendmail.conf. Validating configuration.
 Writing configuration to /etc/mail/sendmail.conf.
 Writing /etc/cron.d/sendmail. Reading configuration
 from /etc/mail/sendmail.conf. Validating configuration.
 Writing configuration to /etc/mail/sendmail.conf.
 Writing /etc/cron.d/sendmail.
 Could not open /etc/mail/databases(No such file or directory),
 creating it. Reading configuration from /etc/mail/sendmail.conf.
 Validating configuration.
 Creating /etc/mail/databases...
 
 Checking filesystem, this may take some time - it will not hang!
   ...   Done.
  
 Checking for installed MDAs...
 sasl2-bin not installed, not configuring sendmail support.
 
 To enable sendmail SASL2 support at a later date, invoke
 /usr/share/sendmail/update_auth
 
  
 Creating/Updating SSL(for TLS) information
 Creating /etc/mail/tls/starttls.m4...
 You already have sendmail certificates
  
 
 *** *** *** WARNING *** WARNING *** WARNING *** WARNING *** *** ***
 
 Everything you need to support STARTTLS (encrypted mail transmission
 and user authentication via certificates) is installed and configured
 but is *NOT* being used.
 
 To enable sendmail to use STARTTLS, you need to:
 1) Add this line to /etc/mail/sendmail.mc and optionally
to /etc/mail/submit.mc:
   include(`/etc/mail/tls/starttls.m4')dnl
 2) Run sendmailconfig
 3) Restart sendmail
 
 Checking {sendmail,submit}.mc and related databases...
 Reading configuration from /etc/mail/sendmail.conf.
 Validating configuration.
 Creating /etc/mail/databases...
 Reading configuration from /etc/mail/sendmail.conf.
 Validating configuration.
 Creating /etc/mail/databases...
 Reading configuration from /etc/mail/sendmail.conf.
 Validating configuration.
 Creating /etc/mail/Makefile...
 Reading configuration from /etc/mail/sendmail.conf.
 Validating configuration.
 Writing configuration to /etc/mail/sendmail.conf.
 Writing /etc/cron.d/sendmail.
 Disabling HOST statistics file(/var/lib/sendmail/host_status).
 Creating /etc/mail/sendmail.cf...
 *** ERROR: FEATURE() should be before MAILER()
 *** MAILER(`local') must appear after FEATURE(`always_add_domain')***
 ERROR: FEATURE() should be before MAILER() *** MAILER(`local') must
 appear after FEATURE(`allmasquerade')*** ERROR: FEATURE() should be
 before MAILER() Creating /etc/mail/submit.cf...
 Informational: confCR_FILE file empty: /etc/mail/relay-domains
 Informational: