The previous thread for this bug got cross-threaded with a
whiteListedDomains [non]-issue, but the redRe/scriptRe bug still exists:
ASSP v1.3.2(33-45)
I've seen this a many times now, so it is reproducible (a real
issue). Each time I have seen it, it has happened with a redRe match:
What I am
ASSP v1.3.2(33)
I've seen this a few times now, so it appears to be reproducible (a real
issue). Each time I have seen it, it has happened with a redRe match:
What I am seeing are emails that have matched the redRe, and then being
handled and post-processed by ASSP as a scriptRe. Here is an
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
assp-user@lists.sourceforge.net schreibt:
ASSP v1.3.2(33)
I've seen this a few times now, so it appears to be reproducible (a
real
issue). Each time I have seen it, it has happened with a redRe match:
What I am seeing are emails that
Micheal Espinola Jr wrote:
ASSP v1.3.2(33)
I've seen this a few times now, so it appears to be reproducible (a
real
issue). Each time I have seen it, it has happened with a redRe match:
What I am seeing are emails that have matched the redRe, and then
being
handled and post-processed by
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
assp-user@lists.sourceforge.net schreibt:
I don't know if it's the same issue, but I'm seeing any RedRe regex
match
get sent to my sendallspam address. This is in 1.3.2(38). All of
the
messages sent to assp-user@lists.sourceforge.net
Fritz Borgstedt wrote:
I do not understand. What is the issue here?
Is Subject: RE: check this not in redre and scriptre?
in what regular expression is it?
It *is* in the redRe. It's definitely *not* in the scriptRe.
-
Dave Emory wrote:
I don't know if it's the same issue, but I'm seeing any RedRe regex match
get sent to my sendallspam address. This is in 1.3.2(38). All of the
messages sent to assp-user@lists.sourceforge.net are getting copied right
now.
I'm definitely not seeing the same with (33). I
Please switch to the newest built.
fritz
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
Fritz Borgstedt wrote:
Please switch to the newest built.
fritz
Will do.
Not to mix threads, but is my instance of matching an un @
whiteListedDomain (domain.tld) an issue? I thought whitelisted domains
without an @ could only match sub-domains - but not something like:
notrealdomain.tld
There is no . to delineate the sub-domain, so that shouldn't match -
right? If that is correct, then the issue does exist, because I am
seeing it - and I never had such an issue before.
issue? i do not understand. domainlisting never changed the last two
or so years.
blackdomain and
Fritz Borgstedt wrote:
issue? i do not understand. domainlisting never changed the last two
or so years.
blackdomain and whitedomain are handled the same,
I didn't think so either, but for some reason I am seeing a change in
behavior- unless I have had a misconception of the behavior and
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy
assp-user@lists.sourceforge.net schreibt:
Thats not a sub-domain match, so that shouldn't happen with or without
an @, right?
wrong! and waste of time!
Note this matches the end of the address
and the example provided is exactly the
Fritz Borgstedt wrote:
wrong! and waste of time!
Note this matches the end of the address
and the example provided is exactly the case you are describing:
Note that buy.com would also match spambuy.com but .buy.com won\'t
match buy.com.
Yes, I see that now - and am disgusted with myself
13 matches
Mail list logo
