similar to: Postfix and Dovecot SASL - wiki update

Disabling chroot doesn't fix the issue, it just worked around it. Aparently your chroot is not configured correctly, likely using debian based system, and your resolv.conf in the chroot is not updated correctly. Quoting Dan Langille <dan at langille.org>: > I wanted to mention I updated the Postfix and Dovecot SASL wiki > entry yesterday. > >

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

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:

I tried searching this list, but couldn't find anything related to inode limits except for linux quotas. I wanted to add sieve support for our users, so was attempting to get our email system to use dovecot's deliver lda to handle email, instead of postfix's virtual lda, using maildir mailstore. When I did this, I noticed that emails would get stuck in the queue if a user was

> I would love to know why your ubuntu 14.04 system doesn't support sha512-crypt. I just tried SHA512-CRYPT and it is supported on Ubuntu 14.04. I think I was thinking about DBMail instead of Dovecot. I could really use support for BLF-CRYPT since my current password hashes generated by PHP are using Blowfish encryption. Maybe, Dovecot could just add support for BLF-CRYPT by using the

Hi guys, I setup a new box with Debian Squeeze 64bit and installed dovecot from the sources. However, I can't start dovecot or even use doveconf: root at imap01:~# doveconf -n # 2.0.13: /usr/local/etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/conf.d/10-mail.conf line 111: Unknown setting: mail_uid Why is mail_uid and mail_gid an unknown

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

>> Maybe, Dovecot could just add support for BLF-CRYPT by using the open source implementation of Blowfish hashing found in https://github.com/php/php-src/tree/master/ext/standard <https://github.com/php/php-src/tree/master/ext/standard>. The implementation looks like a single function to generate the hash. I?m not much of a programmer, but it would seem to me that these .c/.h files

Hi, Peter Chiochetti <pch at myzel.net> (Di 31 Mai 2016 10:31:50 CEST): > Not having installed any of the two, I can say, as a Ubuntu user: > In ppa "/etc/init.d/dovecot" is a symlink to "/lib/init/upstart-job" The 2.2.24 on 16.04 installs both /etc/init.d/dovecot /lib/systemd/system/dovecot.service > While xi packages places its own init script

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

Dear All, I've installed Postfix 2.7.0 and Dovecot 1.2.9 on Ubuntu 10.04. I want to use Dovecot SASL with Postfix and did the following configuration. main.cf smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/dovecot-auth smtpd_sasl_authenticated_header = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = $myhostname

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:

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

I have had the same email address since 1997 (when microsoft stole bob.com from me thanks to network solutions...) In the early days I of course was free with my email and used it everwhere. Fast forward to 2012, some 15 years later. woof..the amount of spam sent to me has always just kept getting worse and worse. On my centos 5 server I just used sendmail with spamassassin and it killed 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

Hello, I'm trying to configure postfix + Dovecot SASL for user authenticated mail relay. I set following configuration on postfix queue_directory = /var/spool/postfix smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_authenticated_header = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = $myhostname

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

On Mon, Nov 18, 2024, at 7:35 PM, Dan Langille via Nut-upsuser wrote: > On Tue, Nov 12, 2024, at 11:49 PM, Harlan Stenn wrote: > > I just started shopping for my replacements: > >> I like batteries from RaionGroup.com or batterywholesale.com. > > Here is some free coincidental trivia. > > I was a sysadmin for the server behind batterywholesale.com for about > 10

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