On 3/04/19 17:13, Viktor Dukhovni wrote:
>
>
> It seems you're in a sardonic mood, ... best to not go there.
If I gave that impression, I apologize.
All I was trying to say is that, because of the bug, you may be more
likely to run out of disk space by trying to send to bona fide domains
lik
On 3/04/19 01:16, Wietse Venema wrote:
> I prefer to remove the ability to disable safety mechanisms.
And in your initial response, you also wrote:
> Probably better to not allow a limit-less smtp_mx_address_limit,
> as it makes Postfix vulnerable to resource exhaustion attack.
Both respons
On 2/04/19 13:21, Wietse Venema wrote:
> Probably better to not allow a limit-less smtp_mx_address_limit,
> as it makes Postfix vulnerable to resource exhaustion attack.
>
> Wietse
>
Fair enough, but then the docs for smtp_mx_address_limit ought to be
changed to remove the "or zero (no
seems to have been introduced on 20170505, and
in any case, smtp_addr.c has a timestamp of Dec 27, 2017.
If this has been reported already, I apologize. I did a quick search
only and came up empty. If I missed it, this "bug report" becomes a "bug
reminder" :-)
It goes without saying, I hope, that the other client parameters in
main.cf have to be set to the proper values to trigger the bug (e.g.
smtp_balance_inet_proto = yes).
Luc Pardon
On 05-09-18 18:18, Wietse Venema wrote:
> Luc Pardon:
>> The first question is obviously: can we disallow symlinks to the outside
>> world by definition? I'd say the answer is yes, but $(whoami) ?
>
> Here is some background on pathname safety.
>
Thanks for that.
On 05-09-18 15:04, Luc Pardon wrote:
> The Q&D shell scriptlet below my sig would probably do the trick
>
> ==
> #!/bin/sh
>
> # This would not be needed if integrated into postfix-script:
> BASE=$(postconf -hx config_directory | sed
On 05-09-18 13:26, Wietse Venema wrote:
> Luc Pardon:
>> Hello,
>>
>> Running Postfix 3.3.1 under Linux, postfix-script produces pointless
>> warnings if/when there are symbolic links in or below $config_directory.
>
> The problem is that the symlink may po
Hello,
Running Postfix 3.3.1 under Linux, postfix-script produces pointless
warnings if/when there are symbolic links in or below $config_directory.
1. I installed (CA root) certificates in a subdir of /etc/postfix and
rehash with "openssl rehash . This will of course create a
symlink to each cer
(Please note that I also changed the remainder of the subject line to
try and avoid further confusion.)
On 06-08-18 20:48, Wietse Venema wrote:
> Luc Pardon:
>> The only "problem" that I am trying to solve is how to detect that the
>> other side is telling me to re-send
On 26-07-18 17:19, Matus UHLAR - fantomas wrote:
> Anyway, whole point of this discussion that working around problems by
> violating RFC and re-sending hardly (5xx) refused mail through an ISP is
> not
> way to go.
No, the "whole point" of the discussion is *not* that I want to work
around jus
First off, thanks for reading and replying to the real question, as always.
> And if they were to accept your email, they may very well deliver
> your message to the spam folder, because you are sending from an
> inappropriate IP address.
True, but there are many _other_ reasons why "they" may
Hello,
I've been running a small volume Postfix mail server on a fixed IP for
15+ years or so.
Recently, my provider forced me from ADSL (being phased out here) to
VDSL, and I now find myself sending mail from a "dynamic" IP address...
As expected, some destinations refuse to accept my outgoing
12 matches
Mail list logo
