similar to: Postfix SASL AUTH from Dovecot

Hi Is it possible to secure the Dovecot SASL auth provider for postfix? https://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL I'm currently using the inet option to provide SASL auth to postfix for dovecot. Both installs are on different hosts hence the use of inet rather than unix socket. I'm looking for the best way to secure this channel (rather than just assuming the VLAN is secure

Hello, i use Postfix (2.7.1) and Dovecot (1.2.14) on my FreeBSD Server. I use Postfixadmin and Virtuell User. The login going without problems, but the SASL Auth want not work. Have someone a Idea? Regards Silvio #postconf -a dovecot # postconf -n alias_maps = hash:/etc/aliases allow_percent_hack = no biff = no command_directory = /usr/sbin config_directory = /etc/postfix content_filter =

On 27/09/17 20:35, Thomas Bauer wrote: > service auth { > inet_listener{ > address=192.0.0.1 > port=10001 > ssl=yes > } > } ssl=yes is not documented to work for the auth service and it's highly likely that it is simply ignored. > -o smtpd_tls_security_level=encrypt This definitely does not do what you think it does. This setting is for the smtpd

Dear all, Would need some of your advise. As I was the trying to get postfix sasl working with samba AD. I've try to search online for a few examples some use ldap, kerberos or pam. I'm using winbind on that system and I wonder if we can use winbind with sasl. Or anyone have a more correct on how it should be done. My existing setup was working with ldap before moving to samba4.

I'm trying to use Dovecot SASL with postfix 2.3.3 and when trying to send mail I get the debug output below. I don't know enough about whats going on to know where the problem is but something clearly is not right. I would send the configurations for postfix and dovecot except they are clearly talking to each other so I kinda doubt its a configuration issue. The machine can afford to be

i have these errors on my postfix logs. ive just installed postfix+sasl.what seems to be the problem ? mail postfix/smtpd[26307]: auxpropfunc error no mechanism available Feb 1 17:37:27 mail postfix/smtpd[26333]: sql_select option missing --------------------------------- Do you Yahoo!? With a free 1 GB, there's more in store with Yahoo! Mail. -------------- next part

ear All, I configured Postfix 2.3.3-2 on CentOS 5.2 using SASL Dovecot authentication put I am facing the problem to receive mails . My postconf -n result is: [root at mails ~]# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2

I wanted to mention I updated the Postfix and Dovecot SASL wiki entry yesterday. http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL The entry: submission inet n - - - - smtpd was incorrect. It should be: submission inet n - n - - smtpd By specifying n for chroot, it ensures that DNS lookups can occur. Otherwise, if you are using reject_unknown_recipient_domain the following error will

I'm trying to configure my postfix server to use Dovecot as an SASL server and running into some problems. My server supports a couple of domain, I have multiple user/password files for multiple domains to make the files a little easier to manage. Not sure if this question should belong in the dovecot mailing list or the postfix one, but here goes anyway. I have everything configured to use

Hi, I'm relatively new to Dovecot and I did a bit of search but couldn't find a possible solution for the particular setup I'm working on. Basically I have an SMTP/POP/IMAP proxy setup running Postfix & Dovecot. IMAP/POP authentication is done using the password proxy feature, where the login credentials are passed to the backend server after a db lookup, which does the actual

Gedalya skrev den 2015-03-27 14:48: >> is it possible to configure configure haproxy to work with postfix >> sasl and dovecot auth like this: >> clients -> 25:postfix -> 20025:haproxy -> 20025:auth-backend-1, >> 20025:auth-backend-2 > Why don't you set up a dovecot locally (with only auth service) on > each postfix box? cyrus-sasl is still needed, and

I will install cyrus-sasl and see how it goes. Anyway, it would be nice to have same features (authentication agains imap) in dovecot. On 27 Mar 2015, at 16:27, Benny Pedersen <me at junc.eu> wrote: > Edgaras Luko?evi?ius skrev den 2015-03-27 14:58: > >> I don?t want to allow public network facing servers to be able to >> reach passwords database. And I want to

Hi. I'm trying to get Dovecot - Postfix - SASL to work. But I need some help. Dovecot v1.0.rc14 Postfix 2.3.4 dovecot.conf ---------------- auth default { mechanisms = plain login passdb pam { } passdb passwd { } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } postfix/main.cf

Hello, is it possible to configure configure haproxy to work with postfix sasl and dovecot auth like this: clients -> 25:postfix -> 20025:haproxy -> 20025:auth-backend-1, 20025:auth-backend-2 The configuration I have now gives me this error randomly: 535 5.7.8 Error: authentication failed: Connection lost to authentication server This is probably because haproxy change servers while

I have mail server on CentOS 4.1. Sasl authorization for SMTP is enabled. Thunderbird sends mail, but Outlook get an error 554, Relay access denied, error number 0x800CCC79 Outlook has a login and password for SMTP enabled. It is strange, because there is no any sign of authorize in maillog when Outlook try to send mail. -- ____________________________________________________________________ D

Can?t dovecot authenticate against imap? What I need is to make smtp authentication balanced and keep everything in backend (private network) On 27 Mar 2015, at 13:29, Benny Pedersen <me at junc.eu> wrote: > Edgaras Luko?evi?ius skrev den 2015-03-27 12:21: > >> is it possible to configure configure haproxy to work with postfix >> sasl and dovecot auth like this:

Hi, I just moved from Cyrus SASL to Dovecot SASL, with postfix. Works great, and no issue with non-ascii chars, has i had with Cyrus. With Cyrus i was getting the username/passwd via SQL, with this: sql_select: select password from smtp_auth_users where username='%u@%r' and status='true' worked ok for users with email addresses, and i had some special users that were just a

I don?t want to allow public network facing servers to be able to reach passwords database. And I want to segregate roles of the servers. If I will setup dovecot locally I will still have to provide it access to database (eg. /etc/dovecot/dovecot-sql.conf.ext). On 27 Mar 2015, at 15:49, Benny Pedersen <me at junc.eu> wrote: > Edgaras Luko?evi?ius skrev den 2015-03-27 14:34: >>

On 2019-11-14 15:41, Benny Pedersen via dovecot wrote: > Jorge Bastos via dovecot skrev den 2019-11-14 16:25: > >> I've tried to search for the realm part in dovecot but didn't found it, >> Could you guide me to it? > > doveconf -d | grep realm > > doveconf -n if more help is needed Thanks Benny, It was in my front and didn't saw it. Now i need to

I have followed the Dovecot/Postfix/SASL howto, and modified the main.cf and dovecot.conf files, yet when trying to authenticate during a postfix SMTP session the log reports: "postfix/smtpd....warning: SASL authentication failure: Could not open db" Dovecot itself is authenticating IMAP logins correctly, and it is creating the auth file in the location specified under