search for: inet_listeners

thanks, but I do not understand was has a new configuration to do with my auth-Problem? My configuration settings has worked before the Update to 2.1.16. I have not see that the update has changed some of my config-files. ? Gesendet:?Samstag, 18. April 2015 um 20:24 Uhr Von:?"Edgar Pettijohn III" <edgar at pettijohn-web.com> An:?"Dovecot Mailing List" <dovecot at

I have a mail server with multiple IP addresses and associated DNS names In the dovecot configuration I have a listen directive: ??? listen = mail.example.com.com,mail.otherexample.com,localhost Multiple local stanzas are of the form: local mail.example.com { ? protocol imap { ???? ssl_cert = </etc/letsencrypt/live/mail.example.com/fullchain.pem ???? ssl_key =

Hallo I can not find a forum at dovecot.org and I get a problem I can not solve. After Updating to the version dovecot2? 2.1.16? I can no more get eMails with my eMail-client. All has been working fine before. Server: FreeBSD 10.0-RELEASE-p18, with perl 5, version 18, subversion 4 (v5.18.4) ? It seems it is an authentication problem with my server. The errors are: #cat dovecot.log Apr 17

Hello, Sorry, I know the topic has been talked about already but I searched the archives and I'm still unsure of the proper way to have dovecot (imap-login) listen to several addresses and/or several ports. 1. how do I translate dovecot-1 protocol imap { listen = xx.xx.xx.xx:143 yy.yy.yy.yy:143 ssl_listen = xx.xx.xx.xx:993 yy.yy.yy.yy:939 } I started by service imap-login {

Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver =

Hi, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] ->

hi all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the

Hi, Dovecot 2.2.9 (Debian package from backports) does not seem to respect lmtp_rcpt_check_quota # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$ disable_plaintext_auth = no lmtp_rcpt_check_quota = yes mail_debug = yes mail_gid = mstore mail_location =

Hi, we are running a 4 host setup which each hosts a director+mailbox which is mounted via NFSv4 from a DRBD cluster. * Dovecot upstream release 2.1.16 * Doveadm batch subcommand fix - http://hg.dovecot.org/dovecot-2.1/raw-rev/850b5d8bbcc9 * Pigeonhole release 0.3.4 Now we would like to remove duplicate Mails using the vnd.dovecot.duplicate extension using a SIEVE script like this: require

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 appreciate your suggestion. That'll allow both ports or only 8839? Derek On 27 April 2018 4:34:33 PM NZST, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> On 27 April 2018 at 02:25 Derek Harding <rev.derek.harding at gmail.com> >wrote: >> >> >> Hi, >> >> I want dovecot to listen for imaps (ssl) on both 993 and a >non-standard

Hello I use LDA Dovecot 2 with SIEVE as Postfix delivery agent and I occasionally get such message in syslog. info.log:Apr 13 12:39:40 lda(xxxxxxxx): Info: msgid=<4DA484FF.5060903 at gmail.com>: save failed to INBOX: Timeout while waiting for lock See below the doveconf -n trace Thanks for any info > # 2.0.11: /usr/local/etc/dovecot/dovecot.conf > # OS: FreeBSD 8.2-RELEASE amd64

Hello everybody, i tried to debug imap sessions with the rawlog feature and rawlog creates files but when i try to dump them doveadm tells me [...] Error: zlib.read((file)): unexpected EOF at [...]. I looked at syslog files and i see, that rawlog gets terminated with a segfault, e.g.: segfault at 10 ip 00007ff6da362596 sp 00007fffe725a080 error 4 in libdovecot.so.0.0.0[7ff6da2a4000+122000] Is

Hello All, Have anyone met the problem I am struggling with at the moment ? The problem is when I run two instances of dovecot 2.1.8 which are one for proxy-director and another one is a regular one on the same server then I have big amount of strange entries in the /var/log/mail.err: Jul 26 11:51:20 dovecot-test-1 dovecot: director: Error: Empty server list Jul 26 11:51:20 dovecot-test-1

Hi, I know that a lot of work has been done regarding doveadm server, but I'm still experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16 when running the following command in a 4 node director/mailbox cluster: /usr/bin/doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A The dovecot-error.log shows the following errors (addresses anonymized): Apr

Hi All, I need to import mailboxes into my Director NFS setup via one of my director proxy's as doing a direct dsync to the backend mailstores appears to giving me NFS locking issues. It looks like it may be possible to do this using doveadm listeners. I have setup doveadm listeners on a test proxy and backend mailstore. I am not sure how to make the dsync proxy through to the backend

Hi, I'm new to the list (and postfix / dovecot), so if I mistakenly omit something, then please forgive me. I cannot log into Thunderbird via IMAP with my configuration. However, I can check the mail of each user by logging into their user account & then using the "mail" command. Is there something that is wrong with my config to not allow me to log into Thunderbird

Hi, I have an issue with dovecot 2.3.7.2. When lmtp stores a message into INBOX, I get this error: 2019-10-29 16:32:53 lmtp(?test at XXXX?)<28874><4IPiEytbuF3KcAAAioI89A>: Error: sieve: Execution of script /config/dovecot/common/default.sieve was aborted due to temporary failure 2019-10-29 16:32:53 lmtp(?test at XXXX?)<23470>: Error: sieve:

We use a pair of replicating Dovecot servers. If a user subscribes to a folder, shared by an other user, in one replica, that does not get replicated to the other node. Subscription of regular folders below INBOX seem to replicate correctly. Is that a general bug, a known problem or do we need to enable that somehow. Here's our configuration for the concerned namespace: namespace users { ?

Hi, >> I have a fedora21 install with dovecot-2.2.18, and when creating a new >> subfolder with thunderbird, the actual folder name is >> "Folder1^Folder2" with a carat as a separator, instead of creating >> Folder2 in the Folder1 directory. >> >> Is this a thunderbird problem? I don't recall having this problem >> prior to upgrading to