Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Inconsistent Startup file names' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Inconsistent Startup file names
Authored by: babbage on May 10, '05 05:52:34PM

In the start of the hint, we're told that the file names / paths are /Library/Startup Items/Postfix/Postfix and /Library/Startup Items/ Postfix/StartupParameters.plist.

In the file listing section of the hint, we're told to edit /Library/StartupItems/Postfix/StartupItems/StartupItems.plist and /Library/StartupItems/Postfix/StartupItems/postfix.

Neither of these quite looks right to me.

Under Panther and earlier, the standard location for system-wide startup items was /Library/StartupItems/Foo. This seems to be deprecated in Tiger, but it still works, so unless you're rewriting things to be totally the Tiger/launchd way, you should continue to use the Panther style naming convention. Therefore, the directory is StartupItems -- without a space in it, and the structure within the directory is two files: an executable program with the same name as the directory, and a StartupParameters.plist file with configuration options. (There can optionally be more stuff under a Resources directory, but this is uncommon; ususally the startup script is just a Bourne shell script with no unusual dependencies.)

Therefore, for this hint, the full path to the files needed to start up things will be as follows: /Library/StartupItems/Postfix/Postfix
/Library/StartupItems/Postfix/StartupParameters.plist


Now, that said, there was already a StartupItem for Postfix under /System/Library/StartupItems/Postfix under Panther. It looks like Tiger has replaced this with /System/Library/LaunchDaemons/org.postfix.master.plist, and as far as I can tell, the only thing you have to do to enable it is to set MAILSERVER=-YES- in your /etc/hostconfig file. That's all I did with my Mac at home, and the Postfix SMTP daemon starts up just fine at boot time. I suspect that you could just totally leave that step out of these instructions and everything will work just fine.

The bigger problem I'm having, and the reason that I'm reading this article to begin with, is that I had to do a clean install (and didn't think to backup my /System tree before doing so) and now IMAP isn't working for me. So far, nothing I've managed has been able to get it to come back to life. I can connect to the IMAP daemon by doing a telnet localhost imap, but I can't connect, and the mail.log just shows a bunch of failed login attempts from user "???" (sic). I found discussion that seems to clarify some things -- in particular, it seems that the authentication mechanism has changed so that the IMAP daemon must use PAM now, when that was optional before -- but I still can't get it to establish a connection.

I'm going to try the steps from this article when I get home, and will post a followup if I get anywhere with it...

---

--
DO NOT LEAVE IT IS NOT REAL

[ Reply to This | # ]

imap fixed; still can't get imaps to work
Authored by: babbage on May 10, '05 06:42:08PM

Okay, it looks like the suggestion in this hint did the trick for getting my IMAP daemon working, at least in non-SSL mode. I'm still trying to get the other half working, but I can at least start using the IMAP server now.

$ sudo cp /etc/pam.d/ftpd /etc/pam.d/imap
$ sudo cp /etc/pam.d/ftpd /etc/pam.d/pop3

I also did the security symlink, but it doesn't seem to have helped:

$ sudo ln -s /usr/include/pam /usr/include/security

I am, admittedly, cargo culting a bit here. When I figure out how to get this working and what had to happen to make it work, I'll come back and write a cleaner version of the steps that were followed.

---

--
DO NOT LEAVE IT IS NOT REAL

[ Reply to This | # ]

imap fixed; still can't get imaps to work
Authored by: babbage on May 11, '05 05:47:20PM

Ahh, I've got it. Once the xinet.d changes have been made, you have to force the daemon to rescan its config file. The easiest way to do this is simply sudo killall -HUP xinetd; after doing this, I've got IMAP/SSL working again. W00t! :-)

---

--
DO NOT LEAVE IT IS NOT REAL

[ Reply to This | # ]

imap fixed; still can't get imaps to work
Authored by: thePervertedMonk on May 13, '05 04:45:10PM

Hey Babbage,

Any chance of you documenting your process, as promised.
Been trolling, hunting and under-the-bridge sitting, since my Tiger upgrade to get my Postfix up and running.

Used to use: Postfix-Enabler before. I'm not cheapo, but the $9.95 just gave me the incentive to try and get it done myself (with macosxhints.com help, of course).

I've been reading several articles, but nothing concrete and comprehensive.

Looking at your success, I hope you can post something soon.

Cheers.

---
/the Perverted Monk
"my rant is my giant exhale... my exasperation at this approximation
of civilization that causes mad denigration in multiple nations"



[ Reply to This | # ]
imap fixed; still can't get imaps to work
Authored by: mpursley on Oct 14, '05 11:43:36AM

Hey Babbage,

My imapd is broken also...

What I did was use passwd on one user in my box to change the password. That change worked fine... for ssh anyway. But now when I `telnet localhost 143` and use "a login <username> <password>" I get denied for the user that I change the password... but all the other users can get in just fine...

[code]
"a login <user1> <unchaged_password>"
a OK [CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS BINARY UNSELECT SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User <user1> authenticated

"a login <user2> <new_password>"
a NO LOGIN failed
[/code]


I made the /usr/include/security link and /etc/pam.d/ftpd copies. Didn't seem to help... Any other suggestions?


Thanks,
M@



[ Reply to This | # ]
Inconsistent Startup file names
Authored by: dlhull on May 11, '05 06:15:16PM
It looks like Tiger has replaced this with /System/Library/LaunchDaemons/org.postfix.master.plist, and as far as I can tell, the only thing you have to do to enable it is to set MAILSERVER=-YES- in your /etc/hostconfig file.

Yes, but if you examine that file, you'll see that it calls master with the argument list -e 60 which tells it to exit after 60 seconds. So whenever a new file appears in /var/spool/postfix/maildrop, launchd starts master to process it, but master then shuts down again.



[ Reply to This | # ]