similar to: lda / postfix / dovecot -- bounced messages not working

Hello, I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a strange problem with lda. We use bounce mails for internal users if they try to send virus/spammails. The exact same config works with 2.2.23, but not with 2.3.0. The relevant postfix/master.cf part: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail

thanks for your input. Bill: deliver is just a symlink to dovecot-lda Stephan: I don't know, and and it even does not work when I use deliver -f "postmaster at ourdomain.internal" - I get the same error message. A part of the mail I got when using 2.2.23: Return-Path: <MAILER-DAEMON> Delivered-To: user1 at ourdomain.internal Received: from localhost (localhost [127.0.0.1])

Hi, I found the following in my logfiles: The failure is not reproducable at the moment. System is delivering mails to mailboxes with no problems at all. It is a production installation with medium load. dovecot --version: 1.1.7 OS: Linux (Gentoo/x86 stable) - grsec enabled kernel deliver.log: deliver(user at example.tld): Panic: file istream-tee.c: line 144 (i_stream_tee_read): assertion

I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In the Postfix log I now see: Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as B8CA22DA1B37 Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) Passed CLEAN

Hello, I have FreeBSD 12 server with postfix + spamassassin. Old config work fine. ------ old postfix master.cf spamfilter unix - n n - - pipe flags=R user=nobody argv=/usr/local/bin/spamc -e /usr/sbin/sendmail -oi -f ${sender} ${recipient} ------ I try to add dovecot-lda (with sieve support) as local delivery agent to postfix config ----------- postfix master.cf # Spamd filter spamfilter

I wrapped the LDA command in a script. I can see that Postfix passes "@@mydomain.tld" as the -d argument, without quotes. I then adapted the script to specifically replace this address with "@"@mydomain.tld, but this results in the following error message by Dovecot: ??? auth: Info: userdb(?): Username character disallowed by auth_username_chars: 0x22 (username:

Our setup is ok with Postfix / Dovecot. I just need to add dovecot LDA. I use the 1.0beta9 LDA Configuration: protocol lda { postmaster_address = postmaster@clm.net4all.ch #hostname = #mail_plugins = #mail_plugin_dir = /usr/lib/dovecot/imap #sendmail_path = /usr/lib/sendmail auth_socket_path = /var/run/dovecot/auth-master } auth default-socket { mechanisms = plain login passdb

Hi - Updated from 2.2.27 to 2.3.0 server is webmail (roundcube) Sending worked before after update. Now it receives, but trying to send - this is the bounce in the log Feb 9 01:37:45 {hostname} postfix/pipe[22891]: 931FD2577: to=<{user}@{hostname}.{tld}>, relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced (command line usage error. Command output: lda: Fatal:

Op 7-3-2018 om 15:40 schreef Stephan Bosch: > > > Op 7-3-2018 om 13:46 schreef Philipp Berger: >> I wrapped the LDA command in a script. I can see that Postfix passes >> "@@mydomain.tld" as the -d argument, without quotes. >> I then adapted the script to specifically replace this address with >> "@"@mydomain.tld, but this results in the

Hi Timo, some time ago (2007-03-24 and following) I asked whether it was intended that Dovecot deliver bounces mails (by terminating with status 89) if the deliver version is older than the rest of the dovecot installation. You replied that it was a bug, and that it had been fixed in <URL:http://dovecot.org/list/dovecot-cvs/2007-March/008346.html>. When I upgraded from Dovecot 1.0.2 to

Recently configured postfix to use the dovecot lda as I wanted to use sieve. Got that working a few days ago but noticed that I wasn't getting any emails to aliases. Checked the logs and saw messages like: Mar 1 08:19:59 carson postfix/lmtp[16949]: 0DCD22016BE: to=< sales at example.com>, relay=carson.example.com[private/dovecot-lmtp], delay=0.07, delays=0.01/0.01/0/0.04, dsn=5.1.1,

Oh wait, you crossposted to the postfix list. Please keep the discussion there going, you have a postfix issue, not a dovecot one ;) Tom On 02-03-17 09:40, Tom Hendrikx wrote: > Hi, > > Typically, postfix should resolve the aliases into user accounts that > dovecot knows before you even start delivering to dovecot. You probably > messed something up in the postfix config that

Hi, I've been trying to follow the documentation that I am finding, but am running into trouble getting things set up correctly for postfix + virtual domains (using ldap) with dovecot LDA. I can get it to work without LDA, but I'm running into permissions problems when I try to run with LDA. I am wondering if anyone has any good examples of configuring this. I basically have a

I have seen this thread about being able to run doveadm as a non-root user, but I don't understand the solution even though I have seen other pages give this link as the solution. http://bit.ly/2MC5oq9 What configuration is necessary so that I can set the permissions on /var/run/dovecot/stats-writer socket-file so when dovecot starts my virtual mail account has read/write access? I saw

Op 1/24/2018 om 5:30 PM schreef Infoomatic: > Hello, > > I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a strange problem with lda. > We use bounce mails for internal users if they try to send virus/spammails. The exact same config works with 2.2.23, but not with 2.3.0. > > The relevant postfix/master.cf part: > dovecot unix - n n

Dear all, I have a working setup with Postfix + Dovecot, storing users in a MySQL table. I ran into problems setting up and using a mail address like a"@"b at mydomain.tld, which by RFC should be valid, but leads to problems in Dovecot. From my debugging, I can see that on the lookup, Dovecot replaces %n with "a" (quotes added by me) and %d with "b at mydomain.tld"

Hi, Typically, postfix should resolve the aliases into user accounts that dovecot knows before you even start delivering to dovecot. You probably messed something up in the postfix config that disables alias expansion before dovecot delivery is attempted. Can you show us your postfix config? Kind regards, Tom On 01-03-17 15:36, Ian Evans wrote: > Recently configured postfix to use the

Op 6-3-2018 om 14:34 schreef Philipp Berger: > I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In > the Postfix log I now see: > > Mar? 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from > <admin at mydomain.tld> -> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from > MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as

Hi list, I have 7 virtual users in a sql database. I don't want any systemusers or local delivery using postfix. On the postfix side everything works fine as long as I use the 'local' delivery agent. But since I want to use dovecot's sieve functionality I set local_transport to dovecot. From now on Postfix seems to ignore local_* settings like local_recipient_maps. Here is my

I do not know if this is a help request to solve a problem but to understand what is going on. I am going to start with the problem description as I see it and we will go from there. I have postfix setup to use dovecot for tls/sasl in addition to its normal imap/pop3 functions. Postfix is also setup to do virtual domains, getting its information from the files valias, vmaps, and vhosts which are