similar to: Dovecot SASL Client support?

Hello Folks, I've been the admin of a site that uses Postfix with Dovecot on RedHat since, oh, gosh, maybe 1996? It's been a long time. I've never built it from source, though, just used the rpms (and I wonder if maybe that's my problem now). It just works, is reliable, and lets me be a very-part-time administrator. Repeatedly over the last few years I've been asked to have

Greetings all, I have a OpenBSD /Dovecot server at home running and sending / receiving email "internally" without issue.. Recently, I set up the same at our Parish, but one of our users wants to get their email externally. The user can read their email but has to "send" via the local ISP server.. The problem After much searching I have not found an answer to my question. I

Howdy, I know i've asked this before, but i think i got really no answer. I'd like to have dovecot SASL, to check AUTH against an SQL table, instead of dovecot SASL use the AUTH MECH for imap/pop3. I want this, to have the same behavior as I have now, where i use postfix with cyrus SASL on a different table (with the same login details), and when i have an user that his accounts

Hi, I am currently using Dovecot 1.0.rc17 with Postfix 2.3.8 on Ubuntu. So far I'm able to receive my email using dovecot pop3 but I can't send out the email. Anybody managed to get Postfix with Dovecot SASL support so far? What do I missed out? Below is my configure: #-----------/dovecot.conf-------------- base_dir: /var/run/dovecot/ log_timestamp: .%Y-%m-%d %H:%M:%S . protocols: imap

Hi Jacky, in postfix/main.cf you typically set something like smtpd_sasl_auth_enable=yes smtpd_sasl_type=cyrus smtpd_sasl_exceptions_networks=$mynetworks smtpd_sasl_security_options=noanonymous smtpd_sasl_authenticated_header=yes broken_sasl_auth_clients=yes smtpd_recipient_restrictions=permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination smtpd_recipient_restrictions might

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

Hi all, Apologies for the somewhat off-topic questions - I'm trying to get my head around SASL, and what it is/does. I can see that a (SMTP, IMAP etc) server can offer various authentication methods, which are pre-defined and which the client can choose from. SASL then seems to define how those work. But dovecot and cyrus-sasl both seem to offer a client-server interface, usable by eg

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

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'm trying to set up SMTP authentication on my server and am getting an authentication failed error. My client is set up to automatically select authentication method and tries CRAM_MD5. The http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL suggests "passdb pam" and "userdb passwd" -- is it possible to configure sasl authentication using a dovecot.conf like

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

hi everyone could someone show me there sasl configuration section in their dovecot.conf, i have postfix and dovecot setup for virtual users (no system users) everything works fine including tls, i have tried various examples off the web for sasl but they either have obsolete parameters or are for a setup with system users, i would prefer to use dovecots sasl implementation. dovecot --version =

Hello all, I am struggeling to get my Dovecot SASL to work within postfix. I have used the configuration example listed on the main-site of dovecot and it basically isn't giving me any success at all. I am probably missing something easy, but after spending a few days testing and walking through everything I could think about I thought figured it was better to ask :) Hope someone can point me

Hi, I am trying to configure dovecot/postfix with virtual users and sasl auth but there are so many tutorials with mistakes and subtle differences that at the end I am lost. So I am running Ubuntu server 11.04 (natty) and when I installed my server I had followed the following guide http://workaround.org/ispmail/etch Then I have migrated to dovecot 2.1 and now I am trying to allow

I'm trying to figure out if this is a bug... I'm running Postfix with Dovecot Authentication and have Amavisd-new as the front end. I fought with the install and in particular being able to send mail.... Auth failed. Hours of looking through all the config files yielded nothing... so I started Googling about. I finally found a comment at the bottom of a blog to check permissions on:

Hi, I'm testing dovecot 2.1.0, on Debian 6.0, with "passdb driver = imap" and SASL for postfix's SMTP-Auth, like explained ih this howto: http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL Authentications over IMAP (local dovecot -> remote dovecot) works fine, and it's great. Also smtp-auth on postfix (over SASL) works fine. But in the dovecot log I found this

Dear friends, I try configure a webmail on my server using Postfix + Dovecot + MySQL + Squirrelmail. My system is a Debian6 and dovecot version is: #dovecot --version 1.2.15 But, when I try to access an account on squirrel I recieve this message: ?ERROR Error connecting to IMAP server: localhost. 111 : Connection refused? Looking for a problem I foud this: #service dovecot start

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:

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