On 27/11/2022 11:46 AM, Wietse Venema wrote:
I think there is no risk of (false) loop detection between MSA
instance and MTA instance, because the MSA instance is supposed to
send all mail to the security gateway, regardless of destination:
MSA client -> port 465/587 MSA server -> security ga
Gustavo Balduino:
> From what you two concluded, there's no way to reach this behavior
> without splitting the instances, am i correct?
A single instance may be possible but it would be more complicated
and more difficult to maintain than to the two-instance approach.
It would in fact be the si
On Mon, Nov 28, 2022 at 10:18:22AM -0300, Gustavo Balduino wrote:
> On 27/11/2022 11:46 AM, Wietse Venema wrote:
> > I think there is no risk of (false) loop detection between MSA
> > instance and MTA instance, because the MSA instance is supposed to
> > send all mail to the security gateway, rega
All,
I'm bringing a new sending IP online and need to know if there is an easy way
to warm it up w/ Postfix.
For those that don't know, warming up is a process where you start to send
small amounts of mail of the new IP till it's built up a good enough reputation.
In a past life I use Port25's
On Sun, Nov 27, 2022 at 11:40:01PM -0500, Jonathan Capra
wrote:
> I've been trying to set up a Backup MX with a MySQL backend. I have my
> primary working well with MySQL and Postfixadmin frontend. But up till now,
> I've always set up my backup MX with a standard Postfix setup using Berkley
> D
