Noel Jones:
> With postfix-2.9-RC2 on FreeBSD 8.1
>
> I assume the "Operation not permitted" message is an artifact of
> writing to a disconnected socket or such and nothing to worry
> about? Only happens on a small percentage of connections rejected
> by postscreen.
Network writes can fail for all kinds of reasons, and therefore
postscreen reports only unusual errors. EPERM After writing to a
socket is unusual, because UNIX systems don't change read/write
permissions *after* a file handle is created.
Looking over the last year of logs I see 'Operation not permitted'
logged by FreeBSD 8.2 around the time when I had to renumber my
IPv6 subnet.
Sep 5 14:25:24 spike postfix/smtp[97543]: connect to
mail.cloud9.net[2604:8d00:0:1::3]:25: Operation not permitted
Sep 5 15:12:28 spike postfix/smtp[1096]: connect to
mail.cloud9.net[2604:8d00:0:1::3]:25: Operation not permitted
Sep 5 15:12:28 spike postfix/smtp[1096]: connect to
mail.cloud9.net[2604:8d00:0:1::4]:25: Operation not permitted
Other than those, I have no record of EPERM errors from the FreeBSD
network stack.
Wietse
> Jan 25 05:01:39 mgate3 postfix/postscreen[47863]: CONNECT from
> [59.183.173.6]:20919 to [192.168.70.43]:25
> Jan 25 05:01:45 mgate3 postfix/postscreen[47863]: DNSBL rank 10 for
> [59.183.173.6]:20919
> Jan 25 05:07:04 mgate3 postfix/postscreen[47863]: COMMAND TIME LIMIT
> from [59.183.173.6]:20919
> Jan 25 05:07:04 mgate3 postfix/postscreen[47863]: warning: write
> [59.183.173.6]:20919: Operation not permitted
> Jan 25 05:07:04 mgate3 postfix/postscreen[47863]: DISCONNECT
> [59.183.173.6]:20919
