Both for performance and stability reasons I need to setup multiple
sqlbackends for spamassassin.
I have found some bits about the perl failover module, postgres
clustering and patches to spamassassin.
Does anyone have a working solution to share with multiple spamassassin
servers accessing multip
On 02/13/2013 09:19 AM, Robert Schetterer wrote:
>
>> you mean pure exchange ?
>> not filtering linux gateway before exchange ?
To clarify, linux gataways but mail storage is mostly done in an
exchange server.
>>
>> Best Regards
>> MfG Robert Schetterer
>>
> look
>
> http://wiki.mailscanner.info/do
Has anyone seen a tool for the integration between sa-learn and
microsoft exchange?
Ideally I would like a tool like this:
./sa-learn-wrapper --server=XXX --credentials-XXX --spam|ham
--matchingpattern=XXX
I started writing one myself a while ago but stumbled upon the fact that
the the imapserv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2013 05:13 AM, Marc Perkel wrote:
> I'm thinking about setting up to do nightly mass checks and looking for
> advice. Thanks in advance.
>
> I'm thinking about creating a virtual server that will receive a
forked copy of email that I pass th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are probably a little bit off topic here but it is an interesting
subject.
My experience is that reporting a suspected bot is only effective if the
receiver is a larger university or similair institution.
If some RBL provider wants to accept my li
On 11/15/2012 10:24 PM, John Hardin wrote:
> On Thu, 15 Nov 2012, Per-Erik Persson wrote:
>
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Is there a way to add spamassin rules without editing the config and
>> reloading the process?
>&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there a way to add spamassin rules without editing the config and
reloading the process?
To be more specific, I can set up a RBL of my own and add suspicious
servers found in the header, no problems to do that.
This can be done today with our curr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just as a note to everyone who will stumble upon similair problems.
The easiest way I know of to print certain fields in the mailheaders to
the logs is to use header_checks in postfix to print out the matching
field to the syslog which later on can be
On 03/22/2012 07:59 AM, Robert Schetterer wrote:
> Am 22.03.2012 07:51, schrieb Per-Erik Persson:
>> Since we are on the subject of adding "magic links" to email header to
>> make it easier for nontech staff to report spam.
>> I don't understand how to extract t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would be careful about giving points to a non spf enabled site.
My experience is that phishingattempts usually comes from stolen
legitimate accounts on sites with spf enabled.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment
Since we are on the subject of adding "magic links" to email header to
make it easier for nontech staff to report spam.
I don't understand how to extract the tokinzed data needed to represent
the specific email.
Have I missed some plugin that everyone else knows about?
The rest of the problem seem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/09/2012 07:55 AM, Peter Tselios wrote:
> No! Erik you are my God!
>
> That ***excactly*** what I want to do!
>
> Tell me how you did the 1st step...
>
>
> Peter
It is a pythonscript that reads the syslogs from the mailservers and
lump together t
I plan to do the following, only the first step is done at the moment.
1 Monitor the outgoing smtpservers for accounts that suddenly send
emails to many recipient that they usually don't send to and other odd
behavoures and report the queueID's. (account is hijacked and used for
spamming or a bot
13 matches
Mail list logo
