subject:"Postfix woes"

Re: Postfix woes

2007-10-20 Thread Gerard

On October 19, 2007 at 05:44PM Rem P Roberti wrote:

[ ... ]

 This is a follow-up.  My friend arrived back home and I explained the
 problems that I was having.  He said, simple, remark out
 postfix_enable=YES in your rc.conf.  I did.  Problem solved.  Now I
 have neither postfix_enable, or sendmail_enable in my rc.conf, and
 everything boots without a hitch.  This, of course, flies in the face
 of everything that I have heard or read about configuring this program.
 When I asked what was starting the program if those entries were no
 longer operating he said the shell script contained in rc.d.  
 
 I need to give this a rest.

1) Did you install Postfix from ports?

2) Did you read the information available at:

http://www.csua.berkeley.edu/~ranga/notes/freebsd_postfix.html
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mail-changingmta.html

3) Are you now implying that postfix starts even though you have it disabled in
the /etc/rc.conf file?

You should not have had Sendmail and postfix running at the same time anyway.

Besides you /etc/rc.conf file, do you also have a /etc/rc.conf.local file? If
so, what does it contain. I am assuming that you never touched the
/etc/defaults/rc.conf file. If you did alter it, that was a mistake.

Postfix is not simply starting on its own. Somewhere, somehow, something is
starting it.


-- 
Gerard
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Postfix woes

2007-10-19 Thread Paul Schmehl

--On Thursday, October 18, 2007 22:46:51 -0700 Rem P Roberti 
[EMAIL PROTECTED] wrote:



I did what you all requested and submitted my Postfix problem to the
Postfix list.  The resident guru went over my maillog and sent back his
analysis which, in short, states that the problem has nothing to do with
Postfix, and that I should seek help here to get to the bottom of it
all.  That reply is listed below.   This is a rather strange business.

OK.  FIrst of all, don't top post.  It makes it very hard to follow a 
conversation.


When you install FreeBSD, you are the master of your own domain.  That 
means you are completely responsible for everything running on your box.


When you install Postfix, it installs a startup script in 
/usr/local/etc/rc.d.  In order to start postfix, you must either add 
postfix_enable=YES to /etc/rc.conf or start postfix manually.  If you 
want postfix to start on reboot automatically, you *must* use the entry in 
/etc/rc.conf.


There are no cron jobs or scheduled tasks installed to restart, reload, 
stop or do anything else to postfix.  This means that you, or someone who 
has access to your box, has set this up.  If you don't recall doing 
anything, then you're going to have to start troubleshooting.


Places to look:

1) su to root and type crontab -l to see if there's a cron job designed 
to manipulate postfix, either directly or through a script.  If there is, 
eliminate it.  It's not needed.


2) Look in /etc/periodic to see if there's anything in there (although 
that's highly unlikely).


3) Examine the postfix startup script to  see if someone has altered it in 
some way so that it includes a timer that starts and restarts Postfix


3) Write a script that monitors processes and can detect when something is 
launched at the same time frame that postfix is going up and down


4) Get help from someone knowledgeable who has access to your box

5) Did you install a program (like sysutils/monitord) that checks for 
running processes and attempts to restart them if they're not running?


6) Is there anything in root's mail that would tip you off to the cause of 
the problem?


7) Run postfix in debug mode.  Maybe that will help isolate the cause.

--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Postfix woes

2007-10-19 Thread Per olof Ljungmark


snip

This insanity has nothing to do with Postfix, if you can't find the
cron jobs, start scripts, management agents, ... that are doing this,
go back the FreeBSD list and ask for help to find them.

  

Aloha,

I run Postfix/Dovecot under FreeBSD 7* since Jan 2007.
I had trouble with postfix by itself on FreeBSD when I first set up a 
mail server. I then had one of the FreeBSD gurus on the list suggest I 
run Dovecot to make postfix behave nicely on FreeBSD. That solved my 
problems.
If you havent tried this FreeBSD Postfix/Dovecot based install it may 
work for you.
Also if you are running Dovecot remember just start it in /etc/rc.conf 
you dont need to start postfix in there as well.

If you are just running Postfix you have to start it in /etc/rc.conf


I strongly suggests the OP sorts his Postfix problems first, then move 
on. Installing more software that you are not experienced with woulod 
hardly help. The previous suggestions on how to proceed would be a good 
start instead.


--per
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Postfix woes

2007-10-19 Thread Rem P Roberti

On 2007.10.19 09:35:48 +, Paul Schmehl wrote:
 --On Thursday, October 18, 2007 22:46:51 -0700 Rem P Roberti 
 [EMAIL PROTECTED] wrote:
 
 I did what you all requested and submitted my Postfix problem to the
 Postfix list.  The resident guru went over my maillog and sent back his
 analysis which, in short, states that the problem has nothing to do with
 Postfix, and that I should seek help here to get to the bottom of it
 all.  That reply is listed below.   This is a rather strange business.
 
 OK.  FIrst of all, don't top post.  It makes it very hard to follow a 
 conversation.
 
 When you install FreeBSD, you are the master of your own domain.  That 
 means you are completely responsible for everything running on your box.
 
 When you install Postfix, it installs a startup script in 
 /usr/local/etc/rc.d.  In order to start postfix, you must either add 
 postfix_enable=YES to /etc/rc.conf or start postfix manually.  If you 
 want postfix to start on reboot automatically, you *must* use the entry in 
 /etc/rc.conf.
 
 There are no cron jobs or scheduled tasks installed to restart, reload, 
 stop or do anything else to postfix.  This means that you, or someone who 
 has access to your box, has set this up.  If you don't recall doing 
 anything, then you're going to have to start troubleshooting.
 
 Places to look:
 
 1) su to root and type crontab -l to see if there's a cron job designed 
 to manipulate postfix, either directly or through a script.  If there is, 
 eliminate it.  It's not needed.
 
 2) Look in /etc/periodic to see if there's anything in there (although 
 that's highly unlikely).
 
 3) Examine the postfix startup script to  see if someone has altered it in 
 some way so that it includes a timer that starts and restarts Postfix
 
 3) Write a script that monitors processes and can detect when something is 
 launched at the same time frame that postfix is going up and down
 
 4) Get help from someone knowledgeable who has access to your box
 
 5) Did you install a program (like sysutils/monitord) that checks for 
 running processes and attempts to restart them if they're not running?
 
 6) Is there anything in root's mail that would tip you off to the cause of 
 the problem?
 
 7) Run postfix in debug mode.  Maybe that will help isolate the cause.


This is a follow-up.  My friend arrived back home and I explained the
problems that I was having.  He said, simple, remark out
postfix_enable=YES in your rc.conf.  I did.  Problem solved.  Now I
have neither postfix_enable, or sendmail_enable in my rc.conf, and
everything boots without a hitch.  This, of course, flies in the face
of everything that I have heard or read about configuring this program.
When I asked what was starting the program if those entries were no
longer operating he said the shell script contained in rc.d.  

I need to give this a rest.

Rem
 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Postfix woes

2007-10-19 Thread NetOpsCenter


Rem P Roberti wrote:

I did what you all requested and submitted my Postfix problem to the
Postfix list.  The resident guru went over my maillog and sent back his
analysis which, in short, states that the problem has nothing to do with
Postfix, and that I should seek help here to get to the bottom of it
all.  That reply is listed below.   This is a rather strange business.

Rem





From: Rem P Roberti [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Cc: 
Bcc: 
Subject: [EMAIL PROTECTED]: Re: Boot-up weirdness]
Reply-To: 


- Forwarded message from Victor Duchovni [EMAIL PROTECTED] -

Date: Thu, 18 Oct 2007 21:44:36 -0400
From: Victor Duchovni [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Boot-up weirdness

On Thu, Oct 18, 2007 at 06:11:42PM -0700, Rem P Roberti wrote:

  

Oct 18 16:39:20 bsd postfix/postfix-script[3805]: starting the Postfix
mail system
Oct 18 16:39:20 bsd postfix/master[3806]: daemon started -- version
2.4.5, configuration /usr/local/etc/postfix
Oct 18 16:39:25 bsd postfix/postfix-script[3811]: refreshing the Postfix
mail system
Oct 18 16:39:25 bsd postfix/master[3806]: reload configuration
/usr/local/etc/postfix



Something runs postfix reload five seconds after Postfix starts. It is
not Postfix doing that, so find the start script or cron job responsible.

  

Oct 18 16:40:40 bsd postfix/postfix-script[3937]: stopping the Postfix
mail system
Oct 18 16:40:40 bsd postfix/master[3806]: terminating on signal 15



Something runs postfix stop 85 seconds after that, it is not Postfix
doing that, so find the start script or cron job responsible.

  

Oct 18 16:40:40 bsd postfix/postfix-script[3958]: fatal: the Postfix
mail system is not running



The code in question wants to make doubly sure that Postfix is down,
which it is.

  

Oct 18 16:42:26 bsd postfix/postfix-script[894]: starting the Postfix
mail system
Oct 18 16:42:26 bsd postfix/master[895]: daemon started -- version
2.4.5, configuration /usr/local/etc/postfix



Postfix is restarted by something on your system 106 seconds later.

  

from=[EMAIL PROTECTED], size=701, nrcpt=1 (queue active)
Oct 18 16:42:28 bsd postfix/postfix-script[943]: fatal: the Postfix mail
system is already running
Oct 18 16:42:29 bsd postfix/postfix-script[983]: fatal: the Postfix mail
system is already running



Something is trying to start Postfix again. I am guessing you have two
Postfix start scripts fighting each other...

  

Oct 18 17:38:44 bsd postfix/postmap[1555]: fatal: open transport.db:
Permission denied



An hour or so later, something is trying to run postmap or postmap
-q, it is not Postfix doing that. Find the cron job or start script
in question.

  

Oct 18 17:39:15 bsd postfix/postfix-script[1559]: stopping the Postfix
mail system
Oct 18 17:39:15 bsd postfix/master[895]: terminating on signal 15
Oct 18 17:39:21 bsd postfix/postfix-script[1609]: starting the Postfix
mail system
Oct 18 17:39:21 bsd postfix/master[1610]: daemon started -- version
2.4.5, configuration /usr/local/etc/postfix



Postfix is restarted.

  

Oct 18 17:39:27 bsd postfix/postfix-script[1615]: refreshing the Postfix
mail system



And reloaded for good measure.

  

/usr/local/etc/postfix
Oct 18 17:41:23 bsd postfix/postfix-script[1768]: stopping the Postfix
mail system
Oct 18 17:41:23 bsd postfix/master[1610]: terminating on signal 15
Oct 18 17:41:23 bsd postfix/postfix-script[1789]: fatal: the Postfix
mail system is not running
Oct 18 17:42:52 bsd postfix/postfix-script[894]: starting the Postfix
mail system
Oct 18 17:42:52 bsd postfix/master[895]: daemon started -- version
2.4.5, configuration /usr/local/etc/postfix



This insanity has nothing to do with Postfix, if you can't find the
cron jobs, start scripts, management agents, ... that are doing this,
go back the FreeBSD list and ask for help to find them.

  

Aloha,

I run Postfix/Dovecot under FreeBSD 7* since Jan 2007.
I had trouble with postfix by itself on FreeBSD when I first set up a 
mail server. I then had one of the FreeBSD gurus on the list suggest I 
run Dovecot to make postfix behave nicely on FreeBSD. That solved my 
problems.
If you havent tried this FreeBSD Postfix/Dovecot based install it may 
work for you.
Also if you are running Dovecot remember just start it in /etc/rc.conf 
you dont need to start postfix in there as well.

If you are just running Postfix you have to start it in /etc/rc.conf



~Al Plant - Honolulu, Hawaii -  Phone:  808-284-2740
 + http://hawaiidakine.com + http://freebsdinfo.org + [EMAIL PROTECTED] +
 + http://internetohana.org   - Supporting - FreeBSD 6.* - 7.* +
All that's really worth doing is what we do for others.- Lewis Carrol


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Postfix woes

2007-10-19 Thread Gerard

On October 19, 2007 at 01:46AM Rem P Roberti wrote:

[ ... ]

 This insanity has nothing to do with Postfix, if you can't find the
 cron jobs, start scripts, management agents, ... that are doing this,
 go back the FreeBSD list and ask for help to find them.

Victor would know. I suggest that you paste the output of all your CRON jobs,
and perhaps the /etc/rc.conf' file so we can review them. You might also try,
as root, issuing this command: 'atq'. See if anything is listed.

By the way, have you modified any of the startup scripts; i.e., files in
'/usr/local/etc/rc.d'?


-- 
Gerard
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Postfix woes

2007-10-18 Thread Rem P Roberti

I did what you all requested and submitted my Postfix problem to the
Postfix list.  The resident guru went over my maillog and sent back his
analysis which, in short, states that the problem has nothing to do with
Postfix, and that I should seek help here to get to the bottom of it
all.  That reply is listed below.   This is a rather strange business.

Rem





From: Rem P Roberti [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Cc: 
Bcc: 
Subject: [EMAIL PROTECTED]: Re: Boot-up weirdness]
Reply-To: 

- Forwarded message from Victor Duchovni [EMAIL PROTECTED] -

Date: Thu, 18 Oct 2007 21:44:36 -0400
From: Victor Duchovni [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Boot-up weirdness

On Thu, Oct 18, 2007 at 06:11:42PM -0700, Rem P Roberti wrote:

 Oct 18 16:39:20 bsd postfix/postfix-script[3805]: starting the Postfix
 mail system
 Oct 18 16:39:20 bsd postfix/master[3806]: daemon started -- version
 2.4.5, configuration /usr/local/etc/postfix
 Oct 18 16:39:25 bsd postfix/postfix-script[3811]: refreshing the Postfix
 mail system
 Oct 18 16:39:25 bsd postfix/master[3806]: reload configuration
 /usr/local/etc/postfix

Something runs postfix reload five seconds after Postfix starts. It is
not Postfix doing that, so find the start script or cron job responsible.

 Oct 18 16:40:40 bsd postfix/postfix-script[3937]: stopping the Postfix
 mail system
 Oct 18 16:40:40 bsd postfix/master[3806]: terminating on signal 15

Something runs postfix stop 85 seconds after that, it is not Postfix
doing that, so find the start script or cron job responsible.

 Oct 18 16:40:40 bsd postfix/postfix-script[3958]: fatal: the Postfix
 mail system is not running

The code in question wants to make doubly sure that Postfix is down,
which it is.

 Oct 18 16:42:26 bsd postfix/postfix-script[894]: starting the Postfix
 mail system
 Oct 18 16:42:26 bsd postfix/master[895]: daemon started -- version
 2.4.5, configuration /usr/local/etc/postfix

Postfix is restarted by something on your system 106 seconds later.

 from=[EMAIL PROTECTED], size=701, nrcpt=1 (queue active)
 Oct 18 16:42:28 bsd postfix/postfix-script[943]: fatal: the Postfix mail
 system is already running
 Oct 18 16:42:29 bsd postfix/postfix-script[983]: fatal: the Postfix mail
 system is already running

Something is trying to start Postfix again. I am guessing you have two
Postfix start scripts fighting each other...

 Oct 18 17:38:44 bsd postfix/postmap[1555]: fatal: open transport.db:
 Permission denied

An hour or so later, something is trying to run postmap or postmap
-q, it is not Postfix doing that. Find the cron job or start script
in question.

 Oct 18 17:39:15 bsd postfix/postfix-script[1559]: stopping the Postfix
 mail system
 Oct 18 17:39:15 bsd postfix/master[895]: terminating on signal 15
 Oct 18 17:39:21 bsd postfix/postfix-script[1609]: starting the Postfix
 mail system
 Oct 18 17:39:21 bsd postfix/master[1610]: daemon started -- version
 2.4.5, configuration /usr/local/etc/postfix

Postfix is restarted.

 Oct 18 17:39:27 bsd postfix/postfix-script[1615]: refreshing the Postfix
 mail system

And reloaded for good measure.

 /usr/local/etc/postfix
 Oct 18 17:41:23 bsd postfix/postfix-script[1768]: stopping the Postfix
 mail system
 Oct 18 17:41:23 bsd postfix/master[1610]: terminating on signal 15
 Oct 18 17:41:23 bsd postfix/postfix-script[1789]: fatal: the Postfix
 mail system is not running
 Oct 18 17:42:52 bsd postfix/postfix-script[894]: starting the Postfix
 mail system
 Oct 18 17:42:52 bsd postfix/master[895]: daemon started -- version
 2.4.5, configuration /usr/local/etc/postfix

This insanity has nothing to do with Postfix, if you can't find the
cron jobs, start scripts, management agents, ... that are doing this,
go back the FreeBSD list and ask for help to find them.

-- 
Viktor.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: More Postfix Woes

2007-10-18 Thread Rem P Roberti

On 2007.10.18 19:09:01 +, Gerard wrote:
 On October 18, 2007 at 06:42PM Rem P Roberti wrote:
 
 
  I don't know what is going on with respect to Postfix during my boot
  process, but the program starts, and stops, starts, and stops, and this
  newbie is a little perplexed.  Fortunately, it ends up started, so I
  have access to my email, but something is obviously not right here.  I
  have provided below entries from my latest maillog.  Any help is
  appreciated...
 
 For starters, you should read the Postfix documentation. You might also try
 posting on the Postfix forum. Check out http://postfix.com for further 
 details.
 
 Now, before you go any further, the log file is telling you that your
 'transport' is out of date. You have to run 'postmap' on it and then restart
 Postfix to get it corrected. Try: 'postmap /usr/local/etc/postfix/transport'
 assuming that your transport map is named 'transport'. This will update the
 mapping.
 
 You should always supply the complete output of: postconf -n when asking
 help regarding Postfix. It saves a lot of time.
 

As per your suggestion, here is the output of postconf -n...


alias_maps = hash:/etc/aliases
body_checks = regexp:/usr/local/etc/postfix/body_checks
command_directory = /usr/local/sbin
config_directory = /usr/local/etc/postfix
daemon_directory = /usr/local/libexec/postfix
debug_peer_level = 5
default_privs = nobody
html_directory = no
luser_relay = steve-junk
mail_owner = postfix
mailq_path = /usr/local/bin/mailq
manpage_directory = /usr/local/man
mydestination = $myhostname, localhost.$mydomain, localhost
mydomain = remdog.net
myhostname = bsd.remdog.net
myorigin = $myhostname
newaliases_path = /usr/local/bin/newaliases
queue_directory = /var/spool/postfix
readme_directory = no
recipient_delimiter = -
relay_domains = $mydestination
sample_directory = /usr/local/etc/postfix
sendmail_path = /usr/local/sbin/sendmail
setgid_group = maildrop
smtp_helo_name = $mydomain
smtpd_client_restrictions = permit_mynetworks,  check_client_access
hash:/usr/local/etc/postfix/access, check_client_access
regexp:/usr/local/etc/postfix/regexp_table, reject_unknown_client
smtpd_recipient_restrictions = permit_mynetworks,
check_sender_access hash:/usr/local/etc/postfix/access,
check_recipient_access hash:/usr/local/etc/postfix/access,
reject_unauth_destination,  check_recipient_access
regexp:/usr/local/etc/postfix/regexp_table,  check_sender_access
regexp:/usr/local/etc/postfix/regexp_table, reject_unknown_client
transport_maps = hash:/usr/local/etc/postfix/transport
unknown_hostname_reject_code = 450
unknown_local_recipient_reject_code = 550
virtual_alias_maps = hash:/usr/local/etc/postfix/virtual



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: More Postfix Woes

2007-10-18 Thread Rem P Roberti

On 2007.10.18 16:05:00 +, Chuck Swiger wrote:
 On Oct 18, 2007, at 3:42 PM, Rem P Roberti wrote:
 Oct 18 03:16:21 bsd postfix/trivial-rewrite[16064]: warning: database
 /usr/local/etc/postfix/transport.db is older than source file
 /usr/local/etc/postfix/transport
 
 Fix this by doing:
 
   cd /usr/local/etc/postfix ; postmap transport
 
 [ ... ]
 Oct 18 08:03:12 bsd postfix/postfix-script[17269]: stopping the  
 Postfix mail system
 Oct 18 08:03:12 bsd postfix/master[894]: terminating on signal 15
 Oct 18 08:03:12 bsd postfix/postfix-script[17290]: fatal: the  
 Postfix mail system is not running
 
 That's bizzare.  Do you have some sort of scripted utility which is  
 trying to stop and restart Postfix via cron or some such?
 
 -- 
 -Chuck


Thanks to all.  I have run postmap transport, and the rc.conf was
exactly as per pkg-message.  As far as the starting and stopping, I'm
still clueless.  To the best of my knowledge there are no scripts which
would cause the problem, and nothing strange in cron.

Rem
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: More Postfix Woes

2007-10-18 Thread Paul Schmehl

--On Thursday, October 18, 2007 15:42:22 -0700 Rem P Roberti 
[EMAIL PROTECTED] wrote:



I don't know what is going on with respect to Postfix during my boot
process, but the program starts, and stops, starts, and stops, and this
newbie is a little perplexed.  Fortunately, it ends up started, so I
have access to my email, but something is obviously not right here.  I
have provided below entries from my latest maillog.  Any help is
appreciated...


You really should google for this stuff - or join the postfix list.


Oct 18 00:00:00 bsd newsyslog[2514]: logfile turned over
Oct 18 02:20:02 bsd postfix/pickup[2799]: 9EBD01D119: uid=0 from=root
Oct 18 02:20:02 bsd postfix/trivial-rewrite[3032]: warning: database
/usr/local/etc/postfix/transport.db is older than source file
/usr/local/etc/postfix/transport


Read the install docs regarding postmap or man (1) postmap

You need to run postmap to update the transport database to match the 
transport source file.  Without looking at your configuration (run postconf 
-n), it's hard to say, but it's probably a hash db.


--
Paul Schmehl ([EMAIL PROTECTED])
Senior Information Security Analyst
The University of Texas at Dallas
http://www.utdallas.edu/ir/security/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: More Postfix Woes

2007-10-18 Thread Duane Hill

On Thu, 18 Oct 2007 15:42:22 -0700
Rem P Roberti [EMAIL PROTECTED] confabulated:

 I don't know what is going on with respect to Postfix during my boot
 process, but the program starts, and stops, starts, and stops, and
 this newbie is a little perplexed.  Fortunately, it ends up started,
 so I have access to my email, but something is obviously not right
 here.  I have provided below entries from my latest maillog.  Any
 help is appreciated...
 
 
 
 Oct 18 00:00:00 bsd newsyslog[2514]: logfile turned over
 Oct 18 02:20:02 bsd postfix/pickup[2799]: 9EBD01D119: uid=0
 from=root Oct 18 02:20:02 bsd postfix/trivial-rewrite[3032]:
 warning: database /usr/local/etc/postfix/transport.db is older than
 source file /usr/local/etc/postfix/transport
 Oct 18 02:20:02 bsd postfix/cleanup[3031]: 9EBD01D119:
 message-id=[EMAIL PROTECTED]
 Oct 18 02:20:02 bsd postfix/qmgr[906]: 9EBD01D119:
 from=[EMAIL PROTECTED], size=931, nrcpt=1 (queue active)
 Oct 18 02:20:02 bsd postfix/local[3033]: 9EBD01D119:
 to=[EMAIL PROTECTED], orig_to=root, relay=local, delay=302,
 delays=302/0.01/0/0.05, dsn=2.0.0, status=sent (delivered to command:
 IFS=' '  exec /usr/local/bin/procmail -f- || exit 75 #rem)
 Oct 18 02:20:02 bsd postfix/qmgr[906]: 9EBD01D119: removed
 Oct 18 02:45:20 bsd postfix/pickup[2799]: 4E5D11D119: uid=0
 from=root Oct 18 02:45:20 bsd postfix/trivial-rewrite[3247]:
 warning: database /usr/local/etc/postfix/transport.db is older than
 source file /usr/local/etc/postfix/transport
 Oct 18 02:45:20 bsd postfix/cleanup[3246]: 4E5D11D119:
 message-id=[EMAIL PROTECTED]
 Oct 18 02:45:20 bsd postfix/qmgr[906]: 4E5D11D119:
 from=[EMAIL PROTECTED], size=939, nrcpt=1 (queue active)
 Oct 18 02:45:20 bsd postfix/local[3248]: 4E5D11D119:
 to=[EMAIL PROTECTED], orig_to=root, relay=local, delay=19,
 delays=19/0.01/0/0.01, dsn=2.0.0, status=sent (delivered to command:
 IFS=' '  exec /usr/local/bin/procmail -f- || exit 75 #rem)
 Oct 18 02:45:20 bsd postfix/qmgr[906]: 4E5D11D119: removed
 Oct 18 03:02:23 bsd postfix/pickup[3268]: 582321D119: uid=0
 from=root Oct 18 03:02:23 bsd postfix/trivial-rewrite[3583]:
 warning: database /usr/local/etc/postfix/transport.db is older than
 source file /usr/local/etc/postfix/transport
 Oct 18 03:02:23 bsd postfix/cleanup[3576]: 582321D119:
 message-id=[EMAIL PROTECTED]
 Oct 18 03:02:23 bsd postfix/qmgr[906]: 582321D119:
 from=[EMAIL PROTECTED], size=1189, nrcpt=1 (queue active)
 Oct 18 03:02:23 bsd postfix/pickup[3268]: 63AE11D11B: uid=0
 from=root Oct 18 03:02:23 bsd postfix/cleanup[3576]: 63AE11D11B:
 message-id=[EMAIL PROTECTED]
 Oct 18 03:02:23 bsd postfix/qmgr[906]: 63AE11D11B:
 from=[EMAIL PROTECTED], size=2038, nrcpt=1 (queue active)
 Oct 18 03:02:23 bsd postfix/local[3589]: 63AE11D11B:
 to=[EMAIL PROTECTED], orig_to=root, relay=local, delay=0.08,
 delays=0.02/0.01/0/0.05, dsn=2.0.0, status=sent (delivered to command:
 IFS=' '  exec /usr/local/bin/procmail -f- || exit 75 #rem)
 Oct 18 03:02:23 bsd postfix/qmgr[906]: 63AE11D11B: removed
 Oct 18 03:02:23 bsd postfix/local[3588]: 582321D119:
 to=[EMAIL PROTECTED], orig_to=root, relay=local, delay=0.17,
 delays=0.09/0.01/0/0.07, dsn=2.0.0, status=sent (delivered to command:
 IFS=' '  exec /usr/local/bin/procmail -f- || exit 75 #rem)
 Oct 18 03:02:23 bsd postfix/qmgr[906]: 582321D119: removed
 Oct 18 03:16:21 bsd postfix/pickup[3268]: 4F6211D119: uid=0
 from=root Oct 18 03:16:21 bsd postfix/trivial-rewrite[16064]:
 warning: database /usr/local/etc/postfix/transport.db is older than
 source file /usr/local/etc/postfix/transport
 Oct 18 03:16:21 bsd postfix/cleanup[16063]: 4F6211D119:
 message-id=[EMAIL PROTECTED]
 Oct 18 03:16:21 bsd postfix/qmgr[906]: 4F6211D119:
 from=[EMAIL PROTECTED], size=562, nrcpt=1 (queue active)
 Oct 18 03:16:21 bsd postfix/local[16065]: 4F6211D119:
 to=[EMAIL PROTECTED], orig_to=root, relay=local, delay=75,
 delays=75/0.01/0/0.01, dsn=2.0.0, status=sent (delivered to command:
 IFS=' '  exec /usr/local/bin/procmail -f- || exit 75 #rem)
 Oct 18 03:16:21 bsd postfix/qmgr[906]: 4F6211D119: removed
 Oct 18 08:03:12 bsd postfix/postfix-script[17269]: stopping the
 Postfix mail system
 Oct 18 08:03:12 bsd postfix/master[894]: terminating on signal 15
 Oct 18 08:03:12 bsd postfix/postfix-script[17290]: fatal: the Postfix
 mail system is not running
 Oct 18 08:04:42 bsd postfix/postfix-script[894]: starting the Postfix
 mail system
 Oct 18 08:04:42 bsd postfix/master[895]: daemon started -- version
 2.4.5, configuration /usr/local/etc/postfix
 Oct 18 08:04:42 bsd postfix/pickup[902]: B2EE61D131: uid=0 from=root
 Oct 18 08:04:42 bsd postfix/trivial-rewrite[919]: warning: database
 /usr/local/etc/postfix/transport.db is older than source file
 /usr/local/etc/postfix/transport
 Oct 18 08:04:42 bsd postfix/cleanup[914]: B2EE61D131:
 message-id=[EMAIL PROTECTED]
 Oct 18 08:04:42 bsd postfix/qmgr[903]: B2EE61D131:
 from=[EMAIL PROTECTED], size=701, nrcpt=1 (queue active)
 Oct 18 08:04:44 bsd postfix/postfix-script[943]: fatal: the

Re: More Postfix Woes

2007-10-18 Thread Chuck Swiger


On Oct 18, 2007, at 3:42 PM, Rem P Roberti wrote:

Oct 18 03:16:21 bsd postfix/trivial-rewrite[16064]: warning: database
/usr/local/etc/postfix/transport.db is older than source file
/usr/local/etc/postfix/transport


Fix this by doing:

  cd /usr/local/etc/postfix ; postmap transport

[ ... ]
Oct 18 08:03:12 bsd postfix/postfix-script[17269]: stopping the  
Postfix mail system

Oct 18 08:03:12 bsd postfix/master[894]: terminating on signal 15
Oct 18 08:03:12 bsd postfix/postfix-script[17290]: fatal: the  
Postfix mail system is not running


That's bizzare.  Do you have some sort of scripted utility which is  
trying to stop and restart Postfix via cron or some such?


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: More Postfix Woes

2007-10-18 Thread Per olof Ljungmark


Rem P Roberti wrote:

I don't know what is going on with respect to Postfix during my boot
process, but the program starts, and stops, starts, and stops, and this
newbie is a little perplexed.  Fortunately, it ends up started, so I
have access to my email, but something is obviously not right here.  I
have provided below entries from my latest maillog.  Any help is
appreciated...

snip

Oct 18 14:28:15 bsd postfix/trivial-rewrite[2976]: warning: database
/usr/local/etc/postfix/transport.db is older than source file
/usr/local/etc/postfix/transport
Oct 18 14:28:15 bsd postfix/cleanup[2975]: 9D9EF1D0C6:
message-id=[EMAIL PROTECTED]
Oct 18 14:28:15 bsd postfix/qmgr[903]: 9D9EF1D0C6:
from=[EMAIL PROTECTED], size=2780, nrcpt=2 (queue active)
Oct 18 14:28:16 bsd postfix/smtp[2977]: 9D9EF1D0C6:
to=[EMAIL PROTECTED], relay=smtp.comcast.net[204.127.225.17]:25,
delay=1.1, delays=0.03/0.08/0.41/0.57, dsn=2.0.0, status=sent (250 ok ;
id=20071018212731b1100331cce)
Oct 18 14:28:16 bsd postfix/smtp[2977]: 9D9EF1D0C6:
to=[EMAIL PROTECTED], relay=smtp.comcast.net[204.127.225.17]:25,
delay=1.1, delays=0.03/0.08/0.41/0.57, dsn=2.0.0, status=sent (250 ok ;
id=20071018212731b1100331cce)
Oct 18 14:28:16 bsd postfix/qmgr[903]: 9D9EF1D0C6: removed


Hello,

First:

Run postmap transport from the /usr/local/etc/postfix directory

Then, I saw one stop/start in the above, could it be yourself doing it 
or you restarted the machine? Otherwise nothing alarming...


http://www.postfix.org/
is an excellent source of information on Postfix.

Per olof
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: More Postfix Woes

2007-10-18 Thread Gerard

On October 18, 2007 at 06:42PM Rem P Roberti wrote:


 I don't know what is going on with respect to Postfix during my boot
 process, but the program starts, and stops, starts, and stops, and this
 newbie is a little perplexed.  Fortunately, it ends up started, so I
 have access to my email, but something is obviously not right here.  I
 have provided below entries from my latest maillog.  Any help is
 appreciated...

For starters, you should read the Postfix documentation. You might also try
posting on the Postfix forum. Check out http://postfix.com for further details.

Now, before you go any further, the log file is telling you that your
'transport' is out of date. You have to run 'postmap' on it and then restart
Postfix to get it corrected. Try: 'postmap /usr/local/etc/postfix/transport'
assuming that your transport map is named 'transport'. This will update the
mapping.

You should always supply the complete output of: postconf -n when asking
help regarding Postfix. It saves a lot of time.


-- 
Gerard
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: More Postfix Woes

2007-10-18 Thread Rem P Roberti

On 2007.10.19 01:01:39 +, Per olof Ljungmark wrote:
 Rem P Roberti wrote:
 I don't know what is going on with respect to Postfix during my boot
 process, but the program starts, and stops, starts, and stops, and this
 newbie is a little perplexed.  Fortunately, it ends up started, so I
 have access to my email, but something is obviously not right here.  I
 have provided below entries from my latest maillog.  Any help is
 appreciated...
 snip
 Oct 18 14:28:15 bsd postfix/trivial-rewrite[2976]: warning: database
 /usr/local/etc/postfix/transport.db is older than source file
 /usr/local/etc/postfix/transport
 Oct 18 14:28:15 bsd postfix/cleanup[2975]: 9D9EF1D0C6:
 message-id=[EMAIL PROTECTED]
 Oct 18 14:28:15 bsd postfix/qmgr[903]: 9D9EF1D0C6:
 from=[EMAIL PROTECTED], size=2780, nrcpt=2 (queue active)
 Oct 18 14:28:16 bsd postfix/smtp[2977]: 9D9EF1D0C6:
 to=[EMAIL PROTECTED], relay=smtp.comcast.net[204.127.225.17]:25,
 delay=1.1, delays=0.03/0.08/0.41/0.57, dsn=2.0.0, status=sent (250 ok ;
 id=20071018212731b1100331cce)
 Oct 18 14:28:16 bsd postfix/smtp[2977]: 9D9EF1D0C6:
 to=[EMAIL PROTECTED], relay=smtp.comcast.net[204.127.225.17]:25,
 delay=1.1, delays=0.03/0.08/0.41/0.57, dsn=2.0.0, status=sent (250 ok ;
 id=20071018212731b1100331cce)
 Oct 18 14:28:16 bsd postfix/qmgr[903]: 9D9EF1D0C6: removed
 
 Hello,
 
 First:
 
 Run postmap transport from the /usr/local/etc/postfix directory
 
 Then, I saw one stop/start in the above, could it be yourself doing it 
 or you restarted the machine? Otherwise nothing alarming...
 
 http://www.postfix.org/
 is an excellent source of information on Postfix.
 
 Per olof

Thanks Per olof, I will run postmap and see what happens.  As it turns
out, The Book of Postfix just arrived, so I now have some good reference
material on hand.

Rem
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Postfix woes

Re: Postfix woes

Re: Postfix woes

Re: Postfix woes

Re: Postfix woes

Re: Postfix woes

Postfix woes

Re: More Postfix Woes

Re: More Postfix Woes

Re: More Postfix Woes

Re: More Postfix Woes

Re: More Postfix Woes

Re: More Postfix Woes

More Postfix Woes

Re: More Postfix Woes

Re: More Postfix Woes

16 matches

Site Navigation

Mail list logo

Footer information