Damian:
> > Damian:
> >> I am trying to understand "allow_untrusted_routing = yes" and the
> >> circumstances where it is (un)safe. The documentation mentions an open
> >> relay loophole in the context of backup MXes. Is untrusted routing safe,
> >> if Postfix has no explicit *_mx_* configuration?
On Tue, Oct 25, 2022 at 09:03:34AM -0400, Wietse Venema wrote:
> > I interpret your answer such that <"re...@third.tld"@mydomain.tld> does
> > not invoke some special trivial-rewrite resolve algorithm that is
> > dedicated to the case in which the local-part looks like an email
> > address. For
Wietse:
Postfix looks for @, % or ! in the address localpart, for example,
user%not-your-domain@your-domain.
There is no special resolver.
I believe, this is what I wrote.
If Postfix finds any, like it would in user%not-your-domain@your-domain,
and "allow_untrusted_routing = yes" is configured
On Tue, Oct 25, 2022 at 05:23:31PM +0200, Damian wrote:
> > My advice is to redesign the system to avoid the need for messing around
> > with the untrusted routing safety net. If you need to turn that knob,
> > you're asking for trouble, and probably doing something wrong.
>
> I want Postfix to a
Damian:
> Wietse:
> > Postfix looks for @, % or ! in the address localpart, for example,
> > user%not-your-domain@your-domain.
> >
> > There is no special resolver.
> I believe, this is what I wrote.
> > If Postfix finds any, like it would in user%not-your-domain@your-domain,
> > and "allow_untrust
Wietse:
There. And to repeat myself, it depends on the destination
MTA how it delvers user%not-your-domain@your-domain.
Viktor:
You'll ideally let go of the goal, but if not, you'll need to allow
untrusted routing, and regularly test carefully to make sure that it
does not create open relay
I've setup a postfix server as a closed relay to only deliver/forward
email for my domain. I believe I have everything working as desired,
except for what is getting logged.
If I connect to postfix with a portable mail client on my local network
and send a message through it, I see the connect
Hi,
I am facing a strange issue here, where I cannot resolve a virtual
alias with the local part support@.
I have a domain example.com in $virtual_mailbox_domains. The virtual
transport sends mail on to Dovecot. For virtual aliases, I use a basic
hash table, containing:
i...@example.com
i...@example.comn...@example.com
supp...@example.com n...@example.com
suppo...@example.comn...@example.com
The strange thing is that only the first and third aliases work. The
support@ alias is not resolved, Postfix just sends it on to Dovecot
with supp...@example.com as fin
On 10/25/2022 3:58 PM, Dominik George wrote:
I am facing a strange issue here, where I cannot resolve a virtual
alias with the local part support@.
I have a domain example.com in $virtual_mailbox_domains. The virtual
transport sends mail on to Dovecot. For virtual aliases, I use a basic
hash tab
James Pifer:
> I've setup a postfix server as a closed relay to only deliver/forward
> email for my domain. I believe I have everything working as desired,
> except for what is getting logged.
>
> If I connect to postfix with a portable mail client on my local network
> and send a message throu
Hi,
> I suspect a subtle typo is at work. Try:
> postmap -q supp...@example.com hash:/path/to/your/virtual_alias_map
I of course tested such things before asking...
The alias resolves using postmap.
Also, the support2 alias was deliberately created using copy&paste to avoid
typos. Adding
How embarrassing. You're right.Sorry for the noise.
>
> On Oct 25, 2022 at 6:32 PM, Wietse Venemawrote:
>
>
> James Pifer:
> > I've setup a postfix server as a closed relay to only deliver/forward
> > email for my domain. I believe I have everything work
Hi Dominiki
On Tue, Oct 25, 2022 at 10:58:51PM +0200, Dominik George wrote:
> I am facing a strange issue here, where I cannot resolve a virtual
> alias with the local part support@.
Please follow the instructions in
https://www.postfix.org/DEBUG_README.html#mail.
Bastian
--
Earth -- mother of
14 matches
Mail list logo