From: Stan Hoeppner on
Joern Bredereck put forth on 7/14/2010 3:50 AM:
>
> Am 14.07.10 10:45, schrieb Stan Hoeppner:
>
>> Do you have more than one access table/type? I have 7 access tables,
>> including hash, CIDR, regexp, and PCRE. I add comments to my regexp and PCRE
>> tables to make matching REJECTs in the mail log to a given filter possible.
>> Without such comments finding the table entry that caused the rejection can be
>> very difficult, if not impossible given time constraints.
>
> Thanks for the tip with the comments. I didn't know they would show up
> in the logs. That's really the best way to tell which table entry matched.

Keep in mind those aren't strictly comments, but custom SMTP rejection text.
Thus, that text is seen on the remote MTA in the rejection message. The '#'
is actually ignored by Postfix. I put the '#' there out of habit.

Anyway, the important thing to remember is that others may see the text, so
make sure it's polite. On the flip side, if the table entry is for a chronic
pain in the butt professional snowshoe spammer, you can put a really rude
comment on that entry if you so desire. ;)

--
Stan

From: Noel Jones on
On 7/14/2010 3:59 AM, Stan Hoeppner wrote:
> Joern Bredereck put forth on 7/14/2010 3:50 AM:
>>
>> Am 14.07.10 10:45, schrieb Stan Hoeppner:
>>
>>> Do you have more than one access table/type? I have 7 access tables,
>>> including hash, CIDR, regexp, and PCRE. I add comments to my regexp and PCRE
>>> tables to make matching REJECTs in the mail log to a given filter possible.
>>> Without such comments finding the table entry that caused the rejection can be
>>> very difficult, if not impossible given time constraints.
>>
>> Thanks for the tip with the comments. I didn't know they would show up
>> in the logs. That's really the best way to tell which table entry matched.
>
> Keep in mind those aren't strictly comments, but custom SMTP rejection text.
> Thus, that text is seen on the remote MTA in the rejection message. The '#'
> is actually ignored by Postfix. I put the '#' there out of habit.
>
> Anyway, the important thing to remember is that others may see the text, so
> make sure it's polite. On the flip side, if the table entry is for a chronic
> pain in the butt professional snowshoe spammer, you can put a really rude
> comment on that entry if you so desire. ;)
>


I suggest always keeping a polite message. The possibility
that a spammer will read it is infinitely less than the
possibility that the CEO's Aunt Mindy will read it.


-- Noel Jones