In my logs, I have thousands of:
postfix/smtpd: connect from unknown [186.225.115.62]
postfix/smtpd: disconnect from unknown [186.225.115.62]
when I watch the traffic on port 25, I see that the client tried AUTH
LOGIN and was rejected:
220 mail..com ESMTP
HELO mail..com
250 mail..com
This is not a real problem, but I am curious to understand what is
happening here.
I am running a small postfix server for personal use. One thing that I
observe over and over again is thousands of "lost connection after AUTH"
connections, such as these:
08:23:19 postfix/smtpd[4925]: connect fr
Hello list,
what would be the easiest way to block emails with no subject ?
thanks,
Thomas
could somebody please explain what these errors mean ?
postfix/smtpd[2608]: connect from
61-216-2-13.HINET-IP.hinet.net[61.216.2.13]
postfix/smtpd[2608]: SSL_accept error from
61-216-2-13.HINET-IP.hinet.net[61.216.2.13]: -1
postfix/smtpd[2608]: warning: TLS library problem:
2608:error:1408F10B:SSL
I am using Postfix as personal mailserver, with very light traffic.
I do, however, get a lot of open-relay attacks.
Often, these attacks come in bursts, tens of attacks within couple of
seconds, from the same IP.
Would this situation be a good use of "rate_limits" ?
Any suggestion how I should f
On 2015-08-23 15:40, Wietse Venema wrote:
>
> The resolver(3) system library uses connected UDP sockets. Other
> system library functions introduce their own system calls. Even if
> you think you have discovered all "normal" behavior, you can expect
> random failures, because the normal behavior d
Hello,
This is a rather specific question, but I could not think of a better
place to ask than this list.
I am running Postfix on a system with RBAC/grsecurity. In RBAC, every
Postfix process (subject) has its rules, for files which it can
read/write, ports to open, etc
For example, /usr/lib/post
On 2015-08-18 18:51, nico...@devels.es wrote:
>
> Even more useful than checking the Subject, I use header_checks to check
> some properties on attachments. In fact, I've picked Wietse's example on
> the header_checks (5) man page [1] and tuned it to my needs. This allows
> one to reject mails base
On 2015-08-06 09:08, Viktor Dukhovni wrote:
>
> You should in most cases update main.cf by setting:
>
> # Exclude obsolete weak crypto.
> #
> smtpd_tls_protocols = !SSLv2, !SSLv3
> smtpd_tls_ciphers = medium
> smtp_tls_protocols = !SSLv2, !SSLv3
> smtp_tls_ciphers = medium
On 2015-06-03 01:16, Sebastian Nielsen wrote:
> If you only are worried by backups or other copies that might come in
> the wrong hands, and not someone directly accessing the server, I would
> suggest setting up a encrypted storage in the server. Since VPS/VM in
> many times give you root access,
Hello,
my Postfix server is running as a VM in a hosted (untrusted)
environment. In theory, the data on the server (i.e. my emails) could be
on some backup tape, or copies could be lying around in the datacenter.
Some of my emails are encrypted (people send me encrypted emails) but
most are not.
On 2015-05-17 15:43, Wietse Venema wrote:
>> How can I disable chroot?
>>
>> Is it just changing the 5th column in /etc/postfix/master.cf from "-" to
>> "n" or is there more to it?
>
> This, plus "postfix reload".
>
thanks, and what about the directories dev, etc, lib, usr in
/var/spool/postfix/
Hello,
I am using Postfix 2.9.6 on Debian.
Unlike upstream, Postfix from Debian package is preconfigured to use chroot.
How can I disable chroot?
Is it just changing the 5th column in /etc/postfix/master.cf from "-" to
"n" or is there more to it?
thanks,
Thomas
13 matches
Mail list logo
