Hot answers tagged

9

Ah-ha! Installing the libsasl2-modules package solved the problem.


9

The giveaway is here: -- active services in /etc/postfix/master.cf -- # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) smtp inet n - - - - smtpd submission inet n - - - - smtpd The smtpd process on the submission ...


8

You can have saslauthd installed but not have any mechanisms installed. It's quite frustrating and poor error-proofing, IMO. "no applicable SASL mechanisms" literally means it can't find any of its mechanisms. On a Fedora-based system you'd need to install the cyrus-sasl-plain package if you want to use the 'PLAIN' auth mechanisms (i.e. SMTP/STARTTLS). ...


7

Postfix can run in a chroot (by default in /var/spool/postfix) or not. If it is, it will try to open /var/spool/postfix/var/run/saslauthd/mux for sasl authentication. If it's not, it will try to open /var/run/saslauthd/mux It seems that, for some reason, your postfix instance was running in a chroot, and it's not anymore. It's odd, but that's what I guess ...


7

you have smtpd_recipient_restrictions twice, and the last one is the one being used and it does not have permit_sasl_authenticated


6

Define another failregex (?i): warning: [-._\w]+\[<HOST>\]: SASL (?:LOGIN|PLAIN|(?:CRAM|DIGEST)-MD5) authentication failed(:.*)$ I tested this regex with fail2ban-regex and is working.


6

You probably just need to add -r to your saslauthd OPTIONS= stanza. From the man pages -r Combine the realm with the login (with an ’@’ sign in between). e.g. login: "foo" realm: "bar" will get passed as login: "foo@bar". Note that the realm will still be passed, which may lead to unexpected behavior.


6

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, ...


6

This feature was available to postfix version 2.11. You can use check_sasl_access parameter to enforce restrictions based on SASL username. Of course you need to put it above permit_sasl_authenticated. Please refer to man 5 postconf for complete documentation. Example configuration, taken from Postfix SASL Howto # main.cf smtpd_relay_restrictions = ...


5

buggy for configuring virtual mailboxes with Maildir protocol I'm using Dovecot LMTP for delivery to Maildir boxes and don't have any problems. I'd like to provide SMTP authentication access introducing SASL with dovecot as IMAP server The easier way is to authenticate SMTP users through Dovecot, so you don't need to configure SASL authentication ...


5

postconf -a and postconf -A tell you what sasl plugin types are available. I would assume those would return errors or empty lists if sasl support was not enabled at build time (though possibly not). You could also check the output of ldd /path/to/postfix and see if it links to a sasl library or not (though it might be possible for postfix to be built with ...


5

Postfix currently supports only two SASL authentication methods. One of the is Dovecot, which you don't want. The other is Cyrus, which is about as close to what you want as it's possible to get without rewriting Postfix. It does involve running a separate authentication daemon (saslauthd), but the authentication file is easy to edit and update. The basics ...


5

You could change the reject_code for your submission listener to 450, so it is not a permanent reject but a defer. check_sender_auth = defer_if_reject reject_authenticated_sender_login_mismatch, permit_sasl_authenticated, reject See http://www.postfix.org/postconf.5.html#defer_if_reject for details. Unfortunately, this is not simple to ...


5

We were able to trace the username by using Dovecot itself. In the config we enabled verbose auth logging using auth_verbose = yes This put the information in /etc/dovecot/info.log


4

auxprop can't deal with encrypted passwords, you should use PAM authentication mechanism and pam_mysql plugin.


4

postfix can be configured to use dovecot for SASL authentication, so you might be better off starting the other way around and figuring out if you can get Dovecot to process these hashes. Keep in mind that hashes are designed not to be "decrypted". When someone wants to log in, the application takes the original salt, the password the user provides and ...


4

The SASL authenticators are only included in exim4-daemon-heavy, including the Dovecot SASL authenticator. More information on that here.


4

yes it is possible. I guess you are using libpam-mysql. There is an option you can set named crypt. auth optional pam_mysql.so user=username passwd=password verbose=0 db=thedb table=user usercolumn=userName passwdcolumn=userPassword crypt=3 account required pam_mysql.so user=username passwd=password verbose=0 db=thedb table=user ...


4

SASL stands for Simple Authentication and Security Layer; it's a framework that allows developers to implement different authentication mechanisms, and allows clients and servers to negotiate a mutually acceptable mechanism for each connection (rather than hard-coding or pre-configuring them). GSSAPI stands for Generic Security Services Application Program ...


4

It's clear to me that the password from mail@xxxxxx.tld has been stolen and someone authenticated on your postfix using this account and password. You could limit the number of messages sent from an user using the anvil process from postfix, as example: smtpd_client_message_rate_limit=100 With this option in main.cf you can limit 100 messages/per client ...


4

Had the same problems like above only on debian squeeze after a dist-upgrade. After hours of config, restart and reinstalling madness I gave following "svn.conf" a try: pwcheck_method: saslauthd #auxprop_plugin: ldap mech_list: plain login cram-md5 digest-md5 IMO, "mech_list: plain" should be enough. the other mechs are overlefts from previous tryouts. ...


4

Well, from what I see in your posted configuration you never set Dovecot's auth_mechanisms = plain login, thus the default of auth_mechanisms = plain is used. Try updating that setting and restarting Dovecot, afterwards re-check the output of doveconf -n. Your auth socket settings seem correct to me, Postfix should be able to do SASL authentication against ...


3

SASL Authentication Check List Base on question and comments, sasl may not be setup correctly. Following check list is created base on Ubunut Guide provided in question. Check file/etc/postfix/sasl/smtpd.conf, should be like following pwcheck_method: saslauthd mech_list: plain login Check libsasl installed dpkg -l | grep sasl Should have the ...


3

Your email client didn't actually authenticate. Are you sure you have correctly configured Outlook to connect to port 587 and given it a username and password?


3

Looks like postfix always looks in the chroot'ed location for saslauthd even though its configured to NOT use the chroot environment for its services. I found this blog post most helpful, even though it's from 2005! http://www.jimmy.co.at/weblog/?p=52 postfix does a chroot so it can’t communicate with saslauthd. This is the tricky part: rm -r ...


3

Postfix restriction classes can return three answers, OK, REJECT or DUNNO, usually they have (OK, DUNNO) or (REJECT, DUNNO), because of the way that postfix functions. DENY and OK mean the rest of the checks are ignored, DUNNO means go on to the next check. So, in your case, permit_mynetworks or permit_sasl_authenticated are returning OK, so it does not ...


3

in master.cf I uncomment smtps inet n - n - - smtpd -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING on iptables allow port 465 and now is function Postfix over SSL is not using port 25?


3

Your server is not an open relay. It is set up to allow three different types of mail: Mail from anybody on the internet to addresses within your own domain Mail that originates on your own mailserver (e.g. notices from cron jobs and the like), to anybody on the internet Mail that comes from an authenticated connection to anybody on the internet If the ...


3

the solution was very simple, the SASL daemon was down. /etc/init.d/saslauthd start Some hacker managed to shut it down again and again so eventually I had closed it completely.


3

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 ...



Only top voted, non community-wiki answers of a minimum length are eligible