😮 [b:1dc14543e5]You don’t risk losing ANY accounts! [/b:1dc14543e5]Sorry, didn’t intend to mislead…
Fundamentally, you risk duplicating messages that are stored on the Server by POP Clients, as well as losing any mail transactions that are active at the time of reconfiguration – that is why I mentioned the precaution. Same thing can happen when you rebuild Apple MailServer Database.
[i:1dc14543e5][b:1dc14543e5]Worst case is users that use POP and store mail on server have to download a new mailbox full of mail the’ve already got…[/b:1dc14543e5][/i:1dc14543e5]
I will be testing a SIMILAR configuration out over the next week.
I believe that mail will work (in BOTH DIRECTIONS!) if you tell Apple MailServer (Squirrelmail) to store mail in “alternate location” (rather than the default contiguous database), and use the Unix default directory, then the MailServer can be made to work with Postfix and other local Unix mail daemons and apps (in addition to POP, SMTP and IMAP email clients) which should therefore include PHP.
Note that CLI sendmail works too (without being daemonised) using the standard default Apple MailServer configs. I must check whether this transaction is a file-based or SMTP:25.
Use
[b:eee4bb4c55]Server Settings | Internet | MailService | Configure Mail Service
and select “Use Alternate Alternate Mail Location”[/b:eee4bb4c55]
As I remember, the default mail storage should be /var/mail (it’s been a while and this must be checked).
WARNING: Clear ALL mail on your Server BEFORE, and temporarily disable POP, IMAP and SMTP, while making this change, otherwise there may be duplication of accounts and messages including a loss of POP sync for read/unread mail stored on the server.
I am slightly surprised no official response has been made to your request and suggest that it may be considered a case of “RTFM” (I am refereing to the OS X Server Admin Guide).
Recent Comments