similar to: List problems?

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

On 2014-01-08 14:32, Charles Marcus wrote: > On 2012-04-09 8:53 AM, Timo Sirainen <tss at iki.fi> wrote: >> On 9.4.2012, at 15.50, Charles Marcus wrote: >>>> LMTP adds a new Delivered-To:<rcpt-to at address> header when there is >>>> a single RCPT TO. You can force a single RCPT TO from Postfix side by >>>> setting

message sent from the sieve-vacation does not contain dkim signature how to configure sieve to send messages via smtp transport with signing?

We're using the SQLite backend for authentication of Postfix SASL. When the db is replaced we HUP dovecot to close and reopen its connection. During this time it appears the socket file is removed and Postfix rejects the authentication attempt. From the logs: Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading configuration Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning:

I just install Dovecot and postfix. When I'm pull dovecot I see in the log that its checking for mail. if a put a test message locally on the server I can pull the message down to my cell phone and other computers. But when I try to a message from gmail or aol it doesn't come in to the server. it always bounces back to the place were I sent it from

I am trying to do authentication with /etc/passwd and something is not working right for me. Pls help! When i try to authenticate via pop3, I get: -ERR Authentication failed. In the logs, I get: May 21 11:14:07 Info: auth(default): client in: AUTH 1 PLAIN service=pop3 secured lip=127.0.0.1 rip=127.0.0.1 lport=110 rport=32774 resp=AGp1bmUAU0lORzNlcnQ= May 21 11:14:07 Info: auth(default):

On 6/9/2015 8:36 AM, Charles Marcus <CMarcus at Media-Brokers.com> wrote: > On 6/8/2015 5:11 PM, Pali Roh?r <pali.rohar at gmail.com> wrote: >> Still I want read/write access to storage and want to use mbox as >> storage (also for easier backup and copy)... >> >> And my question was how to properly read and write from/to mbox files >> which are used

On 3/9/2016 9:02 PM, Timo Sirainen <tss at iki.fi> wrote: > On 08 Mar 2016, at 01:50, Pavel Stano <stanojr at websupport.sk> wrote: >> >> sis attachment deduplication is broken in 2.2.16 upwards. >> It is caused by this commit. >> https://github.com/dovecot/core/commit/664bf3e236c214aee86294483c379e4fa66c2e63 >> >> in src/lib-fs/fs-sis.c function

I'm trying to configure my postfix server to use Dovecot as an SASL server and running into some problems. My server supports a couple of domain, I have multiple user/password files for multiple domains to make the files a little easier to manage. Not sure if this question should belong in the dovecot mailing list or the postfix one, but here goes anyway. I have everything configured to use

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:

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

i have install 2.1.1 and configured in dovecot log this error is coming every 20 seconds: dovecot: imap-login: Disconnected (no auth attempts in 0 secs): rip=**********, lip=**********, TLS handshaking: SSL_accept() syscall failed: Connection reset by peer and this error every 2 seconds: dovecot: imap-login: Disconnected (no auth attempts in 0 secs): rip=**********, lip=********** what can

I have postfix+ dovecot but when I run sasl - have this: Mar 31 21:21:39 localhost postfix/smtpd[13134]: warning: SASL: Connect to smtpd failed: No such file or directory Mar 31 21:21:39 localhost postfix/smtpd[13134]: fatal: no SASL authentication mechanisms Mar 31 21:21:40 localhost postfix/master[13128]: warning: process /usr/libexec/postfix/smtpd pid 13134 exit status 1 Mar 31 21:21:40

Hello, I'm trying to set up a sendmail server on 4.8 that supports auth-based relaying. I followed the procedures at http://puresimplicity.net/~hemi/freebsd/sendmail.html, and aside from having to run makes manually in the library directories, I had no difficulty. I did not use the rebuild world recommendation, though. Everything is up and running, but whenever I try to send mail

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

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

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