On Sun, Jul 28, 2019 at 08:14:38PM +, Bjoern A. Zeeb wrote:
> Now sometimes the same email comes back to MX-E via an *alias* (no From:
> changes) on MX-3. MX-E will receive the looped back email from MX-3
> and then decides by its transport rules that it should send it to MX-I.
>
> Here’s
Wietse Venema schrieb am 28.07.19 um 15:36:02 Uhr:
> ratatouille:
> > Hi!
> >
> > May I allude the dead link http://www.porcupine.org/postfix/dos.html
> > on
> > http://www.porcupine.org/postfix/doc/overview.html and others.
> >
> > Have a good afternoon!
>
> Fixed after 20+ years.
;-) Than
Dear all,
I am confronted with a problem in a mail-cluster of internal, external,
and a 3rd party postfix setup.
For simplicity I’ll reduce the setup to:
MX-I (internal mail relay, user authentication, .., also LMTP delivery)
MX-E (external mail relay, incoming/outgoing)
MX-3 (3rd party mail
ratatouille:
> Hi!
>
> May I allude the dead link http://www.porcupine.org/postfix/dos.html
> on
> http://www.porcupine.org/postfix/doc/overview.html and others.
>
> Have a good afternoon!
Fixed after 20+ years.
Hi!
May I allude the dead link http://www.porcupine.org/postfix/dos.html
on
http://www.porcupine.org/postfix/doc/overview.html and others.
Have a good afternoon!
Andreas
Fulvio Scapin:
> Thanks for the answer Viktor.
>
> As I mentioned, mine was an attempt to parse/validate the syntax
> externally, so I used the documentation as a guideline and probed with
> postmap to see what it would actually accept or not.
>
> I hope you will forgive me if I disagree on a spe
