similar to: Postfix + dovecot-auth

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

Are you a cyrus developer ir what? :D 2015 kov. 27 17:10 "Benny Pedersen" <me at junc.eu> ra??: > Edgaras Luko?evi?ius skrev den 2015-03-27 16:00: > >> I will install cyrus-sasl and see how it goes. >> > > +1 > > Anyway, it would be nice to have same features (authentication agains >> imap) in dovecot. >> > > read more docs in

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

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

Edgaras Luko?evi?ius skrev den 2015-03-27 14:34: > Can?t dovecot authenticate against imap? will it be trusted ? > What I need is to make smtp authentication balanced and keep > everything in backend (private network) dovecot is not a smtp server, thats why i say cyrus-sasl yes cyrus-sasl is ha-awail with rimap, but there is a minor problem with it, haproxy and rimap have both the

Edgaras Luko?evi?ius skrev den 2015-03-27 16:00: > I will install cyrus-sasl and see how it goes. +1 > Anyway, it would be nice to have same features (authentication agains > imap) in dovecot. read more docs in cyrus-sasl, did i say rimap ? :=)

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

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:

Jorge Bastos via dovecot skrev den 2019-11-13 22:00: > How can i have the same with dovecot SASL? > Thanks in advanced, https://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL Hi benny, Thanks, That's exactly what i have in postfix: smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes plus: smtpd_sasl_local_domain = fastmail but the user that i have

Hi, I am trying to create an authenticated relay server using Postfix and Dovecot. However I am having two problems : (a) If I create a dovecot config entry as follows : unix_listener /var/spool/postfix-authrelay/private/dovecot-auth { group = postfix mode = 0666 user = postfix } Dovecot is unable to create the socket ? I thought surely if dovecot is started as root it should

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

Hi List, I just updated an old sendmail installation to a modern postfix/dovecot system with mysql backend. Everything works fine but SMTP-AUTH fails with some clients. The problem is, that with PLAIN (old) clients send the base64 coded form: USERNAME\0USERNAME\0PASSWORD which, as i understand dovecot interprets as MASTERUSER\0USERNAME\PASSWORD. New clients send \0USERNAME\0PASSWORD which works

Again today got annoyed at Cyrus SASL. Upgrading it to newer version had broken PAM support. Trying to login as "user at domain" resulted it only asking for "user" from PAM. Well, got it patched and working again, but I'd rather not go through it all the time.. So I finally did what I had been thinking about a year or so, change Postfix to use dovecot-auth directly. This

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: > > clients -> 25:postfix -> 20025:haproxy -> 20025:auth-backend-1, > 20025:auth-backend-2 configure cyrus-sasl as a remote imap client is more simple if imap hostname is dns round robin it would be ha-avail already

Hi, Am 27.09.2017 um 01:07 schrieb Raymond Sellars: > Is it possible to secure the Dovecot SASL auth provider for postfix? > I'm using this configuration, which you've suggested. > Has anyone managed to implement a secure internal approach they can share? I'm wondering if Postfix with Cyrus against IMAP using STARTTLS is my best alternative. > My config is: On the

Any suggestions to help me troubleshoot a "killed by signal 11" problem with Postfix? I've Googled and fiddled, but cannot figure it out. I have no idea where to look/start. Based on this post, Wietse suggests this type of problem happens when there compiled with different libraries. I tried ldd on various programs and found they all seemed to line up, but I know little.

How to get postfix working on CentOS 6 and Comcast. Recently, they've changed their policies regards email relay and require authentication even to send email. (they no longer use IP address ranges, presumably in an attempt to curb outgoing SPAM) I didn't see an updated howto anywhere on the Interwebs, thought I'd point out what I had to do. The part that had me stumped for longer

Hi Benny, I've tried to search for the realm part in dovecot but didn't found it, Could you guide me to it? -----Original Message----- From: dovecot <dovecot-bounces at dovecot.org> On Behalf Of Benny Pedersen via dovecot Sent: 13 de novembro de 2019 23:33 To: dovecot at dovecot.org Subject: Re: SASL AUTH with postfix Jorge Bastos via dovecot skrev den 2019-11-13 23:53: > Jorge

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 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). did you read cyrus-sasl docs ? it can read auth from sql, so

Tere. Recently just migrated from Sendmail 8.14.3 to Postfix 2.5.6 and switched from Cyrus-sasl 2.1.22 to Dovecot 1.1.13 sasl, all are compiled from source and I have used Dovecot for a long time, since alpha versions. Everything worked well for Outlook Express, Outlook and Thunderbird clients, but Microsoft Entourage 2004 or 2008 clients smtps fails - "Authentication failed because