Comments on: Tiger to Leopard Server Migration, Part Three http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/ Apple Certified Mac Consulting Sat, 27 Feb 2010 07:10:07 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Willard http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-215 Willard Mon, 20 Oct 2008 17:55:38 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-215 Hi, I just did everything that's in there, in fact I already did it before too. Is there a way to get rid od the corrupted db etc and start from scratch. I have backed up everything so I'm willing to take the risk. thanks Hi,

I just did everything that’s in there, in fact I already did it before too. Is there a way to get rid od the corrupted db etc and start from scratch. I have backed up everything so I’m willing to take the risk.

thanks

]]> By: Brent http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-222 Brent Mon, 20 Oct 2008 16:43:04 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-222 It looks like you have some Cyrus IMAP problems. Start with the <a href="http://images.apple.com/server/macosx/docs/Mail_Service_Admin_v10.5_2nd_Ed.pdf" rel="nofollow">Mail Service Admin manual</a>, page 57. It looks like you have some Cyrus IMAP problems. Start with the Mail Service Admin manual, page 57.

]]> By: willard http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-218 willard Mon, 20 Oct 2008 15:50:23 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-218 let me switch on notification so I don't miss you.... let me switch on notification so I don’t miss you….

]]> By: willard http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-202 willard Mon, 20 Oct 2008 15:49:38 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-202 Hi Brent, Somehow the mail.log stopt populating with data the mailaccess.log shows this (doesn't look good to me) Oct 20 10:27:12 server pop3[5100]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:31:09 server pop3[5265]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:32:12 server pop3[5312]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:34:32 server imap[5397]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:37:12 server pop3[5504]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:41:09 server pop3[5675]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 10:42:12 server pop3[5721]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:47:12 server pop3[5915]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:51:09 server pop3[6080]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:52:12 server pop3[6123]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 10:57:12 server pop3[6318]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 11:01:09 server pop3[6483]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 11:02:12 server pop3[6531]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 11:07:12 server pop3[6720]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 11:11:09 server pop3[6892]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 11:12:12 server pop3[6946]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 13:22:16 server imap[12084]: TLS server engine: No CA file specified. Client side certs may not work Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: couldn't checkpoint: Invalid argument Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: sync /var/imap/db: cyrusdb error Oct 20 14:17:00 server ctl_cyrusdb[14765]: DBERROR: critical database situation Oct 20 14:17:09 server ctl_cyrusdb[14830]: cleaning up corrupted database files in: /var/imap/db Oct 20 14:17:09 server ctl_cyrusdb[14830]: ----: removed file: __db.001 Oct 20 14:17:09 server ctl_cyrusdb[14830]: ----: removed file: __db.002 Oct 20 14:17:09 server ctl_cyrusdb[14830]: ----: removed file: __db.003 Oct 20 14:17:09 server ctl_cyrusdb[14830]: ----: removed file: __db.004 Oct 20 14:17:09 server ctl_cyrusdb[14830]: ----: removed file: __db.005 Oct 20 14:17:09 server ctl_cyrusdb[14830]: ----: removed file: log.0000000001 Hi Brent,

Somehow the mail.log stopt populating with data

the mailaccess.log shows this (doesn’t look good to me)

Oct 20 10:27:12 server pop3[5100]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:31:09 server pop3[5265]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:32:12 server pop3[5312]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:34:32 server imap[5397]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:37:12 server pop3[5504]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:41:09 server pop3[5675]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 10:42:02 server ctl_cyrusdb[5710]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 10:42:12 server pop3[5721]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:47:12 server pop3[5915]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:51:09 server pop3[6080]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:52:12 server pop3[6123]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 10:57:12 server pop3[6318]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 11:01:09 server pop3[6483]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 11:02:12 server pop3[6531]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 11:07:12 server pop3[6720]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 11:11:09 server pop3[6892]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 11:12:02 server ctl_cyrusdb[6935]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 11:12:12 server pop3[6946]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 11:42:02 server ctl_cyrusdb[8113]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 12:12:02 server ctl_cyrusdb[9304]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 12:42:02 server ctl_cyrusdb[10485]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 13:12:02 server ctl_cyrusdb[11680]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 13:22:16 server imap[12084]: TLS server engine: No CA file specified. Client side certs may not work
Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 13:42:02 server ctl_cyrusdb[12863]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: couldn’t checkpoint: Invalid argument
Oct 20 14:12:03 server ctl_cyrusdb[14225]: DBERROR: sync /var/imap/db: cyrusdb error
Oct 20 14:17:00 server ctl_cyrusdb[14765]: DBERROR: critical database situation
Oct 20 14:17:09 server ctl_cyrusdb[14830]: cleaning up corrupted database files in: /var/imap/db
Oct 20 14:17:09 server ctl_cyrusdb[14830]: —-: removed file: __db.001
Oct 20 14:17:09 server ctl_cyrusdb[14830]: —-: removed file: __db.002
Oct 20 14:17:09 server ctl_cyrusdb[14830]: —-: removed file: __db.003
Oct 20 14:17:09 server ctl_cyrusdb[14830]: —-: removed file: __db.004
Oct 20 14:17:09 server ctl_cyrusdb[14830]: —-: removed file: __db.005
Oct 20 14:17:09 server ctl_cyrusdb[14830]: —-: removed file: log.0000000001

]]> By: Brent http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-158 Brent Mon, 20 Oct 2008 15:27:42 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-158 Willard, note the permissions errors. Prefix the command with 'sudo'. However, by now it doesn't matter, because postfix polls the alias database, and any changes that you have made would have taken effect. Perhaps you didn't run newaliases with privilege either. Try 'sudo newaliases; sudo postfix reload'. Note also, whether there are any error messages after you run newaliases. Willard, note the permissions errors. Prefix the command with ’sudo’.

However, by now it doesn’t matter, because postfix polls the alias database, and any changes that you have made would have taken effect. Perhaps you didn’t run newaliases with privilege either. Try ’sudo newaliases; sudo postfix reload’. Note also, whether there are any error messages after you run newaliases.

]]> By: willard http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-220 willard Mon, 20 Oct 2008 11:59:06 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-220 Hi Brent, There seems to be a paradox. Postfix is running but claims not to be. I did reload and sent a mail to root. Oct 17 20:31:03 server postfix/postfix-script[18964]: fatal: the Postfix mail system is not running Oct 17 20:32:06 server postfix/postalias[19040]: fatal: open /etc/aliases.db: Permission denied Oct 17 20:33:56 server postfix/postfix-script[19135]: fatal: the Postfix mail system is not running Oct 17 20:39:04 server postfix/postfix-script[19334]: fatal: the Postfix mail system is not running Oct 17 20:40:10 server postfix/postfix-script[19450]: fatal: the Postfix mail system is not running Oct 17 20:45:53 server postfix/postfix-script[19700]: fatal: the Postfix mail system is not running Oct 17 20:46:07 server postfix/postalias[19754]: fatal: open database /etc/postfix/aliases.db: Permission denied Oct 17 20:46:44 server postfix/postfix-script[19784]: fatal: the Postfix mail system is not running Oct 20 13:53:03 server postfix[13322]: error: to submit mail, use the Postfix sendmail command Oct 20 13:53:03 server postfix[13322]: fatal: the postfix command is reserved for the superuser Oct 20 13:53:44 server postfix/postfix-script[13361]: fatal: the Postfix mail system is already running Hi Brent,

There seems to be a paradox. Postfix is running but claims not to be.
I did reload and sent a mail to root.

Oct 17 20:31:03 server postfix/postfix-script[18964]: fatal: the Postfix mail system is not running
Oct 17 20:32:06 server postfix/postalias[19040]: fatal: open /etc/aliases.db: Permission denied
Oct 17 20:33:56 server postfix/postfix-script[19135]: fatal: the Postfix mail system is not running
Oct 17 20:39:04 server postfix/postfix-script[19334]: fatal: the Postfix mail system is not running
Oct 17 20:40:10 server postfix/postfix-script[19450]: fatal: the Postfix mail system is not running
Oct 17 20:45:53 server postfix/postfix-script[19700]: fatal: the Postfix mail system is not running
Oct 17 20:46:07 server postfix/postalias[19754]: fatal: open database
/etc/postfix/aliases.db: Permission denied
Oct 17 20:46:44 server postfix/postfix-script[19784]: fatal: the Postfix mail system is not running
Oct 20 13:53:03 server postfix[13322]: error: to submit mail, use the Postfix sendmail command
Oct 20 13:53:03 server postfix[13322]: fatal: the postfix command is reserved for the superuser
Oct 20 13:53:44 server postfix/postfix-script[13361]: fatal: the Postfix mail system is already running

]]> By: Brent http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-196 Brent Fri, 17 Oct 2008 19:58:55 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-196 You could also try reloading postfix after running newaliases: <code>sudo postfix reload</code> You could also try reloading postfix after running newaliases: sudo postfix reload

]]> By: Brent http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-195 Brent Fri, 17 Oct 2008 19:55:34 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-195 What does /var/log/mail.log say when you send an email to root@? What does /var/log/mail.log say when you send an email to root@?

]]> By: Willard http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-194 Willard Fri, 17 Oct 2008 19:26:35 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-194 <blockquote> Every UNIX server has a few standard email addresses: root@hostname, and postmaster@hostname, for example. You need to tell the server where to send email that the system sends to these addresses. To do that, you need to edit the /etc/postfix/aliases file. Edit at least the first aliases, at the top of the file: # Person who should get root's mail. Don't receive mail as root! root: brentk # Basic system aliases -- these MUST be present MAILER-DAEMON: postmaster postmaster: root This tells the system to send email addressed to root@ to brentk@, and email going to MAILER-DAEMON@ to postmaster@, and email going to postmaster@ to root@. So ‘brentk’ gets everything. If you have any other email aliases, you could add them to this file too. Mail doesn’t need to go to a local user; instead of just ‘brentk’, I could have put ‘brentk@gmail.com’ (not my address — apologies to the imposter) instead. Once you have edited the aliases file, you need to run the “newaliases” command. </blockquote> I did this and even postalias /etc/postfix/aliases before newaliases but it doesn't seem to have any effect. Postmaster mail is not ent to the OD user I redirected it to. anything else I might be missing? (OSX 10.5.5 server)

Every UNIX server has a few standard email addresses: root@hostname, and postmaster@hostname, for example. You need to tell the server where to send email that the system sends to these addresses. To do that, you need to edit the /etc/postfix/aliases file.

Edit at least the first aliases, at the top of the file:

# Person who should get root’s mail. Don’t receive mail as root!
root: brentk

# Basic system aliases — these MUST be present
MAILER-DAEMON: postmaster
postmaster: root

This tells the system to send email addressed to root@ to brentk@, and email going to MAILER-DAEMON@ to postmaster@, and email going to postmaster@ to root@. So ‘brentk’ gets everything.

If you have any other email aliases, you could add them to this file too. Mail doesn’t need to go to a local user; instead of just ‘brentk’, I could have put ‘brentk@gmail.com’ (not my address — apologies to the imposter) instead.

Once you have edited the aliases file, you need to run the “newaliases” command.

I did this and even postalias /etc/postfix/aliases before newaliases

but it doesn’t seem to have any effect. Postmaster mail is not ent to the OD user I redirected it to. anything else I might be missing?
(OSX 10.5.5 server)

]]> By: Ivailo Djilianov http://www.netmojo.ca/2007/11/14/tiger-to-leopard-server-migration-part-three/comment-page-1/#comment-156 Ivailo Djilianov Fri, 18 Jan 2008 06:34:05 +0000 http://www.netmojo.ca/blog/2007/11/14/tiger-to-leopard-server-migration-part-three/#comment-156 Great series of posts, they make me far more confident in what I'm about to do in a couple of hours. Wish me luck ;-) BTW, have you considered migrating mail boxes via the mailbfr script of http://osx.topicdesk.com/ ?Anybody going that way, I suggest they do a full backup of all mail settings on Tiger, then restore only mail data on Leopard and tweak the config files manually. Great series of posts, they make me far more confident in what I’m about to do in a couple of hours. Wish me luck ;-) BTW, have you considered migrating mail boxes via the mailbfr script of http://osx.topicdesk.com/ ?Anybody going that way, I suggest they do a full backup of all mail settings on Tiger, then restore only mail data on Leopard and tweak the config files manually.

]]>