similar to: Yet another going from 1.2 to 2.X question: authentication

At my company we've had a longstanding problem of not being able to send email from devices outside of our internal network and any specific IP address that we open the relay to. As it turns out, SASL has never been set up. I need to set up SASL ASAP but none of the guides I've found seem to work. This is the latest guide I tried: http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL I

On Wed, 9 Jan 2019 at 13:09, Jacky <jacky at jesstech.com> wrote: > Hi Gerald, > > in my postfix/main.cf > > smtpd_sasl_authenticated_header = yes > smtpd_sasl_security_options = noanonymous > smtpd_sasl_local_domain = $myhostname > smtpd_sasl_type = dovecot > smtpd_sasl_path = /var/run/dovecot/auth-client > broken_sasl_auth_clients = yes > > I am already

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 =

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

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, Just found out that Postfix does not implement/support the AUTH=sender parameter. So, back to Dovecot, can we use variables in the submission_relay_user = submission_relay_password = then Dovecot will forward the username and password information of the current user to the Postfix submission service for authentication? Best regards, Jacky On 10/1/2019 10:46 AM, Jacky wrote: >

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

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

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

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

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

I do not know if this is a help request to solve a problem but to understand what is going on. I am going to start with the problem description as I see it and we will go from there. I have postfix setup to use dovecot for tls/sasl in addition to its normal imap/pop3 functions. Postfix is also setup to do virtual domains, getting its information from the files valias, vmaps, and vhosts which are

Hi all, I seem to recall mention of SASL client support either being added, but can't remember for sure. The wiki says nothing about Client support (now, or in the future)... http://wiki2.dovecot.org/Sasl So - is there support for it now? If not, is it planned for anytime soon? Thanks, -- Best regards, Charles

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

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

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

I've tried to setup Postfix to use SASL, but it still doesn't seem to be working with Dovecot. I've set things up based on these instructions: http://wiki.dovecot.org/HowTo/SimpleVirtualInstall http://wiki.dovecot.org/HowTo/PostfixAndDovecotSASL http://wiki.dovecot.org/LDA I've compiled Postfix with Dovecot SASL and SSL/TLS support. The problems I'm seeing in Postfix are: