Re: [policyd-users] Throttled email will not leave queue
Matt Beckman wrote: Thanks, John. How can I determine if it is down? I opened a telnet session on port 10031 to localhost and it connected. I didn't issue any commands, though, if you have some testing suggestions. Also, the logs show that postfix-policyd connected (including showing the current threshold), then went through the process of sending the first message. The first message was sent and immediately received. The next messages all showed NOQUEUE: reject: ... Policy Rejection- Quota Exceeded. After 10 minutes, it then showed a series of connections: Jul 18 14:50:41 mailserver4 postfix/qmgr[25772]: 7DED49C0FE: from=mbeckman[ AT ]domain[ DOT ]com, size=369, nrcpt=1 (queue active) Jul 18 14:50:41 mailserver4 postfix/qmgr[25772]: 5FC0F9C225: from=mbeckman[ AT ]domain[ DOT ]com, size=369, nrcpt=1 (queue active) Jul 18 14:50:41 mailserver4 postfix/qmgr[25772]: C83E89C31F: from=mbeckman[ AT ]domain[ DOT ]com, size=370, nrcpt=1 (queue active) Jul 18 14:50:41 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56370 slots: 0 of 4096 used Jul 18 14:50:41 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56371 slots: 1 of 4096 used Jul 18 14:50:41 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56372 slots: 2 of 4096 used Jul 18 14:50:54 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56373 slots: 3 of 4096 used Jul 18 14:55:41 mailserver4 postfix/smtp[1638]: 7DED49C0FE: to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1]:10031, delay=86153, delays=85853/0.06/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) Jul 18 14:55:41 mailserver4 postfix/smtp[1639]: 5FC0F9C225: to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1]:10031, delay=86135, delays=85835/0.09/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) Jul 18 14:55:41 mailserver4 postfix/smtp[1640]: C83E89C31F: to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1]:10031, delay=86117, delays=85817/0.12/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) The messages were never sent after this point. And the messages never will be. You did not setup Policyd and Postfix correctly. (HINT: relay=[..]:10031 - policyd is not an mta, dont relay mail to it) Cami - 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
Re: [policyd-users] Throttled email will not leave queue
Wednesday, July 18, 2007, 10:31:53 PM, you wrote: MB status=deferred (conversation with 127.0.0.1[127.0.0.1] timed out while receiving the MB initial server greeting) This looks like a general problem on your server. The policyd service should always answer, disregarding the action (throttle, reject, ...). This behaviour seems unusual for me and looks erroneous. Dietmar - 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
Re: [policyd-users] Throttled email will not leave queue
Oops...and here is the post again in plaintext! Hi all, 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) 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 Any ideas? Matt - 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
Re: [policyd-users] Throttled email will not leave queue
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
Re: [policyd-users] Throttled email will not leave queue
Thanks, John. How can I determine if it is down? I opened a telnet session on port 10031 to localhost and it connected. I didn't issue any commands, though, if you have some testing suggestions. Also, the logs show that postfix-policyd connected (including showing the current threshold), then went through the process of sending the first message. The first message was sent and immediately received. The next messages all showed NOQUEUE: reject: ... Policy Rejection- Quota Exceeded. After 10 minutes, it then showed a series of connections: Jul 18 14:50:41 mailserver4 postfix/qmgr[25772]: 7DED49C0FE: from=mbeckman[ AT ]domain[ DOT ]com, size=369, nrcpt=1 (queue active) Jul 18 14:50:41 mailserver4 postfix/qmgr[25772]: 5FC0F9C225: from=mbeckman[ AT ]domain[ DOT ]com, size=369, nrcpt=1 (queue active) Jul 18 14:50:41 mailserver4 postfix/qmgr[25772]: C83E89C31F: from=mbeckman[ AT ]domain[ DOT ]com, size=370, nrcpt=1 (queue active) Jul 18 14:50:41 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56370 slots: 0 of 4096 used Jul 18 14:50:41 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56371 slots: 1 of 4096 used Jul 18 14:50:41 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56372 slots: 2 of 4096 used Jul 18 14:50:54 mailserver4 postfix-policyd: connection from: 127.0.0.1 port: 56373 slots: 3 of 4096 used Jul 18 14:55:41 mailserver4 postfix/smtp[1638]: 7DED49C0FE: to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1]:10031, delay=86153, delays=85853/0.06/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) Jul 18 14:55:41 mailserver4 postfix/smtp[1639]: 5FC0F9C225: to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1]:10031, delay=86135, delays=85835/0.09/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) Jul 18 14:55:41 mailserver4 postfix/smtp[1640]: C83E89C31F: to=[EMAIL PROTECTED], relay=127.0.0.1[127.0.0.1]:10031, delay=86117, delays=85817/0.12/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) The messages were never sent after this point. Thanks, Matt - Original message - From: John Beaver [EMAIL PROTECTED] To: policyd-users@lists.sourceforge.net Date: 7/18/2007 2:21:30 PM Subject: Re: [policyd-users] Throttled email will not leave queue 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 - 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
