similar to: Dovecot no logs by sieve user script

Op 06/01/2019 om 18:58 schreef Christian Wolf: > > Dear mailinglist, > > I have the problem that I had to migrate a setup and since then my > user's sieve script does no longer log anything. > > I have sieve_user_log unset and sieve points to a folder (ready for > ManageSievev service). In the old config I had sieve point to the > symlink and sieve_dir point to

Hello Im having issues login to dovecot using imap through telnet. Im running Linux 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u1 (2019-09-20) x86_64 GNU/Linux Im totally new to setting up mailservers. I havesetup a postfix for SMTP and it can receive emails. Postfix version is mail_version = 3.1.12 I have also installed Dovecot version:2.2.27 (c0f36b0) My configuration is such that POSTFIX is

Hello, I am using dovecot as an imap server, mail is stored in mail directories. Configuration is below. One mail directory has about 14 Gb of mail in the inbox and .Sent directories. Searching from an Android phone with gmail is slow or doesn't work (it times out). Is there a configuration for Dovecot that can improve this? A better e-mail client for Android? Thanks, John root at

Hi people, Version of my beloved Dovecot installation: 2.2.27 (c0f36b0) I moved from a OS X server to a Linux (Ubuntu) Headless server. All fun and good to play around with. Love almost everything. In the combination with Postfix and Dovecot I?m stuck to despair into oblivion. Everything works except I cannot send mail from my (OS X) Outlook client I keep getting: Connection to the

Sure :) thanks cat /var/log/dovecot/[...] Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131) Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=JK0Bfm9YuqfAqAFk lip=192.168.1.100 rip=192.168.1.100 lport=143 rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== (previous base64 data may contain

Do I modify auth-system.conf.ext only (sorry for the question) if yes, I've same problem Pol On 2017-09-05 13:34, Aki Tuomi wrote: > Try configuring like this: > > passdb { > args = scheme=SHA256 username_format=%u /etc/dovecot/users > driver = passwd-file > } > > passdb { > driver = static > args = username=%n noauthenticate > skip = authenticated

Hi, Trying to keep abusive/buggy IMAP clients at bay on a number of Dovecot proxy servers, I've reconfigured them to use "mail_max_userip_connections = 50" in the "protocol imap" section, followed by restarting Dovecot. Yet, I'm still seeing 160+ established connections from a single IP address for the same email account. Am I missing anything? # 2.2.27

Hi, I have been using this setup for years: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~ I have since learned that mail_home and mail_location should be different. I plan to use this: mail_home = /var/mail/vhosts/%d/%n mail_location = maildir:~/mail I would like the transition to be transparent for my email clients. I don't want mail/directories/sieve_scripts to

Hello Actually im not using PAM at all. So yes its true i could drop that. But i see that you have put additional empty double colons in your passwd file which i didn't. So maybe this is the issue? I will try. Thank you ________________________________ From: Aki Tuomi <aki.tuomi at open-xchange.com> Sent: Tuesday, November 19, 2019 10:49 PM To: Andrej Rehak <andrej.rehak at

does not work :-/ Sep 05 13:49:41 auth: Debug: auth client connected (pid=31115) Sep 05 13:49:41 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=IFCT0m9Y0KjAqAFk lip=192.168.1.100 rip=192.168.1.100 lport=143 rport=43216 resp=AHBvbGhhbGxlbkBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== (previous base64 data may contain sensitive data) Sep 05

I ran across what I think may be a bug in dsync when trying to convert from mbox to Maildir format. My first attempt failed with a runaway dsync process spewing out thousands of identical lines of the form: dsync(buus): Error: Duplicate mailbox GUID 00fe691ff60da85b090d0000c8119523 for mailboxes Archive/Personal and Work/VendorInfo - giving a new GUID 00fe691ff60da85b090d0000c8119523 to

thanks Aki, but with all your advices I've same problem: in the logs always I see the authentication with user and domain name, so dovecot doesn't accept it any idea? thanks! Pol On 2017-09-05 10:58, Aki Tuomi wrote: > Oh right, you need to do it like this... > > after the passwd-file drivers add > > passdb { > driver = static > args = username=%n

Hello, Thanks for the advice, I have made that change now but the server is still doing the same fail with no logs thing it was before. # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.6 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no login_greeting = Welcome to easyMail.

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Is your server behind proxy maybe? Can you see in logs that you get different IPs? </div> <div> <br> </div> <div> Maybe check with `doveadm who` how many connections you have? </div> <div>

Hi, mail_max_userip_connections is only enforced at the backend level. The setting has no effect on proxy. If you want to force the limit then you can only do it in the backend. Sami > On 9 Mar 2017, at 12.05, Adi Pircalabu <adi at ddns.com.au> wrote: > > Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per

You can usually see from doveadm who or logs if your router/whatever is doing NAT. Which would be the reason why 500 connections wouldn't be enough. Aki > On 27/02/2020 23:21 Esteban L <esteban at little-beak.com> wrote: > > > > It's not behind a proxy (unless the router is acting as a proxy?). Could it be that my router is doing some Hairpin NAT tomfoolery? The

i'm trying to enable sieve on my dovecot installation, but it seems i'm missing something. Managesieve is ok, i can mange script, but they have no effect at all i've got no error in logs, but no filter is applied here is my dovecot conf : # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.3 ext4 dict {

Hello, Config infos below. Short version, I am getting this weird anomaly on my main email account. Such that, "dovecot.sieve" is showing up as a mailbox in my various email clients (e.g. k-9 (mobile), and Evolution). I have tried deleting the "rogue folder" with doveadm, but it just returns. Anyone have any suggestions where I can track this down. dovecot --version

Hi list, this question was already posted a few years ago (https://www.dovecot.org/list/dovecot/2014-November/098585.html). I already asked the original queriest and he told me, that he never got an solution or workaround but it was not important enough for him. When using replication in conjunction with sieve vacations, the .dovecot.lda-dupes file is not synced with the other server. So when

Hi, I am trying to setup Sieve replication, it is almost working: 1/ Create a script - sync'd across 2/ Activate/de-activate a script - change sync'd 3/ Delete a script - change sync'd But if I make a change to a script it is not replicated, unless I de-activate and activate again. I am seeing in the logs the below during this process (de-activating/activating): Oct? 9