I do appreciate your prompt response.
Your first suggestion (to add an "owner-alias1: address" entry to the local
aliases file) creates a new problem ...
The queue entry has owner-ali...@example.dm as sender address, instead of
the real sender address of the initial message.
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
A87037FE0A 597 Mon Oct 29 14:12:39 owner-ali...@example.dm
(temporary failure. Command output: maildrop: maildir over
quota.)
us...@example.dm
So ... after the expiration of the maximal_queue_lifetime the DSN message
will not be sent to correct recipient ...
Your second suggestion works like a charm ... with a little risk of
confusion from the administrators point of view (distinct local and virtual
domains with distinct local and virtual aliases ... but in the end all
aliases treated as virtual aliases ...)
In the meantime I realized/discovered that when the alias1 is defined in
local alias file using the include file notation, i.e.
alias1: :include:/full/path/to/alias1_members
the message is queued with the initial sender address and with only the
overquota recipient (as it is when virtual aliases are used ... and as I
would expect ...)
Anyway I will go for the 'treat as virtual aliases' solution.
Yet, with all respect, I do believe that you should reconsider the issue so
that no such 'tricks' would be necessary and hence the deployment and
administration of the system would be more straightforward.
Thanks a lot again for your support.
Constantinos
----
Constantinos Kousouris
Network Operation Centre
Athens University of Economics and Business
-----Original Message-----
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Monday, October 29, 2018 1:49 PM
To: Postfix users <postfix-users@postfix.org>
Subject: Re: Multiple delivery of queued message to local alias
kousou+post...@aueb.gr:
> Hello all,
> For the past week I have been puzzled with the following case .
> In local aliases I have defined an alias
> alias1: user1, user2, user3
> User2 is overquota and messages destined to user2 are deferred.
> When a message is sent to alias1 it is delivered to user1 and user3,
> deferred for user2 and put in queue with user2 AND alias as recipients !!!
Has worked this way for 20 years. The problem is that there is only one
queue file record (for alias1). That record cannot be deleted as long as one
of (user1, user2, user3) is deferred.
The solution is to force Postfix to write the addresses to a queue file
before attempting delivery, so that it can delete individual recipients from
the queue file.
Add an "owner-alias1: address" entry to the local aliases file, or use
virtual_alias_maps instead.
Wietse
