On Tue, 31 Aug 2010 17:39:50 +0100, Simon Waters <sim...@zynet.net> wrote: > On Tuesday 31 August 2010 16:57:16 Stefan Seidel wrote: >> >> Additionally, the mail is also stored to a local >> mailbox. I know, that means that users could fetch them via >> POP3/IMAP/Webmail, but as it is, they prefer getting it forwarded. > > Just send the email on as if it is new mail rather than using Postfix for > forwarding, and then it will appear to come from the final destination > host, > and NDN will come back to that host rather than being "general > backscatter". Thanks for the hints. The virtual_alias_map solution is just the one that came with the server management software I use, so I never doubted it. It escapes me however, where I should put a .forward file - the mailboxes are virtual users from a MySQL database and as such there's no home directory. Putting the file in the maildir doesn't work.
> I dare say the relevant ".forward" file is trivial to create, but one can > probably use the Sender Rewriting scheme code out there if ".forward" is > too simple for one's liking. I was actually in favour of using SRS as I also use SPF and it is often mentioned that SRS is needed for SPF to work across forwarding, however everything I found on the internet told me that Postfix didn't support it. > But strikes me if you deliver and forward, perhaps that second step > doesn't > even need SMTP? What are you doing that encourages you to duplicate every > email? Sounds like there maybe a bad design decision lurking. Well, it's an email address, hosted on my server, of which several people want to receive all mails in their private email account as well. As I said before, POP3-ing those messages solves every aspect of this problem, but I can't sell that to those users. Also, some mail providers (e.g. the big Y) do support neither SSL nor CHAP for fetching external POP3 accounts, something I consider broken. Thanks so far, Stefan
