trading fours:
> I am seeing the subjected error for a small percentage of messages, and
> then those message stay in the deferred queue.
>
> from the log:
> postfix/local[1124]: warning: unexpected protocol delivery_request_protocol
> from private/bounce socket (expected: delivery_status_protocol
On 2023-01-01 19:54, Wietse Venema wrote:
Viktor Dukhovni:
On Sun, Jan 01, 2023 at 05:03:27PM +0100, Jesper Dybdal wrote:
...
(I seem to remember that there was a thread here about a similar subject
some time ago, but I can't find it now.)
Did you mean https://www.postfix.org/postconf.5.ht
On 1/1/23 12:33, Bill Cole wrote:
also, private IP ranges should be excluded from checking in DNS lists.
Yes, but non sequitur...
... as your server connects to 192.168.1.160, I assume that servers
sees your address to be from private range too.
Nope, the connecting address is shown in the
I am seeing the subjected error for a small percentage of messages, and
then those message stay in the deferred queue.
from the log:
postfix/local[1124]: warning: unexpected protocol delivery_request_protocol
from private/bounce socket (expected: delivery_status_protocol)
postfix/local[1124]: war
On 2023-01-01 at 13:01:18 UTC-0500 (Sun, 1 Jan 2023 19:01:18 +0100)
Matus UHLAR - fantomas
is rumored to have said:
On 1/1/23 07:23, Forums wrote:
*/postfix/smtp[23430]: 4972423BAF: to=/**/,
relay=192.168.1.160[192.168.1.160]:25, delay=0.99,
delays=0.06/0.03/0.8/0.1, dsn=5.7.1, status=bounced
On Sun, Jan 01, 2023 at 01:54:12PM -0500, Wietse Venema wrote:
> > > (I seem to remember that there was a thread here about a similar subject
> > > some time ago, but I can't find it now.)
>
> Did you mean https://www.postfix.org/postconf.5.html#local_login_sender_maps
> This is available in Pos
Viktor Dukhovni:
> On Sun, Jan 01, 2023 at 05:03:27PM +0100, Jesper Dybdal wrote:
>
> > I use reject_authenticated_sender_login_mismatch to control which
> > envelope sender addresses SASL clients can use.? That works just fine.
> >
> > Is there a similar way to control which envelope sender add
On Sun, Jan 01, 2023 at 05:03:27PM +0100, Jesper Dybdal wrote:
> I use reject_authenticated_sender_login_mismatch to control which
> envelope sender addresses SASL clients can use. That works just fine.
>
> Is there a similar way to control which envelope sender addresses can be
> used by whic
On 1/1/23 07:23, Forums wrote:
*/postfix/smtp[23430]: 4972423BAF: to=/**/,
relay=192.168.1.160[192.168.1.160]:25, delay=0.99,
delays=0.06/0.03/0.8/0.1, dsn=5.7.1, status=bounced (host
192.168.1.160[192.168.1.160] said: 554 5.7.1 Service unavailable;
Sender address [no-re...@mehl-family.fr] blo
On 1/1/23 07:23, Forums wrote:
*/postfix/smtp[23430]: 4972423BAF: to=/**/,
relay=192.168.1.160[192.168.1.160]:25, delay=0.99,
delays=0.06/0.03/0.8/0.1, dsn=5.7.1, status=bounced (host
192.168.1.160[192.168.1.160] said: 554 5.7.1 Service unavailable; Sender
address [no-re...@mehl-family.fr] blo
I use reject_authenticated_sender_login_mismatch to control which
envelope sender addresses SASL clients can use. That works just fine.
Is there a similar way to control which envelope sender addresses can be
used by which system user by calling sendmail(1)?
(I seem to remember that there wa
Hello,
I have an issue with Postfix after a new OS installation (64bits instead
of 32bits).
OS : raspi-os (Debian for Raspberry Pi, my mailserver run on a Raspberry Pi)
What I've done:
- OS 64bits installation
- Softwares installation (Dovecot, Postfix, Clamav, Spamassassin,
OpenDKIM, SPF
12 matches
Mail list logo
