e a warning about the possible issue under Unicode locales.
--
Jim Garrison
j...@acm.org
On 12/23/22 19:06, raf wrote:
On Fri, Dec 23, 2022 at 01:14:26PM -0800, Jim Garrison wrote:
[snip]
Not relevant to your problem, but the above says that
only ipv4 is used but your config includes ipv6
addresses. You might want to delete it (and default to
"all"), or remove the ipv6
On 12/23/22 17:24, Wietse Venema wrote:
You should also include "postconf -P" for parameter settings in
master.cf.
Wietse
Not much there...
$ postconf -P
relay/unix/syslog_name = postfix/$service_name
--
Jim Garrison
j...@acm.org
I have Postfix running inside a private LAN as an outgoing relay via
GMail (no incoming Internet connections). I have two goals
1. Relay only to one specific domain
2. Accept relay from only one specific LAN client
So I configured the following (complete postconf -n appended below):
ands=[0123]
This would trigger on any SMTP session that disconnected before
processing a valid RCPT command. With a suitable maxretry setting (say
5) this would stop most probes.
The Postfix question: Is there a reason this is a bad idea, and could it
cause legitimate MTAs to be banned?
--
Jim
word when it changed on the server.
It seems the error message always contains the base64 encoding of
"Password:" regardless of the actual userid/password.
Anybody know why the error message displays this (base64 encoded)?
--
Jim Garrison
j...@acm.org
On 5/28/2022 7:07 PM, Viktor Dukhovni wrote:
On Sat, May 28, 2022 at 05:11:22PM -0700, Jim Garrison wrote:
Foreground saslauthd command, including debug output from
successful testsaslauthd but no log entries corresponding to the
immediately above extract from the Postfix log:
$ sudo
crease the debug level in Postfix's
interaction with saslauthd?
--
Jim Garrison
j...@acm.org
base64]
535 5.7.8 Error: authentication failed: bad protocol / cancel
QUIT
DONE
--
Jim Garrison
j...@acm.org
.
Otherwise, indeed the mbox file format hasn't changed in decades.
Thanks to all who have responded. I'll be performing the cutover
later this weekend.
--
Jim Garrison
j...@acm.org
host for each user? I.e. is the
mbox format used still the same, or will I run into incompatibilities?
If a conversion or format upgrade is necessary, what is involved?
Thanks
--
Jim Garrison
j...@acm.org
On 7/29/2021 12:34 AM, Matus UHLAR - fantomas wrote:
On 28.07.21 12:54, Jim Garrison wrote:
This means that Postfix now starts up before the network is completely
up, and systemd's DNS resolution hack (systemd-resolved.service),
finding no interfaces up yet, resolves 'localhost' to 127.0.0.2
On 7/28/2021 1:49 PM, Wietse Venema wrote:
Jim Garrison:
For anyone encountering this error, I've traced it to a regression of
a very old bug relating to systemd service ordering dependencies.
In my case, OS is CentOS Linux release 8.4.2105
postfix-3.5.8-1.el8.x86_64
Since a recent update
store the "After=" dependency on network-online.target
--
Jim Garrison
j...@acm.org
a positive result. Is this possible?
-- Jim Garrison
to configure Postfix to not even try the one
reluctant MX host for that domain?
--
Jim Garrison ([EMAIL PROTECTED])
PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88
or incompatibilities between those two versions?
--
Jim Garrison ([EMAIL PROTECTED])
PGP Keys at http://www.jhmg.net RSA 0x04B73B7F DH 0x70738D88
17 matches
Mail list logo
