On Tue, Mar 29, 2022 at 09:50:43PM +0200, Jack Raats wrote:
> I have a postfix server on an ip4 and ipv6 adres.
> I'm using clamav-milter for virus scanning. Do I have to use 2 milters,
> one for ipv4 and one for ipv6 or can I use only one milter?
One is enough.
--
Viktor.
Hi,
I have a postfix server on an ip4 and ipv6 adres.
I'm using clamav-milter for virus scanning. Do I have to use 2 milters,
one for ipv4 and one for ipv6 or can I use only one milter?
Thanks
Jack
No. Thanks. It was a long-leftover 32-bit binary in the wrong place.
Sent from my iPhone
> On Mar 29, 2022, at 4:23 AM, Wietse Venema wrote:
>
> Wietse
Wietse Venema previously_wrote on Mon-28-Mar 22 12:00AM
> external name "Postfix". "post" was a different word for "mail",
> and "fix" was for Sendmail, the inspiration for my efforts.
It is a much cooler sounding name now that its decoded.
But in retrospect the meaning is pretty obvious 臘
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Just going to say I banged my head against this wall for months on end -
every time I updated certificates (using letsencrypt it's pretty
frequent) postfix showed the new certs as active - but external tests
still showed certs from over a year
On Monday, March 28, 2022, 12:01:58 AM GMT+2, Wietse Venema
wrote:
| the inspiration for my efforts.
Thanks for your efforts, Wietse... and for all your support in the list!!!
Regards..
Pete.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey,
On Sun, 2022-03-27 at 10:59 +0200, Benny Pedersen wrote:
> funny from myside: it fixes all known sendmail bugs :)
> it did not take m4 configure from it
How plebeian, you used m4 to configure sendmail. ️
In all my years administering
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 2022-03-27 at 09:08 +0530, Amarjeet Anand wrote:
> What’s the story behind choosing the name as “Postfix”?
As with all children it's what it's parents chose to call it
- --
Nikolai Lusan
-BEGIN PGP SIGNATURE-
Roger Klorese:
> CentOS 7.9 with SELinux off.
>
> Log shows:
>
> Mar 28 11:29:16 divine postfix/pipe[2685]: 21FE73000171E:
> to=, relay=sympa,
> delay=599, delays=599/0.06/0/0.04, dsn=4.3.0, status=deferred (temporary
> failure. Command output: pipe: fatal: pipe_command: execvp
>
On 2022-03-29 Istvan Prosinger wrote:
> the documentation says:
>
> "Reject the request when the HELO or EHLO hostname has no DNS A or MX
> record"
>
> I'm trying to understand the "or" between the "A" and "MX" words -
> will this test reject the transport when any of those records are
>
Hi guys,
the documentation says:
"Reject the request when the HELO or EHLO hostname has no DNS A or MX
record"
I'm trying to understand the "or" between the "A" and "MX" words - will
this test reject the transport when any of those records are missing, or
when the propagated HELO/EHLO
11 matches
Mail list logo