Discussion:
doveadm penalty: who is 0.0.0.0?
Peer Heinlein
2014-09-23 12:31:05 UTC
Permalink
Using doveadm penalty I just noticed a penalty for 0.0.0.0.

Is this Postfix querying the auth-socket for his SASL-requests?

I tried adding 0.0.0.0 to login_trusted_networks, but that doesn't help.

Peer
--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

http://www.heinlein-support.de

Tel: 030 / 405051-42
Fax: 030 / 405051-19

Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht
Berlin-Charlottenburg,
Gesch?ftsf?hrer: Peer Heinlein -- Sitz: Berlin

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://dovecot.org/pipermail/dovecot/attachments/20140923/e74f4563/attachment.sig>
Ralf Hildebrandt
2014-09-25 11:12:23 UTC
Permalink
Post by Peer Heinlein
Using doveadm penalty I just noticed a penalty for 0.0.0.0.
Is this Postfix querying the auth-socket for his SASL-requests?
Maybe a portscan? Sometimes they turn up as 0.0.0.0
--
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstra?e 15, 81669 M?nchen

Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
Timo Sirainen
2014-09-26 21:28:27 UTC
Permalink
Post by Peer Heinlein
Using doveadm penalty I just noticed a penalty for 0.0.0.0.
Is this Postfix querying the auth-socket for his SASL-requests?
Most likely. 0.0.0.0 would in any case mean "unknown". It shouldn't show up in penalty though..
Loading...