Thank you Cami; now this issue it's fixed but a problem remains: policyd seems does not work.
I look at maillog file and I see that policyd is charged correctly: [....] Aug 27 16:39:38 mail policyd: config: triplet timeout> 240 Aug 27 16:39:38 mail policyd: config: optin/optout> 0 Aug 27 16:39:38 mail policyd: config: optin all in> 0 Aug 27 16:39:38 mail policyd: config: triplet auth timeout> 2592000 Aug 27 16:39:38 mail policyd: config: triplet unauth timeout> 172800 Aug 27 16:39:38 mail policyd: Aug 27 16:39:38 mail policyd: ---- SENDER THROTTLE CONFIG ---- Aug 27 16:39:38 mail policyd: config: sender throttle> 0 Aug 27 16:39:38 mail policyd: config: sender throttle sasl> 0 Aug 27 16:39:38 mail policyd: config: sender throttle host> 1 Aug 27 16:39:38 mail policyd: config: postfix_sender_quota_exceeded> action=defer_if_permit Policy Rejection- Quota Exceeded. Aug 27 16:39:38 mail policyd: config: quota_exceeded_temp_reject> 1 Aug 27 16:39:38 mail policyd: config: postfix_bad_size> action=reject Policy Rejection- Message size too big. Aug 27 16:39:38 mail policyd: config: sender msglimit> 512 Aug 27 16:39:38 mail policyd: config: sender quotalimit> 250000000 Aug 27 16:39:38 mail policyd: config: sender timelimit> 3600 Aug 27 16:39:38 mail policyd: config: sender msgsize> 10240000 Aug 27 16:39:38 mail policyd: config: sender expire inactive> 2678400 Aug 27 16:39:38 mail policyd: config: sender throttle autoblacklisting> 0 Aug 27 16:39:38 mail policyd: config: sender throttle autoblacklist number> 3 Aug 27 16:39:38 mail policyd: config: sender throttle autoblacklist expire> 21600 Aug 27 16:39:38 mail policyd: Aug 27 16:39:38 mail policyd: ---- RECIPIENT THROTTLE CONFIG ---- Aug 27 16:39:38 mail policyd: config: recipient throttle> 0 Aug 27 16:39:38 mail policyd: config: recipient msglimit> 64 Aug 27 16:39:38 mail policyd: config: recipient timelimit> 3600 Aug 27 16:39:38 mail policyd: config: recipient expire inactive> 2678400 Aug 27 16:39:38 mail policyd: config: postfix_recipient_quota_exceeded> action=defer_if_permit Policy Rejection- Quota Exceed ed. Aug 27 16:39:38 mail policyd: config: quota_exceeded_temp_reject> 1 Aug 27 16:39:38 mail policyd: Aug 27 16:39:38 mail policyd: starting policyd v1.81 Aug 27 16:39:38 mail policyd: DEBUG: fd: 0: rlimit: max: 4097 cur: 4097 Aug 27 16:39:38 mail policyd: connecting to mysql database: 127.0.0.1 Aug 27 16:39:38 mail policyd: connected.. [...] But if I send some mail to a mailbox in my SMTP, policyd not shows any activity: Aug 27 16:44:02 mail policyd: connected.. Aug 27 16:44:04 mail postfix/smtpd[22457]: disconnect from nf-out-0910.google.com[64.233.182.190] Aug 27 16:44:25 mail postfix/smtpd[22467]: connect from nf-out-0910.google.com[64.233.182.185] Aug 27 16:44:25 mail postfix/smtpd[22467]: A5A55D5002F: client=nf-out-0910.google.com[64.233.182.185] Aug 27 16:44:25 mail postfix/cleanup[22463]: A5A55D5002F: message-id=<[EMAIL PROTECTED]> Aug 27 16:44:25 mail postfix/qmgr[22268]: A5A55D5002F: from=<[EMAIL PROTECTED]>, size=1846, nrcpt=1 (queue active) Aug 27 16:44:33 mail postfix/smtpd[22474]: connect from tartarus[127.0.0.1] Aug 27 16:44:33 mail postfix/smtpd[22474]: 9771FD5003B: client=tartarus[127.0.0.1] Aug 27 16:44:33 mail postfix/cleanup[22463]: 9771FD5003B: message-id=<[EMAIL PROTECTED]> Aug 27 16:44:33 mail postfix/qmgr[22268]: 9771FD5003B: from=<[EMAIL PROTECTED]>, size=2457, nrcpt=1 (queue active) Aug 27 16:44:33 mail postfix/smtpd[22474]: disconnect from tartarus[127.0.0.1] Aug 27 16:44:33 mail postfix/smtp[22465]: A5A55D5002F: to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1]:10024, delay =8.1, delays=0.36/0/0.01/7.7, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 9771FD5003B) Aug 27 16:44:33 mail postfix/qmgr[22268]: A5A55D5002F: removed Aug 27 16:44:33 mail postfix/virtual[22476]: 9771FD5003B: to=<[EMAIL PROTECTED]>, relay=virtual, delay=0.06, delays=0. 02/0/0/0.04, dsn=2.0.0, status=sent (delivered to maildir) Aug 27 16:44:33 mail postfix/qmgr[22268]: 9771FD5003B: removed As you can see, the sender (gmail account) is not controlled by policyd and the mail is delivered to recipient (opengea.org account, the SMTP which has policyd apparently on) without any controls. ¿?¿?¿ I use amavis-new... and I don't know if this application can interrupt some process (I hope not indeed amavisd-new works currently in 10024, 10025 and 10026 ports and policyd works in 10031). -- Thanks, Jordi Espasa Clofent ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
