Gary Aitken:
> I had previously edited main.cf to set
>sendmail_path = /usr/sbin/sendmail
>setgid_group = postdrop
>
> $ sudo postfix check
> postfix: fatal: bad string length 0 < 1: mailq_path =
>
> Not sure what mailq_path should be set to... /var/spool/postfix/ ?
I apologize for the interruption in this thread, fires to put out so slow
getting back to this.
On Sunday, May 31, 2020 4:31:23 PM EDT Gary Aitken wrote:
On 5/31/20 11:34 AM, Matus UHLAR - fantomas wrote:
I'm new to postfix and trying to administer a debian
google-compute box, also new to me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Thank you very much for finding that.
I have been having the same issue for months now, and was beginning to
think I might have to resort to writing a patch to the SNI code which was
seemingly not inspecting deep enough into the certificates (i.e.
On 12 Jun 2020, at 01:11, Fourhundred Thecat <400the...@gmx.ch> wrote:
> But, on the other hand, who is still sending plaintext these days?
Nearly everyone using STARTTLS?
Someone who fails STARTTLS may then use SMTPS
> And why can't legitimate client use reasonable ciphers?
Define legitimate
On Fri, 2020-06-12 at 09:11 +0200, Fourhundred Thecat wrote:
> > On 2020-06-12 08:57, Jeroen Geilman wrote:
> > - too many errors after .* from .*
> > - warning: non-SMTP command from .*
> >
> > While these do indicate badly-behaved clients, there is no reason
> > to assume evil intent.
The
> On 2020-06-12 08:57, Jeroen Geilman wrote:
- too many errors after .* from .*
- warning: non-SMTP command from .*
While these do indicate badly-behaved clients, there is no reason to
assume evil intent.
who would send non-SMTP command to a mailserver. I usually see commands
such as GET /
Hello,
I am parsing mail logs, and banning offending IP addresses. Mostly I
match patterns such as:
too many errors after .* from .*
warning: non-SMTP command from .*
reject: RCPT from .* Recipient address rejected: User unknown in
local recipient table; .*'
I think it is safe to block
