EML:
> On 17/01/2023 23:13, raf wrote:
> > On Tue, Jan 17, 2023 at 03:31:43PM +0000, [email protected] wrote:
> >
>
> >> (2) Mail to unknown user '[email protected]':
> >>
> >> valias: "@example.com @example.com, [email protected]"
> >> vmailbox: "@example.com example.com/foo/"
> >>
> >> <snipped>
> >> Recipient address rejected: User unknown in virtual mailbox table;
> >> from=<[email protected]> to=<"[email protected], foo"@external.org>
> >
> > I'm not suprised that it didn't work. I would have thought that
> > "@example.com"
> > is not a valid alias target since it's not a valid email address. That might
> > not be the reason that it didn't work, but it would make sense.
>
> It doesn't look good, but the virtual mailbox does allow an address of
> this form, so the virtual alias might be expected to also allow it.
The meaning of @domain depends on context.
The virtual(8) delivery agent has a pattern for @domain that ignores
the address localpart, and the virtual(5) alias map has a pattern
for @domain that may or may not ignore the localpart. There is no
guaranee that @domain will be univerally accepted where an email
address is expected.
If you want to store mail for a catch-all recipient and forward it
to some other address, you can use recipient_bcc_maps with either
a constant mapping (hash, btree,m etc.) or transform the recipient
with a regular expression mapping (pcre, regexp).
Wietse
