giacomo:
> > > I've one problem, the messages are without X-Original-To header.
> > ...
> > > Received: from isp.mailserver.com ([xxx.x.x.x])
> > > by localhost (isp.mailserver.com [xxx.x.x.x]) (amavisd-new, port 10024)
> > > with ESMTP id 7FO08wsiMVCK for <catch...@realdomain.com>;
> > > Fri, 3 Oct 2014 18:05:00 +0200 (CEST)
> >
> > As you see above, the ISP expands virtual aliases before their
> > content filter. I suspect that this is why they lose the original
> > recipient.
> >
> > > Received: from mail.somedomain.com (mail.somedomain.com [yyy.yyy.yyy.yy])
> > > by isp.mailserver.com (Postfix) with ESMTP id F09FD4AC55F
> > > for <us...@realdomain.com>; Fri, 3 Oct 2014 18:04:57 +0200 (CEST)
> >
> > I don't understand how the conversion from catch...@realdomain.com
> > to us...@realdomain.com is done.
>
> The catch...@realdomain.com receive all mail for @realdomain.com.
> For now I use an internal mail server (HMailServer) that reads
> and split each messages into the respective mailboxes.
For the last time, I repeat my question. What information is
used to convert catch...@realdomain.com into us...@realdomain.com?
As mentioned, the To: header must not be used - it does not work
for BCC recipients.
For example, this email reply does not have you in the To: header.
If you were to deliver this email based on the To: header then you
would be sending it right back to the postfix-users mailing list.
Wietse
