Your right, my ideas are usually too ahead of their time, usually by around
20 minutes ... we were Storm braining :P
On a serious note, it was an idea for an alert/fail safe when you forget or
do something by mistake and the system to kick in automatically. Maybe
somebody else can better it.
--
That is quite funny.
That's why I would use webmaster accounts, or email that is system
generated, to avoid such interesting occurrences
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff
(Lists)
Sent: Sunday, June 01, 2003 2:40 AM
To: [EMAIL
> To make this closer to a failsafe, we can have your program check
> the weight already assigned to the configured match, if its above X
> weight, it would trigger a configurable alert (off site email, event
> log, log file...etc)
This seems like an awful lot of round-the-clock processing
> To make this closer to a failsafe, we can have your program check the
weight
> already assigned to the configured match, if its above X weight, it would
> trigger a configurable alert (off site email, event log, log file...etc)
But what about this scenario: [EMAIL PROTECTED] sends a message to
[
Glad to know im not way too off in my suggestions ...
To make this closer to a failsafe, we can have your program check the weight
already assigned to the configured match, if its above X weight, it would
trigger a configurable alert (off site email, event log, log file...etc)
-Original Messa
> Not sure how doable is this or if it can be exploited by spammers, but as
a
> fail safe, cant we setup a certain FROM and TO email accounts on a domain
> which we know any email going between those two accounts (from doesn't
have
> to be an email account on server) is 99.99% never spam?
>
> This
> OUCH
>
> How did I post this to the list? This was to be sent to Scott only...
>
> OUCH OUCH OUCH... Forgot to set off my reply receipt :'(
>
> 5000 responses later... So sorry folks ...
>
> OUCH OUCH
And to the wrong list non-the-less.
And with the wrong subject line non-the-less.
50 las
Not sure how doable is this or if it can be exploited by spammers, but as a
fail safe, cant we setup a certain FROM and TO email accounts on a domain
which we know any email going between those two accounts (from doesn't have
to be an email account on server) is 99.99% never spam?
This way if we
OUCH
How did I post this to the list? This was to be sent to Scott only...
OUCH OUCH OUCH... Forgot to set off my reply receipt :'(
5000 responses later... So sorry folks ...
OUCH OUCH
Regards,
Kami
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ka
Hi Scott:
I ran it and it appears to be working. When ran manually the report shows
that it has detected an infected file.
I also attached the virus.cfg for your review if possible.
Regards,
Kami
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of R. Scott
Andy,
I'll respond briefly. Anything else we should take off-list.
1. The domain did expire. If you had taken a look at it yesterday morning
you would have seen that it was available to be registered.
2. Much of the confusion in the records is due to their mixture of internal
and external ad
In Declude JM perhaps it is not a bad idea to have some fail safe
options. For example..
There are quite a few. :)
I made a blank entry in our database which ended up as:
BODY 20 CONTAINS
& it was blank after contains.. a number of emails failed this test by the
time I found out about it.
Hi Darin,
No - the domain has been back for a while - but it's a terrible mess. See:
http://www.dnsreport.com/tools/dnsreport.ch?domain=skanskausa.com for an
independent review.
A) their name server lists has the following NS records:
dns-sku-par-0.
cbru.br.ns.els-gms.att.net.
dbru.br.ns.els-
Hi Scott:
No - neither was the case - those were normal "firstname.lastname" email
addresses.
Best Regards
Andy Schmidt
Phone: +1 201 934-3414 x20 (Business)
Fax:+1 201 934-9206
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of R. Scott Perry
Sent
Title: Message
Scott:
In Declude JM
perhaps it is not a bad idea to have some fail safe options. For
example..
I made a blank
entry in our database which ended up as:
BODY 20
CONTAINS
& it was blank
after contains.. a number of emails failed this test by the time I found out
about
Maybe the declude -diag output could be tweaked to give a quick count of
whitelist lines.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of R. Scott Perry
Sent: Saturday, 31 May 2003 2:28 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Whitelist after
Title: Message
Hi;
I actually
remember at one point there was a limit of 200 on whitelist. Has that
limit changed?
In the manual it
says:
You can have up to 200 of the WHITELIST
entries in the global.cfg file. They only work in the global.cfg file; you can
not have user-specific or d
Just a suggestion...
I really think that we should keep any dynamic entries out of the Global
statement. Global should be a file that changes only when one wants to
make changes to the engine or adding functionality. It is simply like a
.ini file that controls the engine.
Currently there is
Does anyone know the behavior of the whitelist feature in the global
config file when 200 entries are reached? It appears to randomly ignore
whitelist entries. Is this correct?
If there are more than 200 whitelist entries in the global.cfg file, the
first entries will get overwritten by the l
Hmmm, this feature doesn't really help us then. Any thoughts about
including CIDR ranges in the PREWHITELIST feature?
Yes -- we're going to try to add extra whitelist types to the PREWHITELIST
option.
-Scott
---
Declude JunkMail: The advanced a
Does anyone know the behavior of the
whitelist feature in the global
config file when 200 entries are reached? It appears to randomly ignore
whitelist entries. Is this correct?
thx,
Dave
Hmmm, this feature doesn't really help us then. Any thoughts about
including CIDR ranges in the PREWHITELIST feature?
Bill
- Original Message -
From: "R. Scott Perry" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, May 31, 2003 5:46 AM
Subject: Re: [Declude.JunkMail] PREWHITE
22 matches
Mail list logo
