Package: postgrey Version: 1.31-3 Severity: minor Hello, some of my postgrey log entries do not contain a client_name= setting: ----- Mar 9 17:02:12 m26s25 postgrey[452]: action=greylist, reason=new, client_address=92.83.159.32, [email protected], [email protected] Mar 9 17:43:22 m26s25 postgrey[452]: action=greylist, reason=new, client_address=189.0.133.192, [email protected], [email protected] Mar 9 17:59:34 m26s25 postgrey[452]: action=greylist, reason=new, client_address=190.232.78.128, [email protected], [email protected] Mar 9 17:59:59 m26s25 postgrey[452]: action=greylist, reason=new, client_address=190.232.78.128, [email protected], [email protected] Mar 9 18:00:18 m26s25 postgrey[452]: action=greylist, reason=new, client_address=190.232.78.128, [email protected], [email protected] ----- I guess this caused by either missing reverse DNS (92.83.159.32, 190.232.78.128) or lame nameservers.
Since the logcheck rules list client_name= as mandatory parameter every sngle one of these entries ends up in my warning e-mail. Replacing " client_name=.+," with "( client_name=.+,)?" in both ignore.d.server/postgrey and violations.ignore.d/postgrey should do the trick. I am going to apply this chane locally and wait for tomorrow's logcheck. thanks, cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
