When I try to send email to gmail,this is the error:
Jun 25 23:50:57 195 postfix/smtp[5560]: connect to mail-smtp-in.l.google.com[64.233.183.27]: Connection refused (port 25)

What is wrong ?

more power to you steve and God Bless.

Users in mysql are in a simple table with the following fields: id, login, hashed_passwd. I used the encrypt() function in mysql, which simply calls the system encrypt. By default encrypt() uses a 2 character salt and generates a DES hash, but if you give an MD5 style salt it will generate an MD5 password hash instead. If you use the builtin md5() function mysql can handle it fine but pam will not.

I know that postfix can use mysql for a whole host of lookups but I haven’t ever actually configured any of those things. Maybe I’ll try it sometime in the future but I don’t have a non-production machine to play with at the moment.

great article!

if it isn’t too much to ask, can you include a mysql lookup instead of systems users.

TIA

I’ve figured out what I feel is a much easier way to deal with this issue.
I created a bind mount between /var/run/saslauthd and
/var/spool/postfix/var/run/saslauthd by adding the following line to
/etc/fstab and creating the /var/spool/postfix/var/run/saslauthd
directory:

/var/run/saslauthd /var/spool/postfix/var/run/saslauthd none rw,bind 0 0

I’m pretty sure I left everything else about saslauthd alone at that
point. The end result is that the saslauthd directory is located at
/var/run/sasluthd, the default configuration, and that location is
mounted inside the postfix chroot as well.

This is the method I would recommend, rather than mucking about with the
symbolic links.

If you’d still like to do it the way I first figured out, you’ll have to
do a little bit of editing in the init script for saslauthd.

Look at the much-easier-to-read version of this guide, at
http://wiki.ev-15.com/debian:mail_system#sasl
and read starting at “Finish SASL Configuration”

You’ll see where I mention adding a PARAMS= line to the file, changing
PWDIR and PIDFILE, and adding a couple lines to force removal of the
/var/run/saslauthd directory and creation of the symbolic link.

You’ll also see “Update #2″ where I recommend the bind mount method. I
just added this today, though I should have added it a while ago.

Let me know how things go.

server# rmdir /var/run/saslauthd
server# ln -s /var/spool/postfix/var/run/saslauthd /var/run/saslauthd

When I try to restart the sasl daemon, I get the following error:

mkdir: cannot create directory `/var/run/saslauthd’: File exists

Any help with this would be GREATLY appreciated.

http://hannibal.solstice.nl/version-2.0/on_debian/hannibal-3.0_on-debian-sarge_2004-04-02.html.orig
but am now pretty confused on how to properly tie in the ldap portion. They also use Amavis and the clamav filters. Of course their examples include lots of other functionality that I am not going to be using.

I plan on adding lots of users and don’t want to create local user accounts. I had looked in MySQL with Courier, but gave up after so many days.

I like the idea of starting out with Ldap given it’s powerful adaptability and scale.

Any ideas or pointers? Could I interest you in taking the plunge with an additional tutorial that covers some thing like this – i.e. running on Sarge.

thanks again.