>
> Hi Jonathan, thank you.
> It helped me to eliminate some fake senders and spams, but I see your
> point.
> Yes, I'm not using postscreen as I have rspamd.
> Is there any further suggestion you might have?
>
I had a look at https://ssl-config.mozilla.org when setting up TLS things,
but I think
On Sat, Oct 26, 2024 at 12:06:12AM +0900, Nico Schottelius via Postfix-users
wrote:
> The maps/hashes that make a lot of sense on VMs/servers for avoiding
> reloading postfix, do not make much sense in the k8s/container context.
Restarts are much more disruptive that reloads, because the entire
Nico Schottelius via Postfix-users:
> As soon as the helm chart is a little bit less hacky, I'll also share it
> here for others to use.
Sounds good.
> p.s.: It seems that postfix on Alpine Linux by default does not have
> btree or sdbm support:
Consider using LMDB or CDB instead.
- CDB is opt
Viktor Dukhovni via Postfix-users:
> On Fri, Oct 25, 2024 at 01:42:40PM +1100, Viktor Dukhovni via Postfix-users
> wrote:
>
> > So we only support "postgresql:" and [not] "postgres:", because with non-URL
> > hosts, we use a legacy API to separately specify host, port, database,
> > username and
Hello .*,
a short update for those who may also be interested in running postfix
in k8s: we have a very minimal postfix setup in k8s running:
kubectl logs mx1-54b44b9b4b-z7nlt
postfix/postlog: starting the Postfix mail system
Oct 25 14:25:23 router2 postfix/postfix-script[68]: starting the Postf
On Fri, Oct 25, 2024 at 12:39:50PM +0200, Thomas Landauer via Postfix-users
wrote:
> > Rather, Postfix address rewriting makes multiple queries against
> > whatever tables are configured, using various fragments of the input
> > address as documented for virtual(5), aliases(5), canonical(5), etc.
Hi,
Rather, Postfix address rewriting makes multiple queries against
whatever tables are configured, using various fragments of the input
address as documented for virtual(5), aliases(5), canonical(5), etc.
Sorry, I still don't get it :-(
If everything is tried anyway, then what's the reason o
On Thu, Oct 24, 2024 at 6:14 PM Benny Pedersen via Postfix-users
wrote:
> smtpd_sasl_auth_enable = yes
>
> remove this in main.cf
>
> add it to port 465 587 in master.cf
>
> i will refrain for commenting on CHROOT, most users don't make it work
Thank you Benny, I already had smtpd_sasl_auth_enab
On Fri, Oct 25, 2024 at 10:52:38AM +0200, Thomas Landauer via Postfix-users
wrote:
> > > The expansion parameters `%s`, `%u` and `%d` are not working as
> > > documented:
> >
> > You're mistaken. The behaviour is exactly as documented.
>
> Sorry, but where is this documented at
> https://www.
Hi everybody,
thanks for answering! :-)
The expansion parameters `%s`, `%u` and `%d` are not working as documented:
You're mistaken. The behaviour is exactly as documented.
Sorry, but where is this documented at
https://www.postfix.org/pgsql_table.5.html ? I see explanations for each
exp
Hi
> warning: run-time library vs. compile-time header version mismatch:
> OpenSSL 3.4.0 may not be compatible with OpenSSL 3.3.0
Is this warning still relevant with OpenSSL's new versioning scheme,
where OpenSSL 3.x releases are guaranteed[1] to be ABI compatible ?
[1] https://openssl-library.
* Wietse Venema via Postfix-users :
> And for some reason mail from list.sys4.de has adds no DELIVERED-TO: header
> that would have (also) stopped this loop.
That has also been added while we were at it.
> Can that (also) be fixed? If mail is delivered with LMTP, please add
>
> -o flags=D
Mark via Postfix-users skrev den 2024-10-24 14:00:
https://www.pastebin.cz/en/p/fqcoW8Q
Anything unneeded, excessive, exaggerated, abusive or wrong there,
please?
smtpd_sasl_auth_enable = yes
remove this in main.cf
add it to port 465 587 in master.cf
i will refrain for commenting on CHROO
raf via Postfix-users:
> On Fri, Oct 25, 2024 at 11:46:38AM +1100, Viktor Dukhovni via Postfix-users
> wrote:
>
> > On Thu, Oct 24, 2024 at 07:35:26PM -0400, Wietse Venema via Postfix-users
> > wrote:
> >
> > > > Note, my cursory look at the code suggests that URI connection strings
> > > > MU
Hello,
On 24.10.2024 08:24, Viktor Dukhovni via Postfix-users wrote:
Yes, of course, as documented. TLS is off by default, this is
backwards-compatible behaviour, and Postfix aims to not "surprise"
operators with unexpected new behaviour after an upgrade. Default
settings are in part also the
15 matches
Mail list logo
