search for: rimap

Will Dovecot support the Cyrus SASL library rimap mechanism? If so, is there anything I need to enable/verify for it to work? And is there another tool to verify proper behaviour besides trying to log in with a client? Daniel

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:

...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 same problem to connect to one ip that times out before the next ip is used, haproxy does imho not solve this better then rimap

...ecot 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 same problem to connect to one ip that times out before the next ip is used, haproxy does imho not solve this better then rimap

i've upgraded dovecot on my server to 2.3.9 works properly but saslauthd that uses it for rimap authentication over 127.0.0.1 works SLOW. You need to wait 15-20 seconds before authentication. only imap login over 127.0.0.1 is slowed down, while over any other IP is quick. i had this problem with older version of dovecot but it was about adding login_trusted_networks = 127.0.0.1 but i al...

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

Am 24.03.2019 um 10:01 schrieb Wojciech Puchar via dovecot: > solved by setting saslauthd to authenticate over imap - through dovecot > server. > testsaslauthd shows it works fine. > > but it seems sendmail strips domain name from entered login. No, it is saslauthd. Check the documention and see the "-r" parameter of saslauthd. Alexander

...proxy is still not supported as discussed in these threads (especially the first one)? http://www.dovecot.org/list/dovecot/2012-August/067977.html http://www.dovecot.org/list/dovecot/2011-May/059107.html As I understand it is possible to use saslauthd to do this by using the remote imap option (rimap). Such a facility is important since I am attempting to separate the outward facing servers (dovecot proxy, postfix relay) that have no knowledge of user databases from the backends. thanx Andreas

Hi, I am using SMTP-AUTH over TLS with sendmail, to allow remote users to authenticate and send mail via my server, and this uses saslauthd to authenticate users. I have set up saslauthd with the "MECH=rimap" mechanism, so it uses the local IMAP server, Dovecot, for authentication. I want to do this because Dovecot is set up to use /etc/passwd for user credentials (so I don't have multiple password files to manage), and Dovecot handles restricting the range of valid UIDs (including blockin...

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.

Hi. Apologies to the list for sending this twice as I forgot to enter a proper subject line, I wanted to write the content first and then make up the subject line ;-) -------------------------------------------------------------------- I am trying to configure sendmail that is looks up the users credentials to allow them to send email via that server via an imap server on the same machine

...but I'm hoping maybe someone will see the easy answer. I have in /etc/pam.d/smtp #%PAM-1.0 auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth Also: # saslauthd -v saslauthd 2.1.19 authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap And /usr/lib/sasl2/smtpd.conf (also linked to sample.conf) # cat smtpd.conf loglevel: 7 pwcheck_method: saslauthd mech_list: PLAIN LOGIN Here are the results of a failed attempt: ------------------------------------- # saslauthd -m /var/run/saslauthd -a pam -d saslauthd[3176] :main...

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 ? :=)

...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 ? :=) >

...ogin. > > No, it is saslauthd. Check the documention and see the "-r" parameter of > saslauthd. found it a minute before reading this e-mail. thank you works fine. almost ;) Why authenticating over imap takes so slow? my saslauthd runs like that /usr/local/sbin/saslauthd -a rimap -O 127.0.0.1 -n 0 -r imap server is handled by dovecot of course. to be sure it's not sendmail i've tried testsaslauthd testsaslauthd -u wojtek at puchar.net -p mypassword works but takes 5-10 seconds. server is lightly loaded. telnet 127.0.0.1 imap responds instantly. what to check?

> Why authenticating over imap takes so slow? > > my saslauthd runs like that > > /usr/local/sbin/saslauthd -a rimap -O 127.0.0.1 -n 0 -r > > imap server is handled by dovecot of course. > > to be sure it's not sendmail i've tried testsaslauthd > > testsaslauthd -u wojtek at puchar.net -p mypassword > > works but takes 5-10 seconds. server is lightly loaded. > > telnet 127.0...

* Wojciech Puchar, 16.12.19 15:54 > i've upgraded dovecot on my server to 2.3.9 > > works properly but saslauthd that uses it for rimap authentication over 127.0.0.1 works SLOW. You need to wait 15-20 seconds before authentication. > > only imap login over 127.0.0.1 is slowed down, while over any other IP is quick. > > i had this problem with older version of dovecot but it was about adding > login_trusted_networks...

Hi, i'm trying to configure my postfix to use dovecot SASL instead of saslauthd with rimap to authenticate my users. I've modified my postfix/dovecot configuration as is described on http://wiki.dovecot.org/PostfixAndDovecotSASL but when an user try to login it fails with the following log (debug_auth = on): Dec 12 15:07:53 lorien dovecot: auth(default): client in: AUTH^I1^IPLAIN^I...

Hi all, isn't it possible to use the director functionality for smtp-auth too? I have a frontend system for imap and outgoing mails using sasl and I recognized that all sasl username/password combinations are accepted as these credentials aren't checked by the backend servers. Regards Patrick

Just wondering - is there any way for a dovecot server to authenticate against a different IMAP server? Here's what I'm thinking. I run a spam filtering service and thinking about a way to give users access to their stored spam on my servers. However real email is forwarded to their server, So I'm wondering if I can configure dovecot somehow to do a back end authentication to