Matt Beckman wrote: > I installed policyd on Postfix yesterday, and in order to configure > throttling, I have changed the settings to only allow 1 message from > a host every 2 minutes. During tests I would send out three emails, > and I would expect the first to be sent right away, followed by the > next within 2 minutes, and the last within 2 more minutes. However, > once the messages are placed in the deferred queue, they are never > sent. Here is the Postfix log message: > > Jul 18 11:09:01 mailserver4 postfix/smtp[25775]: 5FC0F9C225: > to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1]:10031, > delay=72535, delays=72235/0.04/300/0, dsn=4.4.2, status=deferred > (conversation with 127.0.0.1[127.0.0.1] timed out while receiving the > initial server greeting)
Looks as if policyd is down and postfix could not connect, which is why it is deferred. Note the error message when trying to connect to policyd. Because postfix could not connect to the policyd server, it temporarily rejects the message (dsn=4.2.2, deferred). > Jul 18 11:25:41 mailserver4 postfix/qmgr[25772]: 7DED49C0FE: > from=<[EMAIL PROTECTED]>, size=369, nrcpt=1 (queue active) > > Jul 18 11:25:41 mailserver4 postfix-policyd: connection from: > 127.0.0.1 port: 46966 slots: 0 of 4096 used > The Postfix main.cf includes these settings: > > mynetworks = 10.2.1.0/24 10.4.1.0/24 127.0.0.0/8 > > smtpd_recipient_restrictions = reject_invalid_hostname > reject_non_fqdn_sender reject_non_fqdn_recipient > reject_unauth_pipelining check_policy_service inet:127.0.0.1:10031 > permit_mynetworks reject > john ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
