On Sat, Jun 25, 2022 at 09:16:57PM -0300, Luc GMail wrote:
> On Jun 25 2022 at 6:05 PM Jaroslaw Rafa wrote:
>
> > Because with such a complicated thing as configuring
> > a MTA (yes, it *is* complicated) you should never rely
> > on recipes. You should rely on reading thoroughly
> > the MTA documentation
>
> 2. Thank you for acknowledging that yes, it *is* complicated. That is
> rare, unfortunately.
MTAs address many diverse use-cases and are therefore complex power
tools. The documentation complexity is irreducible. There is no royal
road to understanding, once you have the right general background, the
discrete tutorials at www.postfix.org are quite approachable. Without
adequate background you're sure to be lost. This is why the fine book
by Ralf and Patrick is essential background reading for those not
already well prepared.
> Suppose I have a mailbox called 'realbox' at example.com. I never
> reveal it to anyone. Instead, I always tell people to contact me at
> l...@example.com. When mail comes in, the MTA realizes there is no
> 'Luc' user or mailbox, so the mail is sent to the catch-all account.
This does not require a "catch all", just one or a few addresses that
route to your script. A "catch all" handles mail for all names at a
domain, even ones you never shared with anyone, and is a pointless spam
magnet.
> When I finally have it working with postfix, I will bug you people
> with one more question: how do I scrub the secret 'realbox' user
> account from the headers so it doesn't get exposed in replies?
Postfix does not add email addresses to headers. MUAs do that.
However, in case you MUA chooses to expose the "secret" address,
you can always rewrite it on the way out:
https://www.postfix.org/postconf.5.html#canonical_maps
In addition you can use access(5) to refuse direct mail to the
"secret" address, which by the way can be at a local domain that
has no IP address or MX records, and the entire domain can be refused
in access(5) tables.
realmailbox@local.invalid
--
Viktor.
