similar to: Securing postfix to dovecot (SASL) auth

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

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

I have been fighting with this for almost 2 days. I can't seem to get the SMTP server to authenticate through SASL. I have turned so many things off and on, I don't remember what I've done, anymore. Can someone look at these and tell me what I'm missing. I get this in the log, anytime postfix tries to authenticate. Sep 24 19:48:14 ubuntu postfix/smtpd[14464]: warning: SASL:

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

Hi, I'm trying to configure a new server with dovecot 2.0 and postfix 2.6.6. My previous servers have all been dovecot 1.x. Trying to port over my previous configurations has been a real headache. Currently, I'm getting the following errors when trying to connect with: openssl s_client -starttls smtp -connect localhost:25 Aug 21 19:08:46 localhost postfix/smtpd[26252]: connect from

One of my accounts was having login failures when trying to send mail, but was able to check mail. I tried everything I could think of to see what the issue might be, but eventually went in and reset the password in the sql database (I knew the password, so I reset it to the same password). {SHA256-CRYPT}$5$VuS? {SHA256-CRYPT}$5$VI7? So the password was updated properly. Clients can still

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

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

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

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

I'm using postfix smtpd / dovecot. Running imaps, imap, pop3s, pop3. I have a ssl certificate setup. Everything works fine via IMAP except sending to an email from outside the network to a recipient outside the network. The problem is when someone (and this is being tested thru the iphone email client configured to use imap) logs in, they can read messages but cannot send to an address

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, I have a freshly setup postfix/dovecot mail server (after a server upgrade I decided to change my sendmail/popper conf to something more modern :) It mostly works, there is no problem in sending/receiving mails in local network, both using text clients like mutt or pine dealing with the incoming/outcoming mail directly. Also dovecot works fine with SSL authentication from the outside

Linux caloro.ch 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux Apt-get install postfix dovecot Adduser -m maurizio Add config steps to dovecot.conf, main.cf, master.cf Email from CLI running, but if connect from Outlook or Thunderbird I have this error, I think that maurizio this user aren?t opened correct on this sqldb? root at caloro:/home/maurizio# postconf -n

Hi; I continue to be plagued with this error: Oct 25 10:49:18 myserver postfix/pipe[3712]: 0423257901AB: to=<foo at bar.com>, relay=dovecot, delay=109318, delays=109318/0.14/0/0.1, dsn=4.3.0, status=deferred (temporary failure It's been a week that I've been working day and night to get this fixed. I forgot to add this information: [root]# doveconf -n auth_mechanisms = plain

Hi Buddies, I have 2 servers running dovecot + postfix for pop/imap users. The users mailbox are in a Nfs storage. The load of server is ranging at 3.0 to 15.0. I really dont know what happened.. I read a lot about tuning of dovecot, and the changes are applied, how you can see. The Hardware of server is really good! The host have 8GB of mem and 2 sockets with 2 cores anyone. The server receives

> That's a permission error. Somewhere in your directory hierarchy things > are off. See Postfix' set-permissions command. > But surely if Dovecot is staring as root then directory permissions are relevant, especially if I'm then asking the config to chmod the file anway ? To me, it seems dovecot is not behaving correctly, because if it is not using root to access the

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

On 27.09.2017 13:21, Peter wrote: > 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. It is documented for inet_listener's in general