Monday, January 30, 2023, 10:59:19 AM, Viktor Dukhovni wrote:
> On Mon, Jan 30, 2023 at 10:50:16AM +1100, Phil Biggs wrote:
>> I understand that why something non-critical, like the patch below, wouldn't
>> be
>> listed in the announcement but would it have been incorporated into 3.7.4?
> Th
On Mon, Jan 30, 2023 at 10:50:16AM +1100, Phil Biggs wrote:
> I understand that why something non-critical, like the patch below, wouldn't
> be
> listed in the announcement but would it have been incorporated into 3.7.4?
The patch is included in the latest patches for Postfix 3.[4567] and
also
Monday, January 23, 2023, 9:35:06 AM, Wietse Venema wrote:
> [This this announcement will be available at
> https://www.postfix.org/announcements/postfix-3.7.4.html]
> Fixed in Postfix 3.7, 3.6, 3.5, 3.4:
> * Workaround: with OpenSSL 3 and later always turn on
> SSL_OP_IGNORE_UNEXPECTED_E
On Sun, Jan 29, 2023 at 05:57:45PM -0500, Wietse Venema wrote:
> > > Is there a way to accomplish that?
> >
> > Yes:
> >
> > master.cf:
> >
> > smtp inet n - n - - smtpd
> > -o { append_at_myorigin = yes }
> > -o { rewrite_service_name
Viktor Dukhovni:
> On Sun, Jan 29, 2023 at 09:32:47PM +, Sean Hennessey wrote:
>
> > What I'm looking for is the envelope recipient. I need a way to force
> > an unqualified to address to a domain I can blackhole. I've got an
> > application that feeds into these systems that will allow its us
On Sun, Jan 29, 2023 at 09:32:47PM +, Sean Hennessey wrote:
> What I'm looking for is the envelope recipient. I need a way to force
> an unqualified to address to a domain I can blackhole. I've got an
> application that feeds into these systems that will allow its users to
> enter badly formed
Sean Hennessey:
> Viktor,
>
> What I'm looking for is the envelope recipient. I need a way to
> force an unqualified to address to a domain I can blackhole. I've
> got an application that feeds into these systems that will allow
> its users to enter badly formed email addresses. What I want to
> d
Viktor,
What I'm looking for is the envelope recipient. I need a way to force an
unqualified to address to a domain I can blackhole. I've got an application
that feeds into these systems that will allow its users to enter badly formed
email addresses. What I want to do is to just swallow those
On Sun, Jan 29, 2023 at 06:32:12PM +, Sean Hennessey wrote:
> That was one of my test cases. I just tried it again;
>
> $ postconf |
> grep -E
> "append_at_my|remote_header_rewrite|local_header_rewrite|inet_interfaces"
> append_at_myorigin = yes
> inet_interfaces = all
> local_header_rewri
Wietse,
That was one of my test cases. I just tried it again;
ssm-user@postfix-warming-c:~$ postconf | grep -E
"append_at_my|remote_header_rewrite|local_header_rewrite|inet_interfaces"
append_at_myorigin = yes
inet_interfaces = all
local_header_rewrite_clients =
remote_header_rewrite_domain = bl
On Sun, Jan 29, 2023 at 03:45:03PM +0200, e wrote:
> This is what the website says: "Subtle point: by default, address
> masquerading is applied only to message headers and to envelope sender
> addresses, but not to envelope recipients. This allows you to use
> address masquerading on a mail gatew
> What I'm looking for is a way to force a rewrite of ADDRESSES THAT
> DON'T HAVE AN @DOMAIN that are coming into this machine from other
> computers.
Use append_at_myorigin:
append_at_myorigin (for addresses without *domain*),
Not append_dot_mydomain:
append_dot_mydomain (for addresses
This is what the website says: "Subtle point: by default, address masquerading
is applied only to message headers and to envelope sender addresses, but not to
envelope recipients. This allows you to use address masquerading on a mail
gateway machine, while still being able to forward mail from o
13 matches
Mail list logo
