similar to: Lmtp issues on dovecot 2.3.x with big messages

On 17.04.2018 2:21, Stephan Bosch wrote: > Op 16/04/2018 om 19:57 schreef Michael Tratz: >>>>> Messages are being sent to dovecot LMTP by postfix. If I change >>>>> this email >>>>> to another server with dovecot 2.2.x the same message are delivered >>>>> immediately. >>>> Confirmed. Starts to fail here around 30Mb. Tested

Op 16/04/2018 om 19:57 schreef Michael Tratz: >>>> Messages are being sent to dovecot LMTP by postfix. If I change this email >>>> to another server with dovecot 2.2.x the same message are delivered >>>> immediately. >>> Confirmed. Starts to fail here around 30Mb. Tested with Swaks. >>> >>> Working on a fix... >> Problem found.

Hello, After update dovecot to version 2.3.x, LMTP stopped to receive big messages ( > 45 MB ). Messages are being sent to dovecot LMTP by postfix. If I change this email to another server with dovecot 2.2.x the same message are delivered immediately. Log with mail_debug = yes: Apr? 4 13:36:13 mailsrv01 dovecot: lmtp(190031): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt=

Op 4/4/2018 om 8:26 PM schreef Ricardo Machini Barbosa: > Hello, > > After update dovecot to version 2.3.x, LMTP stopped to receive big messages > ( > 45 MB ). > Messages are being sent to dovecot LMTP by postfix. If I change this email > to another server with dovecot 2.2.x the same message are delivered > immediately. Confirmed. Starts to fail here around 30Mb. Tested

Hi. I'm using SMTP auth with Exim authenticating against Dovecot's auth socket. My (excellent) SMTP test tool "swaks" (http://jetmore.org/john/code/#swaks) tries multiple auth mechanismus consecutively which leads to the following message in Dovecot's log file: Error: auth(default): BUG: Authentication client gave a PID 6738 of existing connection I'm not sure where to

Sending (in my case: forwarding) messages from Sieve via sendmail does not work with version 2.3.1. I have narrowed it down to this simple test case: # dovecot -n # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # OS: Linux 4.4.0-119-generic x86_64 Ubuntu 16.04.4 LTS # Hostname: tuxi.topfen.net first_valid_gid = 200 first_valid_uid = 200 mail_location = mbox:~/mail passdb { args =

Hello again, I have created a parser script, a little bit more advanced than the one provided with Dovecot. The main feature is probably to index documents inside zip/rar/tgz archives... I am using Ansible, swaks and doveadm to run automatic tests for each supported content. For specific reasons, I am not yet able to add Apache Tika to the distribution. However, I already made some tests

:-) My postfix configuration is quite complex with a lot of special cases and rules. However I'd like to make an anti-spam configuration as simple and lightweight as possible (KISS). /etc/postfix/master.cf ------------------------------------------------------------------------ smtp inet n - n - - smtpd -o content_filter=spamassassin spamassassin unix

Hi, I hit a bizare problem with dovecot 2.2.7 on debian 9 with LMTP enabled and auth/penalty disabled as documented here : https://wiki.dovecot.org/Authentication/Penalty Use case : I run a swaks command to send an email to an exim4 that tries to make a callout to dovecot-lmtp. At RCPT TO: swaks hangs 5.0<something-small> seconds then process normally (exim is waiting for callout

Two machines (NFS Server: running ZFS / Client: disk-less), both are running FreeBSD r253506. The NFS client starts to deadlock processes within a few hours. It usually gets worse from there on. The processes stay in "D" state. I haven't been able to reproduce it when I want it to happen. I only have to wait a few hours until the deadlocks occur when traffic to the client machine

Hi, I can confirm that in the bad behavior, the 5 second delay occurs at each AUTH in our case. I think the configuration we have kill auth process at each end of AUTH (and fork a new one for next next AUTH). I think the "disable" flag is local to the process that is killed / respawned. A collegue of mine, Laurent Guerby, has found a workaround for us and it's findings seems

On 16/03/2019 11:49, Marek Kozlowski via dovecot wrote: > Can I test local mail delivery by dovecot LMTP manually? I mean: to > simulate "I'm the Postfix" and produce for some testing e-mail the > same effect as postfix granting it via `local_transport' to dovecot? > You can probably use swaks for that, it has LMTP support. -- You canna change the laws of physics,

Hi Marti, (Please do not send CC to my private account) Marti Markov <marti1234 at gmail.com> (Mo 21 Nov 2016 03:52:54 CET): > > Here is the router: > > virtual_aliases: ? > hide data = CHECK_VIRTUAL_ALIASES > local_user: > debug_print = "R: local_user for $local_part@$domain" > driver = accept > domains = +local_domains >

Is there a way to get this as a patchset against 2.3.8? On Tue, Oct 8, 2019 at 12:03 PM Stephan Bosch via dovecot < dovecot at dovecot.org> wrote: > > > On 08/10/2019 02:52, Stephan Bosch via dovecot wrote: > > > > > > On 07/10/2019 15:13, Fabian Kuran via dovecot wrote: > >> Hi, > >> > >>> Am 23.09.2019 um 09:36 schrieb Filip Hanes

We use Maildir++ quota, with the rules taken from our LDAP backend. We also have an old expunge script that's not quota-aware; it removes old messages from the maildir by simply deleting the files. Sometimes, a mailbox is over quota before the script runs, but well under quota after the old messages are deleted. This change does not seem to be picked up, however: When I try to deliver a new

Dear dovecot users. I have an odd issue in that when I connect to my dovecot server from either a local or remote system I can't see my test emails (I have the impression that is is looking at the wrong location on disk). here are some details.... # dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 auth_debug = yes auth_debug_passwords = yes

Hi Heiko, Here is the router: virtual_aliases: driver = redirect debug_print = "R: Check address using virtual_aliases for $local_part@$domain" allow_fail allow_defer hide data = CHECK_VIRTUAL_ALIASES user = vmail group = mail local_user: debug_print = "R: local_user for $local_part@$domain" driver = accept

Hi all, Hey all, I upgraded to dovecot 2.3.1 (from 2.2.34) and noticed that the behavior for dovecot-lda changed. Apparently it no longer accepts -f "" or -f "<>? With 2.2.34, both were accepted now I get: root at mail:~# /usr/local/libexec/dovecot/dovecot-lda -f "<>" lda(root): Fatal: Invalid -f parameter: Null path not allowed or root at mail:~#

On 31/03/18 09:29, Stephan Bosch wrote: > Op 3/31/2018 om 9:27 AM schreef Andr? Rodier: >> Hello, >> >> I am using a custom directory for sieve logs and trace and it apparently >> generate an error, in some corner case. >> >> - I have an IMAP global sieve script, that is run when appending emails >> into the "Archives" folder. >> - I

Hi, I wonder if someone could give me a little help bringing the sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole Trying to use both together at present I get an error: ? managesieve: Fatal: Couldn't load required plugin /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen() failed: /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: undefined symbol: