Bill Cole:
> On 15 Mar 2021, at 12:17, Viktor Dukhovni wrote:
>
> > You've enabled SASL with dovecot as a backend. You could limit this
> > to
> > port 587 (enable SASL via master.cf only for the submission service),
> > and require TLS there. It'll probably still get probed. That's life
> >
On 15 Mar 2021, at 12:17, Viktor Dukhovni wrote:
You've enabled SASL with dovecot as a backend. You could limit this
to
port 587 (enable SASL via master.cf only for the submission service),
and require TLS there. It'll probably still get probed. That's life
on the public Internet.
Not
On Mon, Mar 15, 2021 at 03:24:19PM +0100, Jens Hoffrichter wrote:
> I can see in the log file that the trivial rewrite resolves the next
> hop correctly from the extra transport map, and sends that back to the
> smtpd, but the information is ignored when it comes to the smtp
> process.
Transport
On Mon, Mar 15, 2021 at 09:07:43AM -0700, Stephen Satchell wrote:
> Problem: someone is probing my Ubuntu 20.04 LTS based mail server.
> Along with SSH attacks (now mitigated) I had a number of log messages
> saying auth failures in Dovecot. When I traced packets generating these
> messages,
Problem: someone is probing my Ubuntu 20.04 LTS based mail server.
Along with SSH attacks (now mitigated) I had a number of log messages
saying auth failures in Dovecot. When I traced packets generating these
messages, I found that the packets were being directed to 25/tcp -- Postfix.
I
Hi!
I'm trying to implement a relatively esoteric use case right now,
where all the mails I sent to postfix on a specific smtp daemon
configured in the master.cf to a different nexthop than the regular
mail going through the services. But this should only occur for a list
of domains (my internal
