I have been planning on installing mail on this server for quite some time but never really got around to do it, until now. So qmail it is. Found the qmailrocks.org website and followed their FreeBSD installation guide.
The only thing that has not really been as described is the php.ini file. I didnt have any at all but I had the distribution one so I made a copy of it:
cp /usr/local/etc/php.ini-dist /usr/local/etc/php.ini
I got as far as to page 13, has to continue some other day.
Update 2004-07-21: Today I got a bit further and now I have both CLAM antivirus protection and SpamAssassin installed.
Update 2004-08-30: Today I finished the whole installation according to qmailrocks but there are still things to be done:
- Existing users should have mail accounts
- Support for .forward(installed dot-forward but didnt configure qmail)
- Support for procmail
- Finish the Horde and Imp installation
2004-09-03: Continuing with qmail. So I found out by reading LifeWithQmail that the /var/qmail/users/assign controlls which users that gets addresses. Though when I ran qmail-pw2u I got this error all the time:
qmail-pw2u: fatal: unable to find alias user
and I couldn’t figure out why. Reading in some forums I started to get a clue. If a include file exists it must list alias otherwise will qmail-pw2u give this error. Which is a bit strange, specifically since I had an assignment file without alias before I started to look into this. The assignment file that is produced from the QmailRocks installation doesn’t have it and qmail definetly works after that installation.
So should I edit my newly created assign file and remove alias or should it be kept? The generated file includes three different alias rules, and according to the documentation the alias user is a catch-all user.
Still cannot get it to work to send e-mail to an ordinary user: gets: Sorry, no mailbox here by that name. vpopmail (#5.1.1)
Thanks for having that helpful little tidbit of info about the /var/qmail/assign/include file, it helped me fix an issue! Found your site on google . . .