Right, I figured out the symlink after I sent my response.
Did you try the command switches from my post?
Bill
On 1/25/2018 8:07 AM, Infoomatic wrote:
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
"[email protected]" - I get the same error message.
A part of the mail I got when using 2.2.23:
Return-Path: <MAILER-DAEMON>
Delivered-To: [email protected]
Received: from localhost (localhost [127.0.0.1])
by hosting.ourdomain.internal (Postfix) with ESMTP id 8E985424C7
for <[email protected]>; Thu, 25 Jan 2018 12:36:59 +0100 (CET)
Content-Type: multipart/report; report-type=delivery-status;
That's strange. Any ideas, anyone?
Regards,
infoomatic
Gesendet: Donnerstag, 25. Januar 2018 um 09:35 Uhr
Von: "Stephan Bosch" <[email protected]>
An: Infoomatic <[email protected]>, [email protected]
Betreff: Re: problem with lda
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 - - pipe
flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/deliver -d
${recipient} -f ${sender}
On the same machine, with 2.2.23 I get a bounce mail when trying to send a virus, with
the subject "VIRUS in message apparently from you (Eicar-Test-Signature)", to
both the users inbox as well as to the mailbox of [email protected]
With 2.3.0, in the logs I get an error:
relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced (command
line usage error. Command output: lda: Fatal: Invalid -f parameter: Missing
domain
and the alert message is only sent to [email protected], but not to
the user who tried to send the mail.
The relevant part of our dovecot.conf:
protocol lda {
mail_plugins = " quota zlib sieve acl mail_log notify"
postmaster_address = [email protected]
}
Does anyone know how to solve this problem? Or is there a workaround via
postfix/amavis/spamassassin? Any hints are highly appreciated, thanks!
Apparently, the ${sender} has no @domain part. Why?
Regards,
Stephan.
