Hi,
The old problem with the interim files is back/still there.
Your web server does NOT have .CFG configured in the MIME types - so it
refuses to download the sample CFG files. You need to either update the web
server settings to permit .CFG filetypes OR rename or zip those sample CFG
Effective immediately, please use dave.marche...@connectedindustries.com for
all business and non-business related correspondence. The citcomm.com address
is no longer valid.
Thanks,
Dave Marchette
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an
We are seeing quite a few email's being caught as VIRUS by
X-Declude-Virus: Detected [Outlook 'MIME segment in MIME Postamble'
Vulnerability] [from IP 173.227.130.61 (mail.politics1.com)].
The email DOES have (at the end)
--Boundary-00=_TY255O4SHK9FB43NIKKB--
Is the CONFIRM ON still supported - for double opt-in email
I did not find a Config.cfg file, so I created on and it seems to work OK.
Ferrell
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to imail...@declude.com, and
type unsubscribe
Hi Ferrell,
I can assure you that the MIME segment in MIME Postamble Vulnerability is
triggering correctly.
This vulnerability occurs when it appears as though a MIME segment is occurring
after the end of the MIME body (specifically, a MIME segment with a boundary
other than the one specified
I am trying to use the following regex to catch phishing URLs like
http://www.usps.com.scam.com
http\:\/\/www.*?\.com\..*?\.com
The issue is the question marks do not stop the greediness of the *
it will catch
Hi Rick,
Are you sure your regex catches the long URL how did you test it ?
David
-Original Message-
From: Rick Davidson [mailto:rdavid...@nat.com]
Sent: Thursday, November 03, 2011 6:38 PM
To: Declude.JunkMail@declude.com
Subject: [Declude.JunkMail] Regex Greed Issue
I am trying to
well based on your response I guessed you couldn't reproduce it with the
example I sent, I confirmed that, and I am unable to trick that regex, however
it does catch messages it shouldnt.
here is the log entry for the example message
11/03/2011 15:14:07.489 008080891 Triggered body PCRE
