Sorry , didn't send tha last email to the list as well/
Doesn't Spamassassin have a standard routine somewhere to deteremine who an
email is for? It would seem like pretty basic stuff?
Rick
On Thu, May 22, 2008 at 11:38 AM, Theo Van Dinter <[EMAIL PROTECTED]>
wrote:
> [sending back to users
[sending back to users@ list since it's generally useful info]
On Thu, May 22, 2008 at 11:25:44AM -0400, Rick Duval wrote:
> One thing though, IF using to:addr I often get the name of the mailing list
> as opposed to the actual recipient. Is there a "clean" way to get that?
It sounds like you wan
On Thu, May 22, 2008 at 08:57:37AM -0400, Rick Duval wrote:
> Can someone point me to a list and description of vars available to plugins.
>
> I know a couple like $pms->get("to") , etc but there's also "to:addr". I'm
> looking for some sort of reference that tell me what the differences are?
$pm
Can someone point me to a list and description of vars available to plugins.
I know a couple like $pms->get("to") , etc but there's also "to:addr". I'm
looking for some sort of reference that tell me what the differences are?
Also how to just get a clean "to" address. I've notice that may mailing
On Wed, May 07, 2008 at 12:13:19PM +0530, ram wrote:
> http://wiki.apache.org/spamassassin/PluginWritingTips
> Gives plugin writing tips. But is there a beginners
> plugin-writing-howto.
I took perldoc Mail::SpamAssassin::Plugin
--
Christian Recktenwald : voice +49 711 601 2091 : Boeblin
http://wiki.apache.org/spamassassin/PluginWritingTips
Gives plugin writing tips. But is there a beginners
plugin-writing-howto.
What are requisites. I am fairly comfortable writing in perl, will that
be enough. I want to call a web api for a third party scanner within SA
Thanks
Ram
Alex Woick wrote:
> Matt Kettler schrieb am 14.12.2007 03:46:
>> 1) Plugins are somewhat new to SA (ie: 3.0.0 and higher)
>> 2) While not really hard, the work involved in making a sa plugin is
>> non-trivial
>> 3) You have to know perl.
>
> The real challenge in writing a plugin is not the coding
Matt Kettler schrieb am 14.12.2007 03:46:
1) Plugins are somewhat new to SA (ie: 3.0.0 and higher)
2) While not really hard, the work involved in making a sa plugin is
non-trivial
3) You have to know perl.
The real challenge in writing a plugin is not the coding itself. It is
the algorithm that
Jason Bennett wrote:
> Is there a central repository somewhere of custom plugins available for
> SA? I've find a few in the wiki but I was wondering if there was a site
> that had a good selection of them?
>
Well, the wiki has a list 29 of them, which I would consider more th
Is there a central repository somewhere of custom plugins available for
SA? I've find a few in the wiki but I was wondering if there was a site
that had a good selection of them?
Thanks!
J
10 matches
Mail list logo
