Tag Info

New answers tagged

1

You can exclude xxx@xxx.com to using relayhost by setting empty relay host in transport_maps #main.cf transport_maps = hash:/etc/postfix/transport #/etc/postfix/transport xxx@xxx.com smtp:


1

Basically if you want to do SASL authentication via MySQL you have 3 options Using pam-mysql and saslauthd. Your linked tutorial use this. Using sql auxprop plugin. In /etc/postfix/sasl/smtpd.conf file above, you have defined this method. Using dovecot instead cyrus SASL (option 1 and 2). Let's dovecot provide the auth socket for you. You states that you ...


0

You could also try to add postfix user to sasl group.


2

Sorry for misleading comment above. When you use sasldb, then you doesn't need saslauthd running. So you can safely remove it from startup script. You should run saslauthd when you do password checking via system user, LDAP or remote IMAP. The first step is creating a database for sasldb using saslpasswd2 binary # saslpasswd2 -c username@example.com ...


3

As you can see, there's no smtpd_sasl_path in our output of postconf -n Why? The answer is easy. Because there's no smtpd_sasl_path set. Have a look at your first snippet: There's a typo in it. You wrote smptd_sasl_path = private/auth -- but there's a difference between smtpd and smptd. Because Postfix doesn't have informations where to find the socket, ...


1

In the tutorial linked above, the author using CRYPT hash algorithm. This fact can be looked in SQL query: INSERT INTO `user` (`email`, `password`, `name`) VALUES ("admin@example.com", ENCRYPT("adminpassword"), "Administrator"); Saslauthd using pam-mysql to authenticate user, so we need to configure pam-mysql to use same hash algorithm. The configuration ...


0

I had the exact same issue and in the end found out it was because I had set sasl-host in slapd.conf to be the kerberos server hostname. When I changed sasl-host to be ldap hostname (e.g. sasl-host ldap.example.com) it worked correctly.


1

It's simply a clean way of overriding main.cf since usually smtpd_client_restrictions in main.cf isn't used, which is the same as saying by default it is set to smtpd_client_restrictions = permit. You could achieve the same result by overriding smtpd_recipient_restrictions as you say in your question, in which case you wouldn't need the ...


0

Well it seams that the only problem was that I didn't have package cyrus-sasl-plain installed on the new server. After restarting all services (saslauthd and sendmail) and also the mail client sending and authenticating worked fine.


1

Your sendmail.mc looks ok. Apart from stopping and starting sendmail again (which I would guess you have already done). I would look at the actual configuration file which would be called sendmail.cf. Make sure you see the lines: C{TrustAuthMech}DIGEST-MD5 CRAM-MD5 LOGIN PLAIN and # list of authentication mechanisms O AuthMechanisms=DIGEST-MD5 ...



Top 50 recent answers are included