> > ${config_directory}/reject1_map
> > # These hosts are whitelisted from this test only
> > 192.0.2.1 OK
> > 192.0.2.2 OK
> > # Everyone else gets this test
> > 0.0.0.0/0 reject1
>
> To make "from this test only", it would have to be "DUNNO",
> rather than
> On Dec 29, 2018, at 7:19 PM, Michael Fox wrote:
>
> ${config_directory}/reject1_map
> # These hosts are whitelisted from this test only
> 192.0.2.1 OK
> 192.0.2.2 OK
> # Everyone else gets this test
> 0.0.0.0/0 reject1
To make "from this test
Philip:
> Hi there,
>
> I want to change the retry rate for yahoo (aol.com) etc. I'm wondering
> if I can add this to the groups as below with the slower/faster delivery
> rates.
>
> Will queue_run_delay work as snail_queue_run_delay? I don't want to
> change the default for all domains just
Hi there,
I want to change the retry rate for yahoo (aol.com) etc. I'm wondering
if I can add this to the groups as below with the slower/faster delivery
rates.
Will queue_run_delay work as snail_queue_run_delay? I don't want to
change the default for all domains just a few that give me
> > Suppose I have the following general case:
> >
> > /etc/postfix/whitelist1:
> > OK
> > OK
> >
> > /etc/postfix/whitelist2:
> > OK
> >
> > How would I accomplish the following?
> >
> > smtpd_*_restrictions =
> > . . .
> > reject_[type1] . . . (except
> Since hostname based whitelists are fragile in the face of transient
> DNS failures, and many users struggle with regular expression correctness.
> A CIDR map is more appropriate here:
> Viktor.
Excellent. Thanks.
Michael
John Fawcett:
> > I would not log this for EVERY command. Especially because the
> > logged text size by far exceeds the command size (each logfile
> > record takes ~100 bytes, while the client needs to send only four
> > characters plus CRLF.
> >
> > For example, Postfix logs pipelining errors
On 29/12/2018 23:20, Wietse Venema wrote:
> Sorry, I did not recognize the diff because all whitespace was using
> UTF8 code points, and I read mail with a text editor that is optimized
> for programing, not for text processing.
>
> After fixing the whitespace:
Thanks for reviewing it further.
Sorry, I did not recognize the diff because all whitespace was using
UTF8 code points, and I read mail with a text editor that is optimized
for programing, not for text processing.
After fixing the whitespace:
> --- smtpd/smtpd.c.orig2018-12-28 13:18:55.427162049 +0100
> +++ smtpd/smtpd.c
Philippe - Forums skrev den 2018-12-29 19:55:
If "myorigin" is by default "myhostname", no need to specify
"myorigin", right?
myhostname here is localhost.$mydomain so you like to reply to a
loopback only ip without mx btw
myorigin is so system users have meaningfull email adresses that can
If "myorigin" is by default "myhostname", no need to specify "myorigin",
right?
But it's OK now.
The problem was that I don't spécify the good file to hash with
"sender_canonical_maps" option. I corrected it and now I receive an
email with the good sender name.
---
##
Philippe - Forums:
> Hi,
>
> I've made this correction:
>
> mydomain = my-domain.fr
> myhostname = my-servername.$mydomain
>
> On all of my servers.
>
> But always the same problem: my mailserver don't want to use
> "u...@my-domain.fr" as sender name, always "user@my-servername".
Seems you
On 29.12.18 18:51, Philippe - Forums wrote:
mydomain = my-domain.fr
myhostname = my-servername.$mydomain
On all of my servers.
But always the same problem: my mailserver don't want to use
"u...@my-domain.fr" as sender name, always "user@my-servername".
the important question is, how do you
Hi,
I've made this correction:
mydomain = my-domain.fr
myhostname = my-servername.$mydomain
On all of my servers.
But always the same problem: my mailserver don't want to use
"u...@my-domain.fr" as sender name, always "user@my-servername".
---
##
Philippe - Forums
Le
John Fawcett:
> Hi
>
> I'd like to make two suggestions for additional logging.
>
> The first one is to leave an explicit trace in the log when starttls is
> enforced (for example on the submission port) but the client does not
> issue STARTTLS.
There is no code in Postfix to log something that
On 29/12/2018 13:59, Patrick Ben Koetter wrote:
> * John Fawcett :
>> The first one is to leave an explicit trace in the log when starttls is
>> enforced (for example on the submission port) but the client does not
>> issue STARTTLS.
> Have you tried to set reject_plaintext_session and trace its
* John Fawcett :
> The first one is to leave an explicit trace in the log when starttls is
> enforced (for example on the submission port) but the client does not
> issue STARTTLS.
Have you tried to set reject_plaintext_session and trace its error message in
the log?
p@rick
--
[*] sys4 AG
Hi
while looking through the code for the previous post I noticed that the
return type for smtpd_sasl_auth_cmd in the comment does not correspond
to the one in the code.
John
--- smtpd/smtpd_sasl_proto.c.orig 2018-12-29 12:00:06.168219924 +0100
+++ smtpd/smtpd_sasl_proto.c 2018-12-29
Hi
I'd like to make two suggestions for additional logging.
The first one is to leave an explicit trace in the log when starttls is
enforced (for example on the submission port) but the client does not
issue STARTTLS.
The second one is to explicitly log that a protocol error has occurred.
19 matches
Mail list logo
