 |
Now serving 108 guides. |
|
 Qmail (with SSL), Courier IMAP, vpopmail, SA, and ClamAV General Information This guide is designed to help you install FreeBSD and setup qmail with mail filtering abilities. I designed my own qmail guide for a few reasons. First, there really isn't much out there when you look for this type of install from the ports system. Second, I have a vpopmail patch that allows creation of Custom Maildirs. I have been using a custom Maildir structure for about a year and a half now with no issues. The vpopmail skel patch allows you to patch vpopmail so you can make your own custom directories. If you create a user with just the normal vpopmail install, you get a default Maildir with new, tmp and cur in it which really doesn't allow you to do too much with filtering and the like. If you create a new user and vpopmail has been patched with the skel patch, the user's maildir is copied from the ~vpopmail/skel dir. If you really think about it, you can pretty much add your own maildrop recipe into the skel dir along with the .qmail file. If you add the qmailadmin into the mix, you or your users can turn on or off the spam filtering at leisure. If you really know what you're doing, this can open up a whole new world with vpopmail.Requirements
Installation This is a qmailrocks style install with a few modifications:This documentation will install everything you need virtually from ports. When I say virtually, I mean just a few key components are not ported at the present time of this writing. What I love about ports is that upgradng the software is quite simple by just running the portupgrade command and checking a few conf files and you're off and running. The vpopmail skel patch allows you to patch vpopmail so you can make your own custom directories. If you create a user with just the normal vpopmail install, you get a default Maildir with new, tmp and cur in it which really doesn't allow you to do too much with filtering and the like. If you create a new user and vpopmail has been patched with the skel patch, the user's maildir is copied from the ~vpopmail/skel dir. If you really think about it, you can pretty much add your own maildrop recipe into the skel dir along with the .qmail file. If you add the qmailadmin into the mix, you or your users can turn on or off the spam filtering at leisure. If you really know what you're doing, this can open up a whole new world with vpopmail. I have been using a custom Maildir structure for about a year and a half now with no issues. I am dividing up the qmail install into a few separate sections. The first part involves getting qmail running on your box and getting everything working. The second part of it, what I would call "webify" qmail, is adding the options to add users and email lists via qmailadmin and other types of web interfaces like squirrelmail. Lastly, I am working on (this is not documented yet) a way to tell imap to trash emails in the .Spam folder after x days or so. This can become really useful if you have a large ISP with hundreds or thousands of emails. Qmail The qmail program is a secure, reliable, efficient simple message transfer agent. It is meant to be a replacement for the entire sendmail-binmail system that most UNIX hosts use. For more information, Please see the following links:Let's add some users/groups and also we can create the supervise directories. Here is how to run it:
What we want to do is download the qmail source and then extract it. Here is the way we will do this:
The first command is fetching the actual patch from John's site. Replace VER with the version of the patch that you downloaded. Then we will want to apply the patch so run the following commands:
Now run the following commands:
At this point I would not recommend deleting any of the qmail files. They really don't take up a lot of room but if you ever delete anything by accident or need to rebuild your queue, you can stop qmail and then run make setup check and then start qmail again. This by any means won't fix everything but leaving the qmail files there won't hurt a bit. One last thing to recommend is going into /var/qmail/control/locals and making sure that file is empty. If you need a good explanation as to why to do this, take a look at How to use rcpthosts and locals.We are now done getting qmail setup (for now)! WOOT! UCSPI-TCP UCSPI-tcp is a set of command-line tools for building TCP-based client/server applications. They are compliant to UCSPI, the UNIX Client-Server Program Interface. UCSPI tools are available for several different types of networks. For more information, please see http://cr.yp.to/ucspi-tcp.html.Installing ucspi-tcp is pretty straighforward:
rblsmtp with uscpi, that is completely up to you. By experience alone, I can tell you enabling rbls will dramatically decrease the amount of spams you get. If you have or plan to have a large email server, this will definitely help in the long run. The last option SSL is optional so if you plan on adding things like POP or SMTP with SSL, now is the time to do it. You can always install ucspi-ssl later on if you decide not to install it at this time.Other than that, UCSPI-tcp is installed. Simple, eh? EZMLM-IDX Ezmlm-idx is a mailing list addon. It is the best (in my opinion) mailing list option out there. It works quite well with qmailadmin, which we will install later in the guide, and works seamlessly with qmail. For more information, Please see http://www.ezmlm.org/.
Before you can use the programs, you should copy the "ezmlmglrc.sample", "ezmlmrc.sample" and "ezmlmsubrc.sample" files in /usr/local/etc/ezmlm to "ezmlmglrc", "ezmlmrc" and "ezmlmsubrc" respectively.
Qmail-Autoresponder qmail-autoresponder is a program that allows you to setup responders for forwarding and mailing robots in qmailadmin. For more information, please see http://untroubled.org/qmail-autoresponder/.Installing from ports just can't get any easier than this:
Vpopmail Let's get started! One of the first things we need to do is fetch the tarball which contains the vpopmail skel(eton) files. Why do we need this you say? In laymans terms, rather than having vpopmail make a basic Maildir with new, cur and tmp in it, we are going to replace that with a completely customized Maildir. The next few commands will fetch the tarball, extract it in the correct place and then chown and chmod it.
/usr/local/vpopmail so we're going to delete that folder and symlink it to ~vpopmail:
/usr/ports/mail/vpopmail/files folder and then download the patch into it so it's applied automagically!
Your users will be very happy that they will have the ability to turn on or off their spam protection, change their passwords, and all kinda of other fun stuff. Maildrop Maildrop is a replacement for your local mail delivery agent and is similar to mail/procmail. For more information, please see http://www.courier-mta.org/maildrop/.
.qmail file within the users virtual maildir tells maildrop to log in /var/log/qmail/maildrop using multilog. Let's create the directory and then give it proper ownership:
Uninstalling Sendmail Type in the following commands to eliminate sendmail from being called on your box:
/etc/rc.conf like so:
/etc/make.conf like so:
Configuration Qmail Getting this part of qmail going is, well, going to be a little rough. We need to download the scripts for qmail-smtpd, qmail-send, and qmail-pop3d. We will start with making all the needed directories and stuff like that so let's get to it!
There are basically two different ways to set up smtp. There is with TLS and with SSL. I am going to walk you through setting it up with TLS. The file we are going to edit is called smtpd_run. We are going to want to setup smtp-auth with TLS on port 25 so we will configure it like so:IP=1.2.3.4 - Substitute your own IP address. Do not leave this set to 0 without a good reason.PORT=25 - Set the port number we will be listening on.SSL=0 - Do not run an SSL-only service.FORCE_TLS=0 - Refuse to accept mail from clients who have not done STARTTLS.DENY_TLS=0 - Do not refuse to process the STARTTLS command.AUTH=1 - Allow the AUTH command after STARTTLS has been completed.REQUIRE_AUTH=0 - Refuse to accept mail from clients who have not done AUTH.Now let's make the supervise directory and get everything copied over: Note: Since there are a lot of commands here, I decided to make a little script for it.
/var/qmail/supervise/qmail-smtpd/run file in the /etc/tcp/smtp file. Let's say the IP you used was 192.168.9.1. The line should look like this:
Qmail with TLS We need to install ucspi-ssl so qmail will accept smtp connections with ssl. We can do that like so:
/var/qmail/control/servercert.pem file. This file contains the public and private keys used to set up SSL or TLS encryption. It should be readable to the userid which your "qmail-smtpd" program runs as (which is normally the "qmaild" user).Part of the file is a "certificate", which is the public key with a signature applied to it. This is the same kind of signature used when you create an SSL key for use with a secure web site- in fact, if you already have such a certificate from an SSL web site, you can use it (with the matching ".key" file) to build this .pem file. As long as the key and the certificate are both stored in PEM-encoded format, you can "cat" the files together and save the result as "servercert.pem", and it will work. If you don't have such a key, you can create a key and then sign it using itself (also known as a "self-signed" certificate). Clients will complain about the certificate not being signed by a trusted certificate authority, but the encryption is just as secure. The following example shows how to create a self-signed certificate which expires ten years from the date it was created. Let's start with creating the key:
Note: The common name must be the name of the mail server so make sure you enter it on that line.
SpamAssassin SpamAssassin is a mail filter which attempts to identify spam using text analysis and several internet-based realtime blacklists. Additional drop-in rule sets are available at http://wiki.apache.org/spamassassin/CustomRulesets. The official SpamAssassin website is at http://spamassassin.apache.org/.When we install SpamAssassin from ports, it installs all the required Perl Modules for us which makes installing SpamAssassin really, really easy! Start by doing the following:
/usr/local/etc/mail/spamassassin/v310.pre. All you need to do is install the perl module for it and then uncomment it in v310.pre. Pretty easy to do.After running the above command, let's clean up the install:
/usr/local/etc/mail/spamassassin/, you will see four files. Two of them are .sample files and the two others are your SpamAssassin global options. init.pre and v310.pre have many different options to choose from. Enable them at your leisure. We will not be going over them as they are optional settings.What we need to do is get local.cf setup so run the following:
rewrite_header Subject - Leave this commented (#). We will configure qmail-scanner to rewrite the subject for us.report_safe - Leave this commented. This just leaves the message as Spam or Ham and does not save it as an attachment.trusted_networks - Leave this commented. We define this globally in qmail in the /etc/tcp/smtp file.lock_method flock - Leave this commented.required_score - Uncomment this and set this to around 4.3 or so. I have mine set at 3.9 right now and seems to be catching a lot of spams.use_bayes - Leave this commented. We will configure bayes later in the guide.bayes_auto_learn - Leave this also commented. See use_bayes.bayes_ignore_header - Leave these commented. I really don't have a clue as to what this is even used for.Now we need to tell SpamAssassin to run as user qscand. We do this by editing the startup file:
Thats it! SpamAssassin is installed, configured and also running. We are all done! WOOT! ClamAV Clam Antivirus is command line virus scanner written entirely in C and its database is kept up-to-date. For more information, please see: http://www.clamav.net/Installation is straight forward.
Now let's configure the conf files:
Example - needs be commented (#)LogFile - should be uncommented and set to /var/log/clamav/clamd.log
LogTime - should be uncommmentedLogSyslog - should be uncommentedUser - should be uncommented and set to qscandScanMail - should be uncommentedNow let's edit freshclam.conf:
Example - needs be commented (#)DatabaseDirectory - should be uncommented and set to /var/db/clamav/DatabaseOwner - change from clamav to qscandNow just a few ownership changes:
/var/log/clamav/clam-update.log.To tell FreeBSD to start ClamAV on startup:
QmailScanner Qmail-Scanner is e-mail content scanner that enables a qmail server to scan all messages it receives for certain characteristics (normally viruses), and react accordingly. For more information see http://qmail-scanner.sourceforge.net/.When installing qmail-scanner it will install all dependancies for you. So let's go ahead and install it!
Note: If you see an error saying "CANNOT EVEN RUN A SIMPLE SETUID SCRIPT" that means you did not enable Perl with Setuid. Bad news: You will have to make deinstall SpamAssassin, Clamav, and qmail-scanner and start those steps all over again. Now let's install it providing the above worked flawlessly:
/var/qmail/bin. Go ahead and hit enter on the keyboard when it asks.Updating the qmail-scanner version files The first one is the command that updates your version files. It updates your headers when you upgrade ClamAV or SpamAssassin. It also helps keep the/var/spool/qmailscan folder clear when SMTP sessions are dropped. I would HIGHLY suggest putting this in cron and running it once a day. If you don't, you'll see an error pop up frequestly in /var/log/maillog.
/var/spool/qmailscan/quarantine, one message in ~vpopmail/domains/domain.xxx/postmaster/Maildir/new and one in your ~vpopmail/domains/domain.xxx/postmaster/Maildir/.Spam/new folder.If you get any errors like "451 qq temporary problem", you did something wrong and will want to troubleshoot the 451 qq temporary problem. We basically don't need to do anything to qmail-smtpd/run to implement it. The qmail-scanner variable is automatically in the qmail-smtpd/run script as an if ... then statement. If you check your headers, you should now have qmail-scanner working on your system! E-Mail Client Setup Thunderbird Click File, click New and click Account
Select Email account and click Next
Your name: Type in your name as you'd like it to appear in your recipient's "From" field. Email address: Enter your E-mail address Click Next
Server information: Incoming Server: Enter the name or IP address of your server. Global Inbox: Untick this unless you'd like all your Thunderbird Email accounts to store messages in one set of mailboxes Click Next
Incoming User Name: Enter your full E-mail address Click Next
Account Name: Enter the name by which you'll refer to this account, this is only for display purposes within Thunderbird Click Next
Check your settings and click Finish Click Tools, click Account Settings
In the menu on the left-hand side, Click Outgoing Server (SMTP). Click the Edit tab on the right-hand side.
Under the last section under Use secure connection, click TLS and click Ok twice
Microsoft Outlook Click Tools and click E-mail Accounts
Select Add a new E-mail Account and click on Next
Select POP3 from the list and click Next
User Information: Your Name: Enter your name -> this is the name your recipients will see in the "From" field of your E-mails E-mail Address: Enter your E-mail address Logon Information: Username: Enter your email address Password: Enter the password you entered into vpopmail or qmailadmin Server Information: POP3: enter then name ip of your server SMTP: enter then name ip of your server Click "More Settings"
Click the "Outgoing Server" tab Place a tick in the "My outgoing server (SMTP) requires authenticaion" box Select "Use same settings as my incoming mail server Click Next Click Finish
Outlook Express Click "Tools" and then click on "Accounts"
Select the "Mail" tab Click "Add" towards the top right Select "Mail"
Display Name: For the Display Name Type in your Name - This is the name people will see in the "From" field of your Emails Click Next
Email Address: Type in your E-mail address - user@domain.com Click Next
Servers: POP: type in the name or IP address of your server SMTP: type in the name or IP address of your server Click Next
Account Name: user@domain.com <- must be the entire E-mail address Password <- whatever password you configured through vpopmail or qmailadmin Keep "Logon using Secure Password Authentication (SPA) unchecked
Click Finish on the Next screen
Now you should see your account in the white box, select your account and click "Properties"
Click on the "Servers" tab at the box and check the box at the bottom under Outgoing Mail Server "My server requires Authentication" and click "Settings"
Make sure under Logon Information that "Use sam settins as my incoming mail server" is checked.
Optional Configuration This next section is optional. If you want to have web based interfaces for adding users and domains, please continue on.If you don't already have a webserver set up, following http://www.bsdguides.org/guides/freebsd/webserver/apache_ssl_php_mysql.php. Courier-IMAP Courier-IMAP is a server that provides IMAP access to Maildir mailboxes. This IMAP server does not handle traditional mailbox files (/var/spool/mail, and derivatives). It was written for the specific purpose of providing IMAP access to Maildirs. For more information, please visit http://www.courier-mta.org/imap/.Let's start with installing the port and configuring the options for it:
/usr/local/etc/rc.d folder:
/etc/rc.conf
/var/qmail/supervise as the physical location for my service directories, you can use whatever you like except that it cannot be /service itself. The examples below will assume you are using /var/service like I did- if you are using something different, adjust the paths where appropriate.
/service
/usr/local/etc/rc.d:
/etc/rc.conf
/etc/rc.conf. Now we want to make service directories for courier-imap just like you did for courierpassd
/service/courier-imap and make sure its running for more than 1 or 2 seconds.If you want to run an imap ssl service you can, but you need to set that up separately from the stock imap service. I use both, I set up the plain imap service bound to the localhost address only, that way only my web mail (and any local service) can access it. The ssl service is for all your public interfaces.
imapctl stat, you should get a output for imap related services. Very cool, huh? Once the courier daemons are started, we are all done here! WOOT!QmailAdmin QmailAdmin is a cgi program for administering Qmail with vchkpw. It provides a web interface to create users, aliases, install ezmlm lists, and also configure mailing robots. For more information, please see http://www.inter7.com/qmailadmin/.First we want to cd to the port and then run the configure command for qmailadmin. Please change the htmldir and cgibindir to your html and cgi-bin paths on your system:
~vpopmail/bin/vadddomain.vQadmin vqadmin is a web based cgi program. It allows system administrators to perform actions which require root access. The cgi is authenticated using Apache style htpasswd files. Root access is required for adding and deleting domains. A user based ACL provides control over what actions can be performed, such as adding/deleting a domain. Accessing user email account information to allow modification of user passwords and quotas. Account service restrictions include enabling or disabling of pop access, authentication based smtp relay control, courier-imap access and sqwebmail access.vqadmin and qmailadmin can work together. qmailadmin can be used to allow users to administer their own domains but not create new domains. Creation or deletion of domains is normally associated with the owner/admins of the machine. vqadmin is for owner/admins or their technical support staff. Let's start by changing to the vqadmin folder and then running the following make commands. Please change the cgi-bin and htmldir paths as required:
AuthUserFile to the path where you will put the .htpasswd file. You can put this file anywhere on your system but I do not recommend that you put it into your www or cgi-bin folders. This is very insecure if you do that.
.htaccess file so only the Apache user can read it. You may need to change the chown to either "nobody", "apache", or "www" etc., depending on what user your installation of Apache is running as:
admin_password below to a password you choose to use to login to the site.
Squirrelmail SquirrelMail is a standards-based webmail package written in PHP4. It includes built-in pure PHP support for the IMAP and SMTP protocols, and all pages render in pure HTML 4.0 (with no Javascript) for maximum compatibility across browsers. It has very few requirements and is very easy to configure and install. SquirrelMail has all the functionality you would want from an email client, including strong MIME support, address books, and folder manipulation. For more information, please see http://www.squirrelmail.org.To install squirrelmail port, run the following command:
/usr/local/www and install all required modules. Now what we will want to do is symlink the webmail location. The reason why we are doing it this way is because we won't want to move the squirrelmail folder to your webmail location as that will make portupgrading harder for you. If we symlink it, it's kinda like an alias.
1 - Organization Preferences, any one of the settings inside this window are optional. When you are done, hit S to save and then hit Enter and then hit R to go back to the Main Menu.Now we want to go to 2 - Server settings. Hit 1 for Domain and hit Enter on the keyboard. You can type the name of the server, the local IP, or public IP, whichever you prefer. If your mailserver is behind a router/firewall, I use the local IP. If you are on the public side of things, the hostname or the static IP will work fine. If you are using a dyndns service like dyndns.org, I would highly suggest using the local IP and putting your qmail server behind a router/firewall.Now we need to change the SMTP server settings. Hit B for Update SMTP Settings and hit Enter. Please verify the following settings:
Just to make sure Squirrelmail is working okay, we will want to run the config test. Do this by going to http://your-squirrelmail-location/src/configtest.php. Replace the your-squirrelmail-location with your ip or your hostname. This will tell you if squirrelmail is setup correctly. If you see this:
Upgrading and Maintaining the Qmail System Upgrading your ports and maintaining them are pretty easy. The first thing I would recommend is installing portupgrade from/usr/ports/sysutils/portupgrade. Once that is installed, you can run man portupgrade or just run portupgrade -r name. The -r switch means to upgrade everything recursively. Recurvisly meaning all of it's dependancies, or more simply, anything the program requires. You can do this for anything else not related to qmail or any of its programs. So for instance portupgrade -r kde, it will upgrade kde and all it's dependancies.Another thing I would recommend using is portaudit. If you have your system setup correctly, you will get portaudit reports in your daily security logs. This will give you any warnings about any obsolete packages and/or any security warnings in regards to anything being installed. The following is the recommended way to upgrade programs from ports. Mostly we will be running through backing up .conf files and running portupgrade and then making sure everything is chmodded or chowned correctly. Qmail Qmail doesn't require any type of upgrades. Qmail hasn't been upgraded since 1997 or 1998 but it is very stable and very secure.UCSPI-TCP Pretty much the same as qmail. I don't think has changed at all. Quite honestly, I have never upgraded it and I haven't ever had a problem with running any old/previous versions.Daemontools Again, Pretty much the same as qmail or UCSPI-TCP.Ezmlm-idx This can change from time to time. I would first backup your list which resides in~vpopmail/domains/domain.xxx/listname before upgrading the port. Then upgrade it.
Qmail-Autoresponder This can be upgraded when new versions come out. In most cases the following works fine:
Vpopmail Portupgrading this can go great or it can really screw up your system. Before running a portupgrade I would highly recommend backing up the entire ~vpopmail folder. If you have the patch file inside/usr/ports/mail/vpopmail/files, things should go okay. I have yet to have run a portupgrade -r vpopmail on my box as I have the latest version. Vpopmail doesn't change too frequently but check it for any Vulnerabilites.Please make sure to run the following after upgrading vpopmail to make sure it works ok with TLS:
SpamAssassin When I have run portupgrades with Spamassassin in the past, I usually don't run into any issues except the upgrade from 2.6x to 3.0.1. There were quite a few changes from version to version including some of the required modules that were new, like the SPF addon for it and such. If you do run a portupgrade on Spamassassin, I would go to Spamassassins website (http://www.spamassassin.org) and read the README files under the download section of the site. There it will tell you any changes/modifications that have been done since the previous version. I would also check the rules under/usr/local/etc/mail/spamassassin file, specifically local.cf, to see if any additions or deletions were made.Restart Spamassassin and then we will need to update the qmail-scanner database by running the following commands:
ClamAV ClamAV is probably the worst one out of all of them all but I make it easy for you. ClamAV changes almost every three months, possibly sooner. I would recommend backing up theclamd.conf and freshclam.conf in /usr/local/etc, upgrade, and then change the ownerships.
clamd.conf and freshclam.conf back to /usr/local/etc and then run freshclam to make sure everything is working perfectly. Restart clamd and then we will need to update the qmail-scanner database.
Qmail-scanner At the time of this writing, I would not recommend doing a portupgrade of qmail-scanner. There are a few reasons why. First, it does not even register with the packages system as we run the configure commands manually. Second, we manually patch it with the qms-analog patch to get the nifty qmail-analog reports. So if a new vesion of qmail-scanner is released, I will update the documentation within a few days of it being released.Courier-imap Upgrading this shouldn't be too bad. What I would suggest doing is backing up the files, upgrade courier-imap, and copy the backup files back over.
Qmailadmin This is something else I wouldn't recommend doing a portupgrade on. When the new version comes out just run through the guide as normal only using the newest version from ports after running the following command. It just can't get any easier than that!
vqAdmin Nothing needs to be backed up here. Follow the guide when the the new version comes out after running:
Squirrelmail This one is a rarity but every so often a squirrelmail upgrade does come up and if it does, backup your squirrelmail folder and then run
Author: Bill 8 Comments Posted by staffan on February 28, 2007 at 8:19:03 pm EET
Problem executing the users.sh script.
The script users.sh contains the following row: chown -R qmaill:wheel /var/log/qmail ...which does not work for me (chown: qmaill: Invalid argument). Does'nt the group qmaill need to exist before running this command? Regards, Staffan Posted by w0ls0n on February 28, 2007 at 8:26:47 pm EET
Hi,
This guide has not been updated in quite some time. I am going through a few more changes before I update the final draft. Take a look at the updated guide at freebsdrocks.net as that is more current. Posted by staffan on February 28, 2007 at 8:29:04 pm EET
Problem executing the users.sh script.
The script users.sh contains the following row: chown -R qmaill:wheel /var/log/qmail ...which does not work for me (chown: qmaill: Invalid argument). Does'nt the group qmaill need to exist before running this command? Regards, Staffan Posted by utech on March 09, 2007 at 3:10:41 pm EET
I recently installed what will be a new mailserver for my organization. I was using this guide...
and I got John Simpson's patches and applied them (version qmail-1.03-jms1.6ca.patch since that's the latest stable one). All patches apply fine. I then run make man. That's fine. Then comes make setup check, which terminates in a fantastic error, which apparently nearly no one has experienced before: [root@amnesiac ~/qmail-1.03]# make setup check ./load qmail-remote control.o constmap.o timeoutread.o timeoutwrite.o timeoutconn.o tcpto.o now.o dns.o ip.o ipalloc.o strsalloc.o ipme.o quote.o ndelay.a case.a sig.a open.a lock.a seek.a getln.a stralloc.a alloc.a substdio.a error.a str.a fs.a auto_qmail.o base64.o qregex.o `cat dns.lib` `cat socket.lib` -lssl -lcrypto qmail-remote.o(.text+0x164: In function `smtp': : undefined reference to `SSL_CTX_set_client_cert_cb' *** Error code 1 Stop in /root/qmail-1.03. this is my uname -a: FreeBSD amnesiac.mydomain.com 6.2-RELEASE FreeBSD 6.2-RELEASE #1: Fri Mar 2 22:25:04 EST 2007 root@:/usr/src/sys/amd64/compile/Amnesiac amd64 openssl is installed and working via openssl command. I'm not sure what else I may be able to do to get this resolved. Any help would be appreciated Posted by w0ls0n on March 17, 2007 at 5:29:55 pm EET
Hi,
I am not sure what would cause that. I just tried Johns latest patch 6cb I believe it is and it patches fine for me. I don't believe I ever tried 6ca. I know 6c worked and John just made a slight addition to 6ca. Try 6cb and see how it works on a freshly extracted qmail source. Posted by utech on March 27, 2007 at 3:14:56 pm EEST
Maybe it has something to do with running a 64-bit kernel and libs?
Posted by w0ls0n on March 27, 2007 at 3:46:04 pm EEST
I ran a 64-bit kernel on FreeBSD for a while without any issues for about a year or more. Decided to upgrade it and use it for a gaming box instead.
Posted by epoxy_nc on June 14, 2007 at 8:01:49 am EEST
"Problem executing the users.sh script.
this guide is a little outdated.. install qmail from ports ... THEN start the guide and patch it... |
Copyright 2003 - 2010 BSD Guides. All rights reserved. |
About | Terms of Use | Privacy | Contact |