And you do!! JhillOn Apr 19, 2025 9:52 PM, Wietse Venema via Postfix-users wrote:John Hill via Postfix-users:
> I was deleting file then, copy in new one.
>
> I stopped the deletion. It seems to work.
>
> I thought of writing directly to the file in the maps directory.
>
> But not sure a
John Hill via Postfix-users:
> I was deleting file then, copy in new one.
>
> I stopped the deletion. It seems to work.
>
> I thought of writing directly to the file in the maps directory.
>
> But not sure about the file locking you mentioned.
>
> I'll do some more homework.
If you use the po
I was deleting file then, copy in new one.
I stopped the deletion. It seems to work.
I thought of writing directly to the file in the maps directory.
But not sure about the file locking you mentioned.
I'll do some more homework.
thx
--john
On 4/19/25 6:10 PM, Wietse Venema via Postfix-users
John Hill via Postfix-users:
> When I manually update my lmdb access tables, adding or deleting. I see
> this message in the log: error: accept connection: Socket operation on
> non-socket.
>
> The line before this error: table
> lmdb:/etc/postfix/maps/postscreen_blacklist has changed - finishi
Am 19.04.25 um 17:51 schrieb Viktor Dukhovni via Postfix-users:
But it may be time for Postfix to no longer enable the PIX workarounds
by default.
agreed. If an operator choose a security device in front if it's MTA that strip
down SMTP like 1980,
he choose plaintext smtp only. I would hone
Just checking
Thanks
--john
On 4/19/25 12:08 PM, Viktor Dukhovni via Postfix-users wrote:
On Sat, Apr 19, 2025 at 11:11:11AM -0400, John Hill via Postfix-users wrote:
When I manually update my lmdb access tables, adding or deleting. I see this
message in the log: error: accept connection: So
On Sat, Apr 19, 2025 at 11:11:11AM -0400, John Hill via Postfix-users wrote:
> When I manually update my lmdb access tables, adding or deleting. I see this
> message in the log: error: accept connection: Socket operation on
> non-socket.
>
> The line before this error: table
> lmdb:/etc/postfix/m
On Sat, Apr 19, 2025 at 05:12:06PM +0200, Florian Piekert via Postfix-users
wrote:
> #smtp_tls_security_level = may
> smtp_tls_security_level = encrypt
>
> for a while, until just now. When I noticed that some target mx
> destination had delivery issues with this, I put the exception in my
> smt
On Sat, Apr 19, 2025 at 04:50:04PM +0200, Matus UHLAR - fantomas via
Postfix-users wrote:
> > I recommend against "recipient_canonical_maps", it rewrites a subset of
> > the message headers, (To/Cc or Resent-To/Resent-Cc), while in almost all
> > cases one should really rewrite all address-valued
Hello,
ofc NOT. But that then works.
Danke Ömer!
Am 19.04.2025 um 17:18 schrieb Ömer Güven:
mx2.neumuenster.demay
Have you tried:
neumuenster.demay
Best,
Ömer
Am 19.04.2025 um 17:15 schrieb Florian Piekert via Postfix-users
:
Dear Postfixians,
I have noticed th
>
> mx2.neumuenster.demay
Have you tried:
> neumuenster.demay
Best,
Ömer
> Am 19.04.2025 um 17:15 schrieb Florian Piekert via Postfix-users
> :
>
> Dear Postfixians,
>
> I have noticed the following.
>
> In main.cf I had
>
> #smtp_tls_security_level = may
> smtp_tls_sec
Dear Postfixians,
I have noticed the following.
In main.cf I had
#smtp_tls_security_level = may
smtp_tls_security_level = encrypt
for a while, until just now. When I noticed that some target mx destination had
delivery issues with this, I put the exception in my smtp_tls_policy_maps file,
pr
When I manually update my lmdb access tables, adding or deleting. I see
this message in the log: error: accept connection: Socket operation on
non-socket.
The line before this error: table
lmdb:/etc/postfix/maps/postscreen_blacklist has changed - finishing in
the background
It seems to work
On 18.04.25 22:00, Dmytro Alieksieiev via Postfix-users wrote:
> So you say it's better to do recipient_canonical_maps on incoming mail?
> How it will improve situation? SRS will still throw same error and
> Postfix still reply with 4xx, no?
On Sat, Apr 19, 2025 at 12:13:52PM +0200, Matus UHLAR
It works if next hop accept email inside of smtp session and then fails,
this not a problem.
--
*Best Regards,*
Dmitriy Alekseev
DevOps Engineer
On Sat, 19 Apr 2025, 16:12 Benny Pedersen via Postfix-users, <
postfix-users@postfix.org> wrote:
> Dmitriy Alekseev via Postfix-users skrev den 2025-0
Dmitriy Alekseev via Postfix-users skrev den 2025-04-19 15:59:
Reverse path is must to be in place to properly process bounces back
if due to any reason dst will fail to get email, and that's all.
this is working if hosts does not accept and later bounces
SRS is not helpfull there
__
Reverse path is must to be in place to properly process bounces back if due
to any reason dst will fail to get email, and that's all.
--
*Best Regards,*
Dmitriy Alekseev
DevOps Engineer
On Sat, 19 Apr 2025, 15:40 Viktor Dukhovni via Postfix-users, <
postfix-users@postfix.org> wrote:
> On Sat, A
On Sat, Apr 19, 2025 at 01:31:28PM +0200, Dmitriy Alekseev wrote:
> I do not rewrite any headers and have 0 intention to do so as it break
> existing dkim and arc signatures. No modification except envelopes needed.
Therefore, avoid 'recipient_canonical_maps', and if you need envelope
sender rewri
I do not rewrite any headers and have 0 intention to do so as it break
existing dkim and arc signatures. No modification except envelopes needed.
--
*Best Regards,*
Dmitriy Alekseev
DevOps Engineer
On Sat, 19 Apr 2025, 13:10 Viktor Dukhovni via Postfix-users, <
postfix-users@postfix.org> wrote:
On Sat, Apr 19, 2025 at 12:13:52PM +0200, Matus UHLAR - fantomas via
Postfix-users wrote:
> On 18.04.25 22:00, Dmytro Alieksieiev via Postfix-users wrote:
> > So you say it's better to do recipient_canonical_maps on incoming mail?
> > How it will improve situation? SRS will still throw same error
On 18/04/2025 20:06, Matus UHLAR - fantomas via Postfix-users wrote:
I remember now when I implemented SRS, I configured separate postfix
instance for outgoing mail. This is the postfix issue described in
postsrs docs: canonical maps are processed when mail is being
received.
Yep, I have 2 s
21 matches
Mail list logo
