I've followed both the perfect server guide and the "Virtual Users And Domains With Postfix, Courier And MySQL (Mandriva 2008.0)" step-by-step, which I chose to use because they're the most well-written and practical guides I could find (I didn't really need to use the perfect server guide, but it helped me sort out msec), but I just can't seem to make it work. I'm running into two problems that I'm hoping you'll be willing to help me work out. I've read through about a dozen pages of this forum, and they seem to be pretty common problems, but the posted solutions just didn't help me. The first, and most crippling, problem is getting the server to authenticate me. It just won't, and I can't figure out why. Here's the log snippit: Code: Feb 27 14:29:04 mail postfix/smtpd: warning: SASL authentication failure: could not verify password Feb 27 14:29:04 mail postfix/smtpd: warning: SASL authentication failure: Password verification failed Feb 27 14:29:04 mail postfix/smtpd: warning: 144-12-178-69.gci.net[188.8.131.52]: SASL PLAIN authentication failed: generic failure Feb 27 14:29:04 mail postfix/smtpd: warning: SASL authentication failure: could not verify password Feb 27 14:29:04 mail postfix/smtpd: warning: 144-12-178-69.gci.net[184.108.40.206]: SASL LOGIN authentication failed: generic failure SMTP is definitely listening, and I get asked for a password, but it won't auth. Same goes for POP3: Code: Feb 27 14:32:06 mail pop3d: authentication error: Input/output error Feb 27 14:32:45 mail pop3d: authentication error: Input/output error Feb 27 14:43:30 mail pop3d: authentication error: Input/output error How do I find out what's causing this? I'm beginning to suspect that this might be a mysql access thing, but I don't know how to find out for sure. Can anyone tell me how to proceed from here? My other problem was the tls certs, but that seems to have resolved itself (finally). I was trying to access the server as mail.taylor-madeak.org, while the host name was server.taylor-madeak.org. I ended up just changing the host name to mail.taylor-madeak.org, deleting the old certs, and creating new ones as per the guide, and restarting the server (literal reboot). But...it seemed to take a while to actually start offering the new cert. It's fixed now, but I do have a couple questions: In the future, how do I get that to update sooner? Is there any way I can have the server's hostname set to something different than the DNS record I access it with and not run into that error from my e-mail client (Thunderbird doesn't like mismatched server names on its certs)? I use the server for more than just e-mail, so it doesn't make any sense to lock the hostname down on mail.localdomain. It doesn't seem to hurt anything, either, but if there's a way to work around it I'd like to know it. Thanks in advance!