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 password:
>
>
> https://github.com/vdukho
Wietse Venema via Postfix-users:
> Viktor Dukhovni via Postfix-users:
> > On Thu, Oct 24, 2024 at 09:28:30AM -0400, Wietse Venema via Postfix-users
> > wrote:
> >
> > > Can that (also) be fixed? If mail is delivered with LMTP, please add
> > >
> > > -o flags=D
> >
> > > to the LMTP command li
Viktor Dukhovni via Postfix-users:
> On Thu, Oct 24, 2024 at 12:00:42PM -0400, Wietse Venema via Postfix-users
> wrote:
> > I have updated the hosts example, and added that the dbname field
> > is required but ignored when the hosts field specifies only URI
> > forms.
> >
> > Examples:
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
> > MUST specify a database name, the required "dbname" parameter is never
> > used to augment the URI, even if it appears to not include the
On Thu, Oct 24, 2024 at 10:24:29PM -0400, Wietse Venema via Postfix-users wrote:
> I suppose that the PostgreSQL client library code is looking up the
> username, and using that as the default database name for a connection
> URI.
Yes, something like that.
> Viktor, I don't think that Postfix's
> Perhaps a Mailman "tuneup" is possible to harden it against this sort
> of loop.
Victor an I had a look and made some changes. I hope this mail goes
through :)
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration
Invalidenstraße 120/121 | D-10115 Berlin
Tel.
Viktor Dukhovni via Postfix-users:
> Meanwhile, on the server side we could set:
>
> # Default to "may" when a cert file is configured.
> #
> smtpd_tls_security_level =
> ${smtpd_tls_chain_files ? {may} :
> {${smtpd_tls_cert_file ? {may} :
> {${smtpd_tls_
Hello Postfix fellows,
Could you please give me your feedback on my postfix (with dovecot
LMTP and virtual users in MySQL db) setup?
Here's my main.cf and master.cf contents;
https://www.pastebin.cz/en/p/fqcoW8Q
Anything unneeded, excessive, exaggerated, abusive or wrong there, please?
Many th
Viktor Dukhovni via Postfix-users:
> On Thu, Oct 24, 2024 at 09:28:30AM -0400, Wietse Venema via Postfix-users
> wrote:
>
> > Can that (also) be fixed? If mail is delivered with LMTP, please add
> >
> > -o flags=D
>
> > to the LMTP command line.
You missed that last part. Command lines are
* Wesley via Postfix-users :
> > > Perhaps a Mailman "tuneup" is possible to harden it against this sort
> > > of loop.
> >
> > Victor an I had a look and made some changes. I hope this mail goes
> > through :)
>
> Why they had a chinese string added in the subject?
Because some chinese server
On Thu, Oct 24, 2024 at 09:28:30AM -0400, Wietse Venema via Postfix-users wrote:
> Can that (also) be fixed? If mail is delivered with LMTP, please add
>
> -o flags=D
IIRC Wietse "misspoke" here, the "flags=..." argument is not a main.cf
parameter override, so this is a positional argument
I have updated the hosts example, and added that the dbname field
is required but ignored when the hosts field specifies only URI
forms.
Examples:
hosts =
postgresql://usern...@example.com/databasename?sslmode=require
...
dbname (required)
The data
On Thu, Oct 24, 2024 at 08:32:22PM +0800, Wesley via Postfix-users wrote:
> On 2024-10-24 20:13, Ralf Hildebrandt via Postfix-users wrote:
>
> Why they had a chinese string added in the subject?
A typical corporate "security" feature, the Chinese text reads "External
Mail". Sadly the same syste
On Thu, 24 Oct 2024 at 13:02, Mark via Postfix-users <
postfix-users@postfix.org> wrote:
> Hello Postfix fellows,
>
> Could you please give me your feedback on my postfix (with dovecot
> LMTP and virtual users in MySQL db) setup?
>
> Here's my main.cf and master.cf contents;
>
> https://www.pasteb
On Thu, Oct 24, 2024 at 11:33:22 -0400, Wietse Venema via Postfix-users wrote:
> And for the Postfix SMTP server, this would add two guards
> to Viktor's example:
>
> smtpd_tls_security_level =
> ${{$compatibility_level} >=level {3.10} ?
> {${built_with_tls ?
>
On Thu, Oct 24, 2024 at 01:24:07PM +0300, Eugene R via Postfix-users wrote:
> 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 u
Geert Hendrickx:
> On Thu, Oct 24, 2024 at 11:33:22 -0400, Wietse Venema via Postfix-users wrote:
> > And for the Postfix SMTP server, this would add two guards
> > to Viktor's example:
> >
> > smtpd_tls_security_level =
> > ${{$compatibility_level} >=level {3.10} ?
> > {${
Ralf Hildebrandt via Postfix-users:
> * Wesley via Postfix-users :
>
> > > > Perhaps a Mailman "tuneup" is possible to harden it against this sort
> > > > of loop.
> > >
> > > Victor an I had a look and made some changes. I hope this mail goes
> > > through :)
> >
> > Why they had a chinese stri
On Wed, Oct 23, 2024 at 06:53:32PM +0200, postfixmailing--- via Postfix-users
wrote:
> I would like change Domain name of all outgoing Email:
>
> user@domainA -> user@domainB
main.cf:
smtp_generic_maps = inline:{ {@domainA = @domainB} }
If you are relaying some SMTP email inbound a
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
> > > MUST specify a database name, the require
On Thu, Oct 24, 2024 at 12:00:42PM -0400, Wietse Venema via Postfix-users wrote:
> I have updated the hosts example, and added that the dbname field
> is required but ignored when the hosts field specifies only URI
> forms.
>
> Examples:
> hosts =
> postgresql://usern...@e
On 25/10/2024 00:35, Ralf Hildebrandt via Postfix-users wrote:
* 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
On Thu, Oct 24, 2024 at 20:00:05 +1100, Viktor Dukhovni via Postfix-users wrote:
> And this is the logic used in Postfix >= 3.10-20240612, but while you've
> upgraded to a shiny new OpenSSL, you haven't also upgraded to a shiny new
> Postfix snapshot. :-)
This is using standard Arch Linux package
On Thu, Oct 24, 2024 at 11:31:13AM +0200, Thomas Landauer via Postfix-users
wrote:
> I think I found some bugs in `postfix-pgsql` lookup, or at least the
> docs don't match the actual behavior.
>
> 1:
> The expansion parameters `%s`, `%u` and `%d` are not working as documented:
You're mistaken.
On Thu, Oct 24, 2024 at 10:50:18AM +0200, Geert Hendrickx via Postfix-users
wrote:
> > 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 O
Hi,
I think I found some bugs in `postfix-pgsql` lookup, or at least the
docs don't match the actual behavior.
1:
The expansion parameters `%s`, `%u` and `%d` are not working as documented:
If I'm just using `%s` in my query template like this:
query = SELECT foo FROM mytable WHERE foo = '%
On Thu, Oct 24, 2024 at 08:57:00AM +0200, Jaroslaw Rafa via Postfix-users wrote:
> Something bad happened to the list (?), as your message seems to be repeated
> multiple times, with Chinese characters prepended to the subject and list
> footer appended to the body multiple times.
I already (~90
On Thu, Oct 24, 2024 at 16:24:04 +1100, 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.
This could be enabled
28 matches
Mail list logo
