Hello,
> On 17 juin 2020, at 22:48, @lbutlr wrote:
>
> On 17 Jun 2020, at 14:00, Patrick Proniewski wrote:
>> Not possible yet. A flag exists for Exchange 2019 but we are running 2016
>> now and upgrade is not scheduled for now.
>
> Perhaps showing the bouncing emails to whomever is in charge
On Tue, Jun 16, 2020 at 10:04:15PM -0600, Gary Aitken wrote:
> ok, I'm willing, but I haven't the faintest idea what setting it up manually
> means. I presume some settings in main.cf, but postconf -d shows 979 things
> to choose from. suggestions?
Intro:
http://www.postfix.org/SOHO_README
On 6/16/20 10:39 PM, Bob Proulx wrote:
Gary Aitken wrote:
...
For future reference it is also possible to use dpkg to remove
postfix ignoring the dependency and then install it again satisfying
the dependency.
dpkg --purge --force-depends postfix ...verify /etc/postfix/ and
other locations are
On Thu, Jun 18, 2020 at 12:52:43PM +1200, Peter wrote:
> That said, CentOS 8 is on openssl 1.1.1c so I'm hoping that will
> continue to be supported for the foreseeable future.
Presently, OpenSSL 1.1.1c is the only LTS OpenSSL release, and even
3.0.0 is not yet expected an LTS release, that'll l
On 18/06/20 12:07 pm, Viktor Dukhovni wrote:
On Jun 17, 2020, at 9:34 PM, Peter wrote:
I'd like to avoid this if possible. CentOS 7 has openssl 1.0.2k and doesn't go
EOL until 2024. I'd like to be able to support new Postfix releases for it for
at least another two or three years.
Postfix
> On Jun 17, 2020, at 9:34 PM, Peter wrote:
>
> I'd like to avoid this if possible. CentOS 7 has openssl 1.0.2k and doesn't
> go EOL until 2024. I'd like to be able to support new Postfix releases for
> it for at least another two or three years.
Postfix 3.5 will be supported until 3.9 comes
On 17 Jun 2020, at 14:00, Patrick Proniewski wrote:
> Not possible yet. A flag exists for Exchange 2019 but we are running 2016 now
> and upgrade is not scheduled for now.
Perhaps showing the bouncing emails to whomever is in charge of this schedule
will change it, especially if any of the boun
On 17 Jun 2020, at 11:07, Roberto Ragusa wrote:
> but when I start contacting them they easily complain with "too many
> concurrent connections" because all the mx hosts have been resolved to the
> same IP (well, IP pool, actually). These domains (not under my control) are
> hosted on a provide
On Wed, Jun 17, 2020 at 10:00:32PM +0200, Patrick Proniewski wrote:
> > - disable SMTPUTF8 in Postfix.
>
> That means disabling it everywhere and let messages bounce on MX servers.
> Would not really change anything in the end.
Yes, but it is the right thing to do. Better than generating
backs
Hi,
> On 17 juin 2020, at 15:42, Bastian Blank
> wrote:
>
> On Wed, Jun 17, 2020 at 02:37:23PM +0200, Patrick Proniewski wrote:
>> For some time now I notice that some messages, either originating from
>> Internet or from internal servers are bounced when they arrive on the last
>> hop: Excha
On Sat, Jun 13, 2020 at 01:19:44AM +1000, Nikolai Lusan wrote:
> Thank you very much for finding that.
The OP provided a system on which I could compare:
- Vendor Postfix vs. Postfix built from source
- stock configs vs. OP's actual config.
It turned out that the configuration was what
Roberto Ragusa:
> Hi,
>
> is there a way to throttle outgoing SMTP by destination IP?
No. The Postfix scheduler does not know about IP addresses. That
is a very fundamental property of the design. It schedules deliveries
in parallel, based on domain names.
Otherwise, if DNS lookups for one domai
Hi,
is there a way to throttle outgoing SMTP by destination IP?
My problem is that I send mails to
- domain1.com
- domain2.com
- domain3.com
which handle mails through
- mx.domain1.com
- mx.domain2.com
- mx.domain3.com
but when I start contacting them they easily complain with
"too many concurre
Patrick Proniewski:
> Jun 17 12:34:20 postfix-mailgw/smtp[77347]: 57F56EB256:
> to=, orig_to=,
> relay=Exchange-VIP[Exchange-VIP]:25, delay=0.01, delays=0.01/0/0/0,
> dsn=5.6.7, status=bounced (SMTPUTF8 is required, but was not offered by host
> Exchange-VIP[Exchange-VIP])
>
It is required (i
On Wed, Jun 17, 2020 at 02:37:23PM +0200, Patrick Proniewski wrote:
> For some time now I notice that some messages, either originating from
> Internet or from internal servers are bounced when they arrive on the last
> hop: Exchange.
> Jun 17 12:34:20 postfix-mailgw/smtp[77347]: 57F56EB256:
> t
Hi,
> On 17 juin 2020, at 15:08, Matus UHLAR - fantomas wrote:
>
> On 17.06.20 14:37, Patrick Proniewski wrote:
>> I have at work a Postfix infrastructure that sits between Internet and our
>> Exchange servers. Postfix is used for MX and SMTP roles, ensure filtering
>> with Amavisd/Clamav/etc
On 17.06.20 14:37, Patrick Proniewski wrote:
I have at work a Postfix infrastructure that sits between Internet and our
Exchange servers. Postfix is used for MX and SMTP roles, ensure filtering with
Amavisd/Clamav/etc.
For some time now I notice that some messages, either originating from Inter
Hello,
I have at work a Postfix infrastructure that sits between Internet and our
Exchange servers. Postfix is used for MX and SMTP roles, ensure filtering with
Amavisd/Clamav/etc.
For some time now I notice that some messages, either originating from Internet
or from internal servers are bounc
18 matches
Mail list logo
