Qmail, Mail toaster - Revision history

Jimbo: Reverted edits by 201.195.124.66 (Talk); changed back to last version by Jimbo

2009-01-01T06:09:52Z

Reverted edits by 201.195.124.66 (Talk); changed back to last version by Jimbo

Show changes

201.195.124.66 at 23:17, 30 December 2008

2008-12-30T23:17:39Z

83.233.30.38 at 04:27, 19 December 2008

2008-12-19T04:27:52Z

Show changes

Jimbo: revert spam

2008-10-09T00:09:54Z

revert spam

Show changes

94.102.60.77 at 13:20, 8 October 2008

2008-10-08T13:20:45Z

Show changes

Dave: /* Making or Requesting a Certificate for Qmail's TLS */

2008-01-02T22:39:55Z

Making or Requesting a Certificate for Qmail's TLS

Jimbo at 16:35, 21 June 2007

2007-06-21T16:35:37Z

Jimbo: Mail toaster moved to Qmail, Mail toaster

2006-05-28T23:52:36Z

Mail toaster moved to Qmail, Mail toaster

Jimbo: /* Installing Qmail with SMTP Authentication */

2006-05-28T23:26:47Z

Installing Qmail with SMTP Authentication

Jimbo: /* Installing Qmail with SMTP Authentication */

2006-05-28T23:24:55Z

Installing Qmail with SMTP Authentication

@@ Line 146: / Line 146: @@
   ph34r# '''chown root /usr/local/vpopmail/bin/vchkpw'''
-Mmmmm, simple.  That's all we have to do with vpopmail.  As a bonus, installing vpopmail also got us the '''ucspi-tcp''' port, which we'll need to use to keep a daemon listening on port 25 (and port 2525, for reasons we'll discuss later) for incoming SMTP traffic.  Okay, but now that we've got a separate database for mailbox accounts from system accounts, how do we manage it?  That would be two more ports - qmailadmin, and vqadmin.  Vqe MUCH easier.
+Mmmmm, simple.  That's all we have to do with vpopmail.  As a bonus, installing vpopmail also got us the '''ucspi-tcp''' port, which we'll need to use to keep a daemon listening on port 25 (and port 2525, for reasons we'll discuss later) for incoming SMTP traffic.  Okay, but now that we've got a separate database for mailbox accounts from system accounts, how do we manage it?  That would be two more ports - qmailadmin, and vqadmin.  Vqadmin lets us add, delete, and otherwise manage entire domains we want to handle the mail for, while qmailadmin gives us a nice friendly little interface to handle individual mailboxes within individual domains.  First, vqadmin:
 Now let's test POP3 (assuming you want to allow clients to use POP3 as well):

@@ Line 91: / Line 91: @@
 Now we'll need to install a certificate for use with TLS authentication/encryption.  To make a certificate request, you can type in '''make certificate-req''' - but that's all I can tell you about that process; I typically use a self-signed certificate instead (one which is not stored at Thawte or Verisign or one of the other major providers, but only on the local server).  You don't have to pay for a self-signed certificate, where you would for one from Thawte or Verisign ''et al'', but you should be aware that 1. users will be warned that they are being asked to accept a certificate not signed by a recognized authority the first time they connect to a server with a self-signed certificate, and 2. Microsoft Outlook may refuse to connect to a server with a self-signed certificate using TLS '''AT ALL''', so you may need to forgo encryption entirely for Outlook users if you're signing your own certificate.
-Whew!  With that said, actually generating the certificate is easy:
+To use a certificate from a known-and-trusted certifying authority (Thawte/Verisign etc,) you'll need to create a [[CSR]] and send it to them when you ask them for a certificate. Be prepared to pay ~200USD for a cert. They'll send you the certificate back and you'll need to install it on your server. This is made easier by [[webmin]], but you can do it via the commandline using [[OpenSSL]]. Certificate management is outside the scope of this article and not something to be taken lightly, as it can be more subtle and difficult than it initially appears.
   ph34r# '''make certificate'''

← Older revision		Revision as of 16:35, 21 June 2007
Line 687:		Line 687:

	[[Category:Common Tasks]]		[[Category:Common Tasks]]
		+	[[Category:Qmail]]

@@ Line 78: / Line 78: @@
   ph34r# '''patch < Qqxrc.patch.txt'''
-Pay careful attention to the output of the patch program: if it tells you any hunks failed, you'll need to investigate and resolve the problem or who knows what you'll wind up with.  Next, we want to make sure Qmail doesn't tell mail clients that we accept CRAM-MD5 logins, since Qmail would take them but vchkpw would fail to understand them.  You can use [[media:Qmail-noCRAM-MD5.patch.txt]] if you like, but I'd recommend instead just using a "poor man's patch" for this, quick and dirty:
+Pay careful attention to the output of the patch program: if it tells you any hunks failed, you'll need to investigate and resolve the problem or who knows what you'll wind up with.  Next, we want to make sure Qmail doesn't tell mail clients that we accept CRAM-MD5 logins, since Qmail would take them but vchkpw would fail to understand them.  You can use [[media:Qmail-noCRAM-MD5.patch.txt|this patch]] if you like, but I'd recommend just using this quick-and-dirty "poor man's patch" instead:
   ph34r# '''sed -i .bak s/CRAM-MD5\ // qmail-smtpd.c'''

@@ Line 78: / Line 78: @@
   ph34r# '''patch < Qqxrc.patch.txt'''
-Pay careful attention to the output of the patch program: if it tells you any hunks failed, you'll need to investigate and resolve the problem or who knows what you'll wind up with.  Next, we want to make sure Qmail doesn't tell mail clients that we accept CRAM-MD5 logins, since Qmail would take them but vchkpw would fail to understand them.  We're going to use a "poor man's patch" for this, quick and dirty:
+Pay careful attention to the output of the patch program: if it tells you any hunks failed, you'll need to investigate and resolve the problem or who knows what you'll wind up with.  Next, we want to make sure Qmail doesn't tell mail clients that we accept CRAM-MD5 logins, since Qmail would take them but vchkpw would fail to understand them.  You can use [[media:Qmail-noCRAM-MD5.patch.txt]] if you like, but I'd recommend instead just using a "poor man's patch" for this, quick and dirty:
-  ph34r# '''sed -i .bak s/CRAM-MD5 // qmail-smtpd.c'''
+  ph34r# '''sed -i .bak s/CRAM-MD5\ // qmail-smtpd.c'''
 Now we can change back into our port directory and issue a make install.