On Sat, Oct 01, 2022 at 09:32:49PM +, Eddie Rowe wrote:
> > You should have at least an RSA certificate (2048-bit key, not more), and
> > only
> I do not recall seeing this on the PostFix web site that discusses TLS
> settings as I struggle to setup TLS with our existing wildcard certificate.
On 10/1/22 16:16, Viktor Dukhovni wrote:
4096-bit RSA certificates mostly work, but are pointless crypto
exhibitionism, waste CPU, can run into client implementation
limitations, and so are not a good idea.
On 01.10.22 17:20, Shawn Heisey wrote:
My cert from letsencrypt is 4096 bit.
yes, Le
I do have it listening on port 465, hopefully I got the config right
so that does not allow authentication. I think I also disabled TLS
below 1.2 on port 587.
On 10/1/22 20:44, Viktor Dukhovni wrote:
What would be the use of "465" if SASL authentication is not allowed?
It is should be configu
Le 02/10/2022 à 11:51, Matus UHLAR - fantomas a écrit :
On 10/1/22 16:16, Viktor Dukhovni wrote:
4096-bit RSA certificates mostly work, but are pointless crypto
exhibitionism, waste CPU, can run into client implementation
limitations, and so are not a good idea.
On 01.10.22 17:20, Shawn Heisey
Hi postfix friends,
usually I've always found a solution when I ran into postfix
problems. Even the change from postfix 2.11 on old 14.xx
ubuntu distribution to the 20.04 LTS (forgot the postfix version)
was not a big deal, everything ran smooth.
But now, with a release-upgrade from 20.04 LTS
Hi postfix friends,
with a release-upgrade from 20.04 LTS to 22.04 LTS
there has been a postfix update to 3.6.4 and now not a single
(sub-)process of postfix starts and there's no log entry nor error
message in mail.err, the process seems to die absolutely silently.
I'm still using my old configu
On Sun, Oct 02, 2022 at 08:22:39PM +, Martin wrote:
> [... lots of prose ...]
>
> # postfix stop
> postfix/postfix-script: stopping the Postfix mail system
> Oct 02 16:24:11 derdickehase postfix/postfix-script[3222]: stopping the
> Postfix mail system
> /usr/libexec/postfix/postfix-script: 2
Viktor Dukhovni:
> On Sun, Oct 02, 2022 at 08:22:39PM +, Martin wrote:
>
> > [... lots of prose ...]
> >
> > # postfix stop
> > postfix/postfix-script: stopping the Postfix mail system
> > Oct 02 16:24:11 derdickehase postfix/postfix-script[3222]: stopping the
> > Postfix mail system
> > /us
On 10/2/22 14:42, Viktor Dukhovni wrote:
On Sun, Oct 02, 2022 at 08:22:39PM +, Martin wrote:
# postfix stop
postfix/postfix-script: stopping the Postfix mail system
Oct 02 16:24:11 derdickehase postfix/postfix-script[3222]: stopping the Postfix
mail system
/usr/libexec/postfix/postfix-scrip
Martin:
> Today I tried to install postfix 3.7.2 manually. I was enable to include
> MySQL support
> as well as TLS support. But the SASL (sasl2 / cyrus) configuration as
> given by page
> https://www.postfix.org/SASL_README.html does not work at all. When
> trying to
> send mails the answer of po
Dnia 2.10.2022 o godz. 17:23:33 Wietse Venema pisze:
>
> If fact it's worse: you can't mix Postfix programs and libraries
> from different Postfix builds, even if they are built from the same
> Postfix source.
What do you mean here by "different builds"?
Does it mean that if I build Postfix two
Dnia 2.10.2022 o godz. 17:35:23 Wietse Venema pisze:
>
> I recommend that you use a pre-built package for your OS distribution.
> That will solve the startup problem too.
I guess he did use those packages, because he wrote that he did a release
upgrade from Ubuntu 20.04 to 22.04 and then Postfix
Jaroslaw Rafa:
> Dnia 2.10.2022 o godz. 17:23:33 Wietse Venema pisze:
> >
> > If fact it's worse: you can't mix Postfix programs and libraries
> > from different Postfix builds, even if they are built from the same
> > Postfix source.
>
> What do you mean here by "different builds"?
Different c
On Sun, Oct 02, 2022 at 06:07:13PM -0400, Wietse Venema wrote:
> > With other software, usually I was pretty successful with the following
> > approach when I installed a binary package from the repository and then
> > found out that something in the program needs patching: getting the
> > corresp
Hello all,
If I am piping my mail to a program (in this case, day job's RT install), is
there some way in which I can exit that will cause a message to be bounced back
to the sender?
Or do I need a full-on milter to do this kind of rejection?
-Dan
I think that as long as the script returns the appropriate error code on
failure you don't have to do anything special; from pipe(8):
In the case of a non-zero exit status, a limited amount of command
output is logged, and reported in a delivery status notification. When
the
On Sun, Oct 02, 2022 at 03:33:52PM -0700, Dan Mahoney wrote:
> If I am piping my mail to a program (in this case, day job's RT
> install), is there some way in which I can exit that will cause a
> message to be bounced back to the sender?
>
> Or do I need a full-on milter to do this kind of rejec
Charles Sprickman:
> I think that as long as the script returns the appropriate error
> code on failure you don't have to do anything special; from pipe(8):
>
>In the case of a non-zero exit status, a limited amount of command
>output is logged, and reported in a delivery status not
18 matches
Mail list logo
