search for: dovecot_virtual_deliveri

On 24 Nov 2018, at 8.33, Odhiambo Washington <odhiambo at gmail.com> wrote: > > > I installed 2.3.4 and just used it with the config files for 2.3.3 without changing anything in the configuration. > I then realized that the LDA was throwing errors. > > 2018-11-24 00:02:51 1gQIaw-000AZS-Bc </var/spool/virtual/crownkenya.com/john.doe/Maildir

No support help needed, just a success report having Dovecot integrate with Vexim (exim with web based frontend and sql db): http://silverwraith.com/vexim/ Just wanted to forward some configs to the list if anyone finds them useful. I just switched from vexim's normal "virtual_delivery" to "dovecot_virtual_delivery" so I could use sieve, which works nicely with

Hello Trying to setup dovecot installation with sieve plugin, can't configure how to make redirect working. My setup 1 Exim + dovecot lda begin transports dovecot_virtual_delivery: driver = pipe command = /usr/local/dovecot/libexec/dovecot/deliver -d $local_part message_prefix = message_suffix = delivery_date_add envelope_to_add return_path_add log_output user = exim 2

On 23.11.2018 15.51, Brad Smith wrote: > On 11/23/2018 8:23 AM, Aki Tuomi wrote: > >> On 23.11.2018 15.20, Brad Smith wrote: >>> On Fri, Nov 23, 2018 at 02:29:22PM +0200, Timo Sirainen wrote: >>>> https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz >>>> https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig >>>> Binary packages in

Hi, I'm running Dovecot 2.1.7 on Debian. Exim is the MTA. I was recently made aware of the fact that the way in which Exim invokes dovecot-lda is prone to code injection: dovecot_virtual_delivery: driver = pipe command = HOME=/home/vmail/\$local_part /usr/lib/dovecot/dovecot-lda -f \$sender_address use_shell .. I.e. a command is executed via the shell, and Exim uses

I'm using exim4 to deliver into dovecot 1.1, and using plus-addressing to deliver mailing lists directly to appropriate folders in my "lists" mailbox. I created a file called /folder-map.lists that looks like ## folder-map.lists dovecot: Dovecot lpedge: Linux PowerEdge ... and so on. So mail to lists-lpedge at jay.fm goes to the "Linux PowerEdge" folder. The one

Hello list I am testing mdbox with Dovecot from http://hg.dovecot.org/dovecot-2.0-sis/.and my MTA is Exim. It appears to crash, but I am not sure how to capture the actual crash. What I get in Exim logs is: 2010-07-28 19:55:13 1Oe9uT-000KmG-Oz ** /var/spool/virtual/ titan.co.ke/wash/Maildir <wash at titan.co.ke> R=virtual_domains T=dovecot_virtual_delivery: Child process of

Hello list, When trying to deliver a big message (which over-quota user limit), I always get segmentation faults. Others common delivers work fine. This only happens with messages, which over-quota user limit. Here is more details: /var/log/maillog: ... ** user at fakedomain.ua R=virtual_user T=dovecot_virtual_delivery: Child process of dovecot_virtual_delivery transport (running command

I'm trying to make dovecot 1.2.15, deliver, openLDAP, exim and fetchmail work together on an Debian Squeeze (virtual) maschine. The connection between dovecot and LDAP seems to be working, I can logon from Thunderbird (IMAP) and my maildir is created automatically. So far so good. But when I download the mails via fetchmail, it seems that deliver cannot find the correct mailbox for the

I installed 2.3.4 and just used it with the config files for 2.3.3 without changing anything in the configuration. I then realized that the LDA was throwing errors. 2018-11-24 00:02:51 1gQIaw-000AZS-Bc </var/spool/virtual/ crownkenya.com/john.doe/Maildir>: dovecot_virtual_delivery transport output: lda(john.doe at our.domain.name)Error: net_connect_unix(/var/run/dovecot//stats-writer)

Hi there! I have been setuped exim and dovecot. Exim uses dovecot-lda to deliver mails to mailbox. Some configurations of exim: dovecot_virtual_delivery: ? driver = pipe ? command = /usr/libexec/dovecot/dovecot-lda -d $local_part@$domain -f $sender_address ? message_prefix = ? message_suffix = ? delivery_date_add ? envelope_to_add ? return_path_add ? log_output ? user = vmail ? group = vmail ?

Hi, We are seeing a frequent assertion failure on LMTP delivery with 2.3.0. This only appears to happen on CentOS/RHEL 7. Jan 24 08:30:58 smoker-devautomerge-c7-1 dovecot: lmtp(29540): Panic: file lib-event.c: line 148 (event_unref): assertion failed: (event != current_global_event) Jan 24 08:30:58 smoker-devautomerge-c7-1 dovecot: lmtp(29540): Error: Raw backtrace:

Hi! This is a bug in the new event code. Can you get a full gdb backtrace? Aki > On January 27, 2018 at 6:58 AM "J. Nick Koston" <nick at cpanel.net> wrote: > > > Hi, > > We are seeing a frequent assertion failure on LMTP delivery with 2.3.0. This only appears to happen on CentOS/RHEL 7. > > Jan 24 08:30:58 smoker-devautomerge-c7-1 dovecot:

Hi Aki, Please see below: Thank you -Nick # gdb /usr/libexec/dovecot/lmtp ./3445 Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/lmtp'. Program terminated with signal 6, Aborted. #0 0x00007f297814d1f7 in raise () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install dovecot-2.3.0-8.cp1162.x86_64 (gdb) back #0