Discussion:
Spamd does not Greylist
Thomas Laus
2017-07-04 12:38:29 UTC
Permalink
List:

I recently installed OpenBSD 6.1 on an Amazon AWS EC2 instance. I used
the default configuration and just have the "-v" flag set in
rc.conf.local for spamd. I see various smtp connections in the daemon
log but was surprised to see the spamdb entry after the initial
connection was showing spamd-white and was not greylisted waiting for
the next connection timeout to expire. This OpenBSD 6.1 instance is at
syspatch #10.

Jul 3 19:07:01 mail spamd[13115]: 203.70.57.17: connected (1/0)
Jul 3 19:07:12 mail spamd[13115]: 203.70.57.17: disconnected after 11
seconds.
Jul 3 19:10:13 mail spamd[13115]: 101.99.15.195: connected (1/0)
Jul 3 19:10:24 mail spamd[13115]: 101.99.15.195: disconnected after 11
seconds.
Jul 3 19:13:49 mail spamd[13115]: 92.79.129.204: connected (1/0)
Jul 3 19:14:00 mail spamd[13115]: 92.79.129.204: disconnected after 11
seconds.
Jul 3 19:17:05 mail spamd[13115]: 113.160.112.52: connected (1/0)
Jul 3 19:17:16 mail spamd[13115]: 113.160.112.52: disconnected after 11
seconds

All 4 of these addresses were the initial connection after starting
spamd and immediately were whitelisted by spamdb.

Has something changed in the spamd configuration in OpenBSD 6.1? It has
been working many years for me on other hosts. This is my only AWS-EC2
instance and all of my other mailservers are running in local hardware.

Tom
--
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF
Loading...