Hello,
Does anyone have a way to automatically delete emails that have MX/mail
records that point to 127.0.0.1? The email is currently in a loop on our
mail server then eventually fails. The link below is an example domain
that
is clogging our filtering server:
Is it possible to set up a filter/test
that basically states
if recipient begins with 01, 02, 03, 04, 05, etc
delete
I have users that come and go every year.
Their username begins the numbers 01, or 02..etc.
Thanks,
Ernesto
---
This E-mail came from the Declude.JunkMail mailing list.
Yes, you can use filters to do this.
MAILFROM 3 STARTSWITH 01
Darrell
---
DLAnalyzer - Comprehensive reporting on Declude Junkmail and Virus. Try it
today http://www.invariantsystems.com
Ernesto Nieto writes:
Is it
Thanks for the reply
but I want to filter based on the person receiving it.
Say I had a user [EMAIL PROTECTED]
I want every email that comes TO that person to be deleted.
But since there might be other '02' users, I'd rather have all '02'
user emails deleted.
- Original Message -
Why have the user or alias at all, then. Just don't have the address in the
domain and you won't receive it...
Darin.
- Original Message -
From: Ernesto Nieto [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, June 16, 2005 3:40 PM
Subject: Re: [Declude.JunkMail]
The only other option I see is using ALLRECIPS which if the message has a
collection of users than it would not catch the recipients in the middle of
the collection that start with the number. However using ALLRECIPS on
messages with one user this would work, but it is not a solve all solution
Does anyone have a filter for the ZDNet
URLredirector that they are willing to share?
I've noticed some minimal spam leakage from the
ZDnet redirectors listed below:
http://chkpt.zdnet.com/chkpt.com/chkpt/http://chkpt.zdnet.com/chkpt/
So I've started my own filter, but I thought why
Is there any reason the Queue times would be over three hours?
The Queue is backed up to over 2+ and the overflow directory
has 19000+ as well. It's taking about four hours to deliver mail
to and from our server even on local accounts. I've checked the
CPU usage and rebooted the machine
Hello All
I know that this has nothhing to do with
Declude,but I figuared with the minds here I could find an
answer.
I have a customer that get mail for a client that
uses exchange server to send there mail. All the mail has the body encoded
is base64. Some of it readable with OE other is
I've noticed the same problem (also starting last night some time), I'm
still running Declude 2.0.5. I am still working on diagnosing it, but I
have been noticing that the Declude instances seem to be running longer
than normal. The dec.log doesn't seem to indicate anything unusual,
but
Mike,
I had the EXACT same problem today although I caught it very early to
QueueMon. I had to add the DNSOVERRIDE xxx.xxx.xxx.xxx where xxx... is in
the declude.cfg file. Ralph from Declude posted this a while back and at
the time I did not exhibit the problem - but I sure did today...
Here
Hi Ernesto-
Are you using a nobody alias? Delete that and your problem should go away.
Nobody aliases are a very bad idea these days.
-Dave Doherty
Skywaves, Inc.
- Original Message -
From: Ernesto Nieto [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, June 16,
Declude detects them (MAILFROM test) if the domain is used in the
FROM address in the headers (from email DATA), but not if the domain
is used in SMTP mailfrom (return address)
The MAILFROM test does not work on the BDAT From: header. It works on
the envelope MAIL FROM: sender.
Can
I dropped back to an older version and within an hour my queueoverflow
went from 42000+ to 25 (that's twenty-five) emails. Mail from gmail, yahoo,
msn, and the rest of the world now gets processed in a matter of seconds
rather then hours. I did not have to reboot the server. I checked our
DNS
Just in case this helps anyone else:
I've done some digging and noticed that the easynet.nl tests don't seem
to resolve (blackholes.easynet.nl, dynablock.easynet.nl,
proxies.blackholes.easynet.nl) and after removing those tests it seemed
to work much better. Though I am taking the time to
I did the same. There is definitely an issue with 2.0.6.16.
-Original Message-
From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of Michael Hardrick
Sent: Thursday, June 16, 2005 7:43 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail]
16 matches
Mail list logo
