[SOLVED] Question about postfix settings in combination with getmail

"[email protected]" <[email protected]>
Newsgroups gmane.mail.getmail.user
Message-ID <[email protected]>
Got an idea in an old postfix's mailing list thread, asked there, got a hint and found a solution:

My new thread in postfix's mailing list archive:
https://marc.info/?t=153418143900005&r=1&w=2

Thanks,
Michael


Am 13.08.2018 um 17:19 schrieb [email protected]:
> Hi all,
> 
> 
> hopefully not too off-topic, but I could imagine that some getmail users have had this situation before and might
> remember their solution:
> 
> I'm using (and loving :-)) getmail for syncing my email accounts at commercial ISPs (like the sender address of this
> email, [email protected], a yahoo account) to my own VPS, with dovecot and postfix on it.
> 
> The getmail part itself works fine and stable, but I recognized an ugly self-made side effect today, for the first time:
> 
> Let's say my VPS' domain is EXAMPLE.COM, one of my private email addresses might be [email protected].
> To get my postfix server to accept both "direct" emails (for [email protected]) and "getmail-ed" emails (for
> [email protected]), I've currently added "rocketmail.com" as (postfix) "virtual domain". As said, works fine for
> receiving "getmail-ed" mails.
> 
> BUT, today I wanted via Thunderbird to send an email from sender [email protected] to [email protected].
> And Thunderbird immediately shows me the postfix error msg "5.1.1 / Recipient address rejected. User unknown in virtual
> mailbox table". So currently my postfix server, listening secured for relaying my emails, "remembers" that he's also
> listening unsecured (on port 25) to receive emails for "virtual domain" rocketmail.com.
> 
> Any hints how to tell postfix that he shouldn't try to catch all emails for a virtual domain, but only the ones for
> existing (getmail) virtual users?
> 
> 
> Thanks in advance,
> Michael
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.