Hi,
our mail server is running nicely for years. There is one recipients server
that doesn't accept our mails with a "time out" response without sending a more
detailed error message. I have attached the -v log output, but only the part
that is produced by the smtp-process at sending to this re
Sean Hennessey:
> I was using the sender_dependent_default_transport_maps to pick
> off what I thought was going to be the interesting from domain.
> The good news is that this mail is coming from customer applications.
> It's not coming from regular user mail clients. So I can guarantee
> there is
Michael Schumacher:
> Hi,
>
> our mail server is running nicely for years. There is one recipients server
> that doesn't accept our mails with a "time out" response without sending a
> more detailed error message. I have attached the -v log output, but only the
> part that is produced by the sm
On 1/13/2023 12:02 AM, Benny Pedersen wrote:
Jaroslaw Rafa skrev den 2023-01-12 21:52:
Dnia 12.01.2023 o godz. 13:49:33 post...@ptld.com pisze:
My solution...
main.cf:
smtp_header_checks = pcre:/etc/postfix/header_checks_smtp
/etc/postfix/header_checks_smtp:
/^Received:/ IG
Hi, i 've question, i need to migrate a virtual domain from 2 server
(with postfix).
On the new server i define mail users and domain but it'isnt in
production now dns record defined.
On the same new soerver i've other virtual domain.
I want that , for a few days, if one user of other domai
>>> 192.0.2.1:submission inet n - n - - smtpd
>>> -o syslog_name=vpnsubmission
>>> -o smtpd_sasl_auth_enable=no
>>> -o
>>> smtpd_relay_restrictions=permit_mynetworks,reject_unauth_destination
>> -o header_checks=pcre:/etc/postfix/vpn_header_checks
>
> header_checks
I have created a second postfix server in my LAN. The idea is to use both in a
failover/loadbalancing setting for now. At the back are two dovecots that
replicate to each other.
When mail is sent out via my router, it picks up anything that goes out to port
25 and makes sure it comes from mail.
On 12.01.23 18:24, Emmanuel Fusté wrote:
For to address the forwarding problem, you should add ARC to the
sending and verifying stack, It was designed specifically for that,
but not widely used, it is pretty experimental.
ARC requires you to trust ARC signer as it is third party.
--
Matus U
Hello!!
Gerald Galster wrote in
:
|>>> 192.0.2.1:submission inet n - n - - smtpd
|>>> -o syslog_name=vpnsubmission
|>>> -o smtpd_sasl_auth_enable=no
|>>> -o
|>>> smtpd_relay_restrictions=permit_mynetworks,reject_unauth_destination
|>> -o header_checks=pcre:/etc
On Fri, Jan 13, 2023 at 05:36:16AM +, Sean Hennessey wrote:
> I was using the sender_dependent_default_transport_maps to pick off
> what I thought was going to be the interesting from domain. The good
> news is that this mail is coming from customer applications. It's not
> coming from regular
On 13/01/23 08:40, Viktor Dukhovni wrote:
On Thu, Jan 12, 2023 at 01:49:33PM -0500, post...@ptld.com wrote:
My solution...
main.cf:
smtp_header_checks = pcre:/etc/postfix/header_checks_smtp
/etc/postfix/header_checks_smtp:
/^Received:/ IGNORE
/^X-Originating-Ip:/
This is I suspect a little off-topic for here, in which case accept my
apologies please.
My Postfix instance is well-established on a LAN behind a WAN IP with
a decent reputation. The internet router for the network has a 4G
failover device for occasional downtime to ensure that critical co
12 matches
Mail list logo