I would like to disable the subject line warning that gets placed in the
subject line for one particular email account on a domain.
He is complaining that he sees too many emails with a subject warning.
Kind of like this. if the email address = [EMAIL PROTECTED] then don't put
subject line
Not a rule, but either a domain-level or user-level config to change the WARN
action to IGNORE.
Darin.
- Original Message -
From: Craig Edmonds
To: declude.junkmail@declude.com
Sent: Friday, February 16, 2007 6:33 AM
Subject: [Declude.JunkMail] disable subject line warning on one
Sent: Friday, February 16, 2007 12:41 PM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] disable subject line warning on one email
account
Not a rule, but either a domain-level or user-level config to change the
WARN action to IGNORE.
Darin.
- Original Message
PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, November 08, 2006 5:45 PM
Subject: RE: [Declude.JunkMail] declude not modifying subject line
I do not understand why you need to rewrite the message beyond what you
already do? Just determine the end of headers properly then rewrite
09, 2006 8:32 AM
Subject: Re: [Declude.JunkMail] declude not modifying subject line
Kevin,
I am very well aware of what byte sequences constitute the end of a line.
However, if the problem were this simple it would have been fixed long ago.
Contrary to what some have said here, we have seen many
4:57 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Hi,
As per previous posts I agree that Declude needs to deal with this
issue,
as neither SmarterMail or Imail have addressed this, just out of curiosity
has anyone contacted SmarterMail
@declude.com
Subject: Re: [Declude.JunkMail] declude not modifying subject line
Well, David. You've known about the problem for a very long time, and from
a customer perspective absolutely nothing has been done. No potential fix
release date. Nothing other than we're working on it. From your post
Sent: Thursday, November 09, 2006 8:58 AM
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Unfortunately Andy you are incorrect we have seen numerous instances where
IMail likewise has put its headers at the end of the body.
David B
www.declude.com
-Original Message
estimate, and meeting the date earlier is, however.
Darin.
- Original Message -
From: David Barker [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Thursday, November 09, 2006 9:06 AM
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Darin,
I will not commit
] [mailto:[EMAIL PROTECTED] On Behalf Of Darin
Cox
Sent: Thursday, November 09, 2006 9:20 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] declude not modifying subject line
David,
I'm sorry you feel that way, but I will not apologize for my post. Frankly
I've had it with posts
: +1 201 934-3414 x20 (Business)
Fax:+1 201 934-9206
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
Barker
Sent: Thursday, November 09, 2006 08:58 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude not modifying subject
09, 2006 08:32 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] declude not modifying subject line
Kevin,
I am very well aware of what byte sequences constitute the end of a line.
However, if the problem were this simple it would have been fixed long ago.
Contrary to what
Hi David F,
David Franco-Rocha [ Declude ] wrote:
The broken line terminators are not necessarily of the same type in a
given message. In addition, they are not necessarily adjacent to each
other (with leading whitespace or unprintable characters on a
line).What may appear obvious to the
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
David Franco-Rocha [ Declude ]
Sent: Thursday, November 09, 2006 5:32 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] declude not modifying subject line
Kevin,
I am very well aware
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
David Franco-Rocha [ Declude ]
Sent: Thursday, November 09, 2006 5:32 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] declude not modifying subject line
Kevin,
I am very well aware of
I've seen some messages with dozens of Kbytes of CC
and TO E-mail lists that would fail this test.
- Original Message -
From:
Herb Guenther
To: declude.junkmail@declude.com
Sent: Thursday, November 09, 2006 3:30
PM
Subject: Re: [Declude.JunkMail] End
that would fail this test.
-
Original Message -
From:
Herb Guenther
To:
declude.junkmail@declude.com
Sent:
Thursday, November 09, 2006 3:30 PM
Subject:
Re: [Declude.JunkMail] End of headers {was - declude not modifying
subject line}
What about
] On Behalf Of Andy
Schmidt
Sent: Wednesday, November 01, 2006 10:31 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Hi David:
Pardon me - but lets not forget that we choose to pay Declude license and
maintenance fees, precisely because of its
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Herb
Guenther
Sent: Wednesday, November 08, 2006 11:22 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] declude not modifying subject line
Hi David;
In an earlier message (below) you mentioned that you were working
is being made overly
complicated.
Declude is not a message-fixer-upper. I have enough problems with people
using CISCO SMTP FIXUP that breaks everything. Declude's job is to
correctly determine the header vs. content and then subject the header and
content to appropriate analysis.
If a message is found
and then subject the header and
content to appropriate analysis.
If a message is found to be malformed, then Declude can make it fail a
Test so that the mail admin can decide to accept or reject those
messages
- but it's not Declude's job to artificially make an incompatible message
compatible
]
To: declude.junkmail@declude.com
Sent: Wednesday, November 08, 2006 12:03 PM
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Hi Dave:
1. This is currently being worked on, there are several other things that
need to be taken into account when doing this, for example if Declude has
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Darin Cox
Sent: Wednesday, November 08, 2006 10:41 AM
To: declude.junkmail@declude.com
Subject: Re: [Declude.JunkMail] declude not modifying subject line
Agreed. Put the headers where they need to be. Don't worry
about fixing
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Me three!
Is it done yet? No? Darn.
Frankly, David, if the Declude app is going to have to rewrite the whole
message anyway to insert headers, make it an optional *feature* to fix up
the line terminators
Schmidt
Phone: +1 201 934-3414 x20 (Business)
Fax:+1 201 934-9206
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
Barker
Sent: Wednesday, November 08, 2006 04:37 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
Barker
Sent: Wednesday, November 08, 2006 3:37 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude not modifying subject line
1. I don't like to keep going in circles on this. If it was as easy as just
fix it there would
Rob,
Thanks for the info. Yes we know that these messages are most likely always
spam, the problem comes in that some admins just tag their subject lines and
rely on either rules at the mail server level or client to process the
message based on the subject. But with the altered header
Barker [EMAIL PROTECTED]
To: declude.junkmail@declude.com
Sent: Wednesday, November 08, 2006 4:37 PM
Subject: RE: [Declude.JunkMail] declude not modifying subject line
1. I don't like to keep going in circles on this. If it was as easy as just
fix it there would be no issue. Please understand
]
Sent: Wednesday, November 08, 2006 5:12 PM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Hi,
As per previous posts I agree that Declude needs to deal with this issue,
as neither SmarterMail or Imail have addressed this, just out
I do not understand why you need to rewrite the message beyond what you already
do? Just determine the end of headers properly then rewrite the message with
your headers in the proper location. You already rewrite the message when
adding headers so why would it take any longer to properly
he problem as it is a non trivial task. However, what do
you expect us to do, go quietly into the night? There are two ways to
stop getting questions on this subject.
1. Fix the problem and get kudos instead of complaints.
or
2. Give a real expected date to address the issue and tell us where in
the
the Subject line and having the
mail server take action based on the headers. You could use actions like.
# MAILBOX will move the E-mail to a user's folder (no, not a Windows
directory)
# ROUTETO will re-route the E-mail to an alternate address
# HOLD will hold the message in the spool\spam directory
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Herb,
I need to clarify something here. This source of this problem is that these
messages do not conform to the RFC's and are extremely broken and should not
be accepted by the mail server in the first place. That is the source
Agreed Andy.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andy
Schmidt
Sent: Wednesday, November 01, 2006 10:31 AM
To: declude.junkmail@declude.com
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Hi David:
Pardon me - but lets
?
With that said, we are working on correcting this problem because clearly
the Mail server is not doing it.
Secondly, there are alternatives to marking the Subject line and having the
mail server take action based on the headers. You could use actions like.
# MAILBOX will move the E-mail to a user's
: Wednesday, November 01, 2006 10:30 AM
Subject: RE: [Declude.JunkMail] declude not modifying subject line
Hi David:
Pardon me - but lets not forget that we choose to pay Declude license and
maintenance fees, precisely because of its claim of being superior in
detecting viruses, vulnerabilities
Hi All;
Another week has went by and I have not heard any time schedule for
fixing the issue with not modifying the message header correctly. This
continues to allow hundreds of spam messages to land in our customers
mailboxes every day.
Again, what is required to get this fixed? We are
:[EMAIL PROTECTED] On Behalf Of Michael
JaworskiSent: Monday, June 19, 2006 1:37 AMTo:
declude.junkmail@declude.comSubject: RE: [Declude.JunkMail] Blank
body Subject
Looks
like the followingfilter is working well. Using the HOLD action to verify
filter success/failure. Caught 32 in the last 5
Must be either
more broken spam or testing for a new spam storm.
John T
eServices For You
Seek, and ye shall
find!
---This E-mail came from the Declude.JunkMail mailing list. Tounsubscribe, just send an E-mail to [EMAIL PROTECTED], andtype "unsubscribe Declude.JunkMail".
:
declude.junkmail@declude.comSubject: [Declude.JunkMail] Bunch more
blank subject blank body
Must be
either more broken spam or testing for a new spam storm.
John
T
eServices For
You
"Seek, and ye shall
find!"
---This E-mail
came from the Declude.JunkMa
Title: Message
I'd suggest that this would work better without false
positives. The headers are missing darn near everything, the date, the
message-id, the subject, and the from. Any one of these could be missing,
but Michael's script will punish with a weight of 30 if either of the two
Title: Message
Anyone
else getting slammed to just about every hosted domain with messages generally
with a blank subject and body?
Some messages with a return address. The body is
of abasic empty html template. The headers lack to and from entries, though the
Declude sender shows
Title: Message
Looks
like the followingfilter is working well. Using the HOLD action to verify
filter success/failure. Caught 32 in the last 5 minutes.
Global.cfg
FILTERMSCfilterD:\SmarterMail\declude\msc.txtx00
msc.txt
HEADERS30 NOTCONTAINS from:HEADERS30 NOTCONTAINS
subject:
$default
Can Declude, IMAIL (or anything) add text to subject of an e-mail that is
being forwarded to an outside e-mail address?
I have too many users (that I am not allowed to stop) forwarding their
e-mail to AOL. Of course some SPAM slips through and they hit report spam
effectively reporting my server
.
- Original Message -
From: Marc Catuogno [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Thursday, January 26, 2006 1:21 PM
Subject: [Declude.JunkMail] Adding text to Subject of FORWARDED e-mail
Can Declude, IMAIL (or anything) add text to subject of an e-mail that is
being forwarded
@declude.com
Sent: Thursday, January 26, 2006 1:55 PM
Subject: Re: [Declude.JunkMail] Adding text to Subject of FORWARDED e-mail
With Declude you can add footers to text messages, and Sandy has an add-in
that can add a footer to HTML messages.
Or you could write a script to run as an external test
Just a curiosity: I received an email from someone at Veritas, and the
subject line was:
Fw: [WARNING - POSSIBLY NOT VIRUS SCANNED]Re: VERITAS Support: Case ID
I'm assuming that this warning was added by their system? Why would they do
that? If they knew it wasn't scanned, why wouldn't
In the last hours a I can see some strange messages (see attached samples)
send from different servers and obviously forged mailfrom adresses.
Each message has as Subject and as Body 1 and an attached but empty file
named 1.txt
The mailfrom-adress seems to be the first part of the recipients
1:56 PM
To: Declude.Virus@declude.com
Cc: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail] Strange messages (Subject: 1)
In the last hours a I can see some strange messages (see attached samples)
send from different servers and obviously forged mailfrom adresses.
Each message has
some strange messages (see attached samples)
send from different servers and obviously forged mailfrom adresses.
Each message has as Subject and as Body "1" and an attached but empty file
named "1.txt"
The mailfrom-adress seems to be the first part of the recipients adress
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
Hi,
If a subject line is encoded like (all on one line):
Subject:
=?utf-8?B?RndkOiBbYmV0dGVybWVudF0gODYlIG9mZiBWaWNvZGluLiAgY291cmFnZW91c2
x5IHNhdmFnZXJz?=
What it really says is:
Fwd: [betterment] 86% off Vicodin. courageously savagers
And I have a filter that looks for vicodin
ANYWHERE
And I have a filter that looks for vicodin
ANYWHERE 2 CONTAINS VICODIN
The filter does not find it. I think it is because the subject line is
encoded. Is there any way to check it with the filters?
Actually, I believe the issue is that ANYWHERE just looks at the subject
and body
Declude will decode declude the subject tests
Declude 1.82 found these:
I've had hits in
=?utf-8?B?Y2hlYXAgb2VtIHNvZnR3YXJlIHNoaXBwaW5nIHdvcmxkd2lkZS4gIHBvdW5jZWQgQ2
hhbmc=?=
for SUBJECT 40 CONTAINS OEM Software
I wonder if it doesn't decode the subject with an ANYWHERE test?
- Original
Great - Fixed.
Thanx
Goran Jovanovic
The LAN Shoppe
-Original Message-
From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of R. Scott Perry
Sent: Thursday, February 10, 2005 3:57 PM
To: Declude.JunkMail@declude.com
Subject: Re
Scott:
If ANYWHERE only gets subject and body, then to fully cover everything in
the message would we then need
ANYWHERE# CONTAINS
HEADERS # CONTAINS
Thanks
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of R. Scott Perry
If ANYWHERE only gets subject and body...
Sorry, I meant that it covers the headers and body (but not any decoded
parts).
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers
since 2000.
Declude Virus: Ultra
Sending message again as the first one did not post.
Goran Jovanovic
The LAN Shoppe
-Original Message-
From: Goran Jovanovic
Sent: Wednesday, February 09, 2005 6:02 PM
To: 'Declude.JunkMail@declude.com'
Subject: Filters and encoded subject lines
Hi,
If a subject line
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Subject problem
Scott. Any response to this.
There should be a new release Monday that covers the issues from this
week.
-Scott
---
Declude JunkMail: The advanced anti-spam solution
: Monday, February 07, 2005 8:03 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Subject problem
Any news of the availability of the new release?
John Tolmachoff
Engineer/Consultant/Owner
eServices For You
-Original Message-
From: [EMAIL PROTECTED
] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of Barry Simpson
Sent: Monday, February 07, 2005 5:12 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Subject problem
There is a new build on www.declude.com 2.0.3 which has the fix in it. The
only outstanding issue we
I'll ask the guys to contact you off list tomorrow to discuss.
Thanks for the offer.
barry
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff
(Lists)
Sent: Monday, February 07, 2005 8:30 PM
To: Declude.JunkMail@declude.com
Subject: RE
We have been developing fixes designed to address the issues reported in the
last few days and comprehensive testing will continue through the weekend.
The results will be reviewed and further information will be released on
Monday.
Thanks for your patience.
Declude Engineering
---
[This
I'm still running 1.81 and don't plan on changing that until all this ruckus
gets settled down. :-)
- Original Message -
From: Ralph Krausse [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Friday, February 04, 2005 4:11 PM
Subject: [Declude.JunkMail] Subject: Declude 2.0
Thank you for the update.
John Tolmachoff
Engineer/Consultant/Owner
eServices For You
-Original Message-
From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of Ralph Krausse
Sent: Friday, February 04, 2005 2:11 PM
To: Declude.JunkMail@declude.com
Subject
I'd upgrade to 1.82 if you use the spamheaders test. It's broken in 1.81.
It's the only change between 1.81 and 1.82.
- Original Message -
From: Glenn \ WCNet [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Friday, February 04, 2005 4:28 PM
Subject: Re: [Declude.JunkMail
I have that test disabled for the duration.
- Original Message -
From: Scott Fisher [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Friday, February 04, 2005 4:50 PM
Subject: Re: [Declude.JunkMail] Subject: Declude 2.0 Update
I'd upgrade to 1.82 if you use the spamheaders
Scott. Any response to this.
Fred
It shows this way in Spam Review and the Subject Line test also catches
this.
It was fixed in the 2.03b but after I installed the production 2.0 released
by Barry it is now broken again.
Fred
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED
Scott. Any response to this.
There should be a new release Monday that covers the issues from this week.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers
since 2000.
Declude Virus: Ultra reliable virus detection
I am running the latest version (newly released 2.0) and the subject is
showing =?iso-8859?
Fred
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL
I am running the latest version (newly released 2.0) and the subject is
showing =?iso-8859?
The subject shouldn't appear that way in the E-mail itself. For Declude
JunkMail usage, it may appear that way with the Subject starting with a
colon issue, which has been fixed in the latest 2.0
I shows this way in Spam Review and the Subject Line test also catches this.
It was fixed in the 2.03b but after I installed the production 2.0 released
by Barry it is now broken again.
Fred
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
I had the same problem. The declude.exe is about 1/2 of the size as the
one it replaced.
That actually is normal -- the old declude.exe file had quite a bit of
extra (unnecessary) debugging code in it. This smaller version removes
that code, which makes Declude slightly more efficient.
I
I emailed support but I imagine they are fixing it, I have not heard back
from them..
The person in charge of the install program just got in, so I expect you
should get a response shortly.
It is now 3 hours later. Any fix yet?
John Tolmachoff
Engineer/Consultant/Owner
eServices For You
/Consultant/Owner
eServices For You
-Original Message-
From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of John Tolmachoff (Lists)
Sent: Wednesday, February 02, 2005 7:47 AM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Problem
Tolmachoff
Engineer/Consultant/Owner
eServices For You
-Original Message-
From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
[EMAIL PROTECTED]] On Behalf Of John Tolmachoff (Lists)
Sent: Wednesday, February 02, 2005 7:47 AM
To: Declude.JunkMail@declude.com
Subject: RE
There appears to be a problem in version 2.0 where Declude is seeing the
first character after the word subject as the start of the subject line. The
first character is a colon and followed by a space and then the actual
subject line.
Log lines and headers sent to support.
John Tolmachoff
There appears to be a problem in version 2.0 where Declude is seeing the
first character after the word subject as the start of the subject line. The
first character is a colon and followed by a space and then the actual
subject line.
You are correct. I'm surprised this didn't get caught during
@declude.com
Subject: Re: [Declude.JunkMail] Problem with subject line in version 2.0
There appears to be a problem in version 2.0 where Declude is seeing the
first character after the word subject as the start of the subject line.
The
first character is a colon and followed by a space
, February 01, 2005 4:31 AM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Problem with subject line in version 2.0
There appears to be a problem in version 2.0 where Declude is seeing the
first character after the word subject as the start of the subject line.
The
first character
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff
(Lists)
Sent: Tuesday, February 01, 2005 11:34 AM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
FYI, I did not use the beta as the new
The fix is in the current 2.0 download from the web site.
Barry Simpson
www.declude.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff
(Lists)
Sent: Tuesday, February 01, 2005 11:33 AM
To: Declude.JunkMail@declude.com
Subject: RE
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
The fix is in the current 2.0 download from the web site.
Barry Simpson
www.declude.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
I ave the same problem and have reverted to the previous 2.0 version.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff
(Lists)
Sent: Tuesday, February 01, 2005 7:58 PM
To: Declude.JunkMail@declude.com
Cc: [EMAIL PROTECTED]
Subject: RE
-
From: [EMAIL PROTECTED] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of Kornitz, David
Sent: Tuesday, February 01, 2005 6:21 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
I ave the same problem and have reverted
)
Sent: Tuesday, February 01, 2005 8:30 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
That is another problem in the growing list:
How do you know what version you have?
Both of them showed version 2.0. Wasn't the beta 2.0b? if so
@declude.com
Cc: [EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 7:58 PM
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
The latest version does not work at all, nothing, zilch, zippo.
This is a disgrace.
Downloaded and copied into the imail directory and ran declude -diag and
all
] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, February 01, 2005 10:21 AM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
The fix is in the current 2.0 download from the web site.
Barry Simpson
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
The fix is in the current 2.0 download from the web site.
Barry Simpson
www.declude.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Tolmachoff
(Lists)
Sent: Tuesday
] [mailto:Declude.JunkMail-
[EMAIL PROTECTED] On Behalf Of Jeff Kratka
Sent: Tuesday, February 01, 2005 9:31 PM
To: Declude.JunkMail@declude.com
Subject: RE: [Declude.JunkMail] Problem with subject line in version 2.0
I had the same problem today while installing v2.0. All Declude functions
strings to comparing a blank space. No biggie... I'll
figure something out.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Matt
Sent: Wednesday, January 05, 2005 5:15 PM
To: Declude.JunkMail@declude.com
Subject: Re: [Declude.JunkMail] Filter for blank subject lines
Any previous talk on filtering for blank subject lines is 2 years old, so
I'd like to present the question again, and/or make a new feature request.
Within our corp, we have several employees who enjoy send their mails with
no subject what-so-ever. Wrist slaps have done nothing to correct
If you have Junkmail Pro, try this as a Filter:
SUBJECT 10ISBLANK
- Original Message -
From: [EMAIL PROTECTED]
To: Declude.JunkMail@declude.com
Sent: Wednesday, January 05, 2005 2:25 PM
Subject: [Declude.JunkMail] Filter for blank subject lines
Any previous talk on filtering
customers.
If you tweak your setup properly, you can tag blank subjects with a
little weight and still not have issues with blocking legitimate E-mail
while improving spam detection.
Matt
[EMAIL PROTECTED] wrote:
Any previous talk on filtering for blank subject lines is 2 years old, so
I'd like
My read is that he is only attempting to enforce the subject requirement on
his on users within his own domain. So if he builds his rules
appropriately, either as a specific domain rule or a combo filter, he should
be able to apply the subject requirement to his own users/domain without
affecting
into a
file cabinet, I have tried it all. Then you have remote users who I don't
have the pleasure of beating on daily. You want to talk about a very large
problem... I'd love to have 1% or 2% of my messages with no subject line.
As it stands right now, this very second, 20% of my corporate inbox
True. Just be careful, and understand that you can't apply such
actions to whitelisted E-mail.
Matt
Bill Landry wrote:
My read is that he is only attempting to enforce the subject requirement on
his on users within his own domain. So if he builds his rules
appropriately, either
I didn't read your original post carefully enough and misunderstood the
exact situation as a result. Sorry to have touched on your
frustration. I agree, no-subject people are annoying, especially when
they do so 20 times a day. Around here that's grounds for disciplinary
action :)
Matt
situation at my office with the blank subject lines
internally, I don't bother telling people what to do, I just find a way
to enforce it through software. If/when you get this figured out I am
very interested in seeing how it was pulled off. In the mean time I'll
tinker around on my server and see
. Normally I'd catch it in my end of the day email
reviews... but this one had no subject, so I (accidentally?) overlooked it.
Had it carried even the vaguest of subject lines, I think it would have
caught my attention last night before I left for the day.
Anywho, I'm determined to get them
1 - 100 of 335 matches
Mail list logo
