How to tell wich url that triggered in SURBL?

[Ken A]

Ah, Sorry. I think the header format is hard coded in the MailScanner 
perl. The long report is more complex and you might be asking for 
trouble or security issues trying to stuff it into a header folding the 
lines, etc..
Ken


Alex Broens wrote:
> Ken
> 
> I'm referring to header reports
> 
> from what I see, Denis' clear-report-template  and additions also apply 
> to the msg report sent to the user but not to header reporting.
> 
> or have I missed something again?
> 
> thanks
> 
> Alex
> 
> On 9/21/2006 6:22 PM, Ken A wrote:
>>
>> In your MailScanner/reports/[lang]/ directory, locate your spam report 
>> file and change $fullspamreport to $longspamreport and you'll get the 
>> description of the rules hit as well as the URIs hit.
>>
>> Ken A.
>> Pacific.Net
>>
>>
>> Furnish, Trever G wrote:
>>>> -----Original Message-----
>>>> From: mailscanner-bounces at lists.mailscanner.info 
>>>> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Martin
>>>> Sent: Monday, September 11, 2006 4:04 AM
>>>> To: mailscanner at lists.mailscanner.info
>>>> Subject: Re: How to tell wich url that triggered in SURBL?
>>>>
>>>> Alex Broens wrote:
>>>>
>>>>> Seems its a MailScanner special.
>>>>> (makes it hard to debug when you have a FP but that's the way it is)
>>>> Humm.. but how do people define in the configs that the actual 
>>>> domain should be listed in the header of the message? All i want is 
>>>> SA or MS to add the following to my header:
>>>>
>>>> Contains an URL listed in the JP blocklist
>>>>  >>    *      [URIs: site.com]  < ----- This line
>>>>
>>>> Today i only see the actual points, but i want to know what site 
>>>> triggered those points. How can i do that?
>>>
>>> Unless I'm misunderstanding what Alex was trying to tell you, he meant
>>> that you can't do that via MailScanner+SpamAssassin.  If you're seeing
>>> signs that people are doing that using SA on the SA lists, then they're
>>> probably using SpamAssassin without using MailScanner.
>>>
>>> MailScanner uses SpamAssassin as a set of perl libraries, which is very
>>> different -- much of what you might read on the SA lists or in the SA
>>> manual pages doesn't apply.
>>>
> 
>