On Mon, 2 Apr 2018, Pedro David Marco wrote:
Yeah, just confirmed. A non-obfuscated URI in plain-text body part is
recognized and extracted for uri rules.
Thanks John... can you provide any pastebein sample please??...
It's trivially easy to add a URI to the text body part of any test m
>Yeah, just confirmed. A non-obfuscated URI in plain-text body part is
>recognized and extracted for uri rules.
Thanks John... can you provide any pastebein sample please??...
PedroD
On 01/04/18 19:18, John Hardin wrote:
On Sun, 1 Apr 2018, John Hardin wrote:
On Sun, 1 Apr 2018, Matus UHLAR - fantomas wrote:
On 01.04.18 05:47, Pedro David Marco wrote:
This is a problem i see oftenly...
what if the URL is only in the TEXT part and not in the HTML? many
email aplicatio
On Sun, 1 Apr 2018, John Hardin wrote:
On Sun, 1 Apr 2018, Matus UHLAR - fantomas wrote:
On 01.04.18 05:47, Pedro David Marco wrote:
This is a problem i see oftenly...
what if the URL is only in the TEXT part and not in the HTML? many email
aplications show those URLs as clickable as if th
On Sun, 1 Apr 2018, Matus UHLAR - fantomas wrote:
On 01.04.18 05:47, Pedro David Marco wrote:
This is a problem i see oftenly...
what if the URL is only in the TEXT part and not in the HTML? many email
aplications show those URLs as clickable as if they were valid HTML HREFs
when they are n
On 01/04/18 07:10, Matus UHLAR - fantomas wrote:
On 01.04.18 05:47, Pedro David Marco wrote:
This is a problem i see oftenly...
what if the URL is only in the TEXT part and not in the HTML? many
email aplications show those URLs as clickable as if they were valid
HTML HREFs when they are no
2018-04-01 2:47 GMT-03:00 Pedro David Marco :
> This is a problem i see oftenly...
>
> what if the URL is only in the TEXT part and not in the HTML? many email
> aplications show those URLs as clickable as if they were valid HTML HREFs
> when they are not...
>
We have a script that can extract
On 01.04.18 05:47, Pedro David Marco wrote:
This is a problem i see oftenly...
what if the URL is only in the TEXT part and not in the HTML? many email
aplications show those URLs as clickable as if they were valid HTML HREFs when
they are not...
in this case, body rule matches, but uri doe
This is a problem i see oftenly...
what if the URL is only in the TEXT part and not in the HTML? many email
aplications show those URLs as clickable as if they were valid HTML HREFs when
they are not...
-PedroD
On 31/03/18 22:39, John Hardin wrote:
On Sat, 31 Mar 2018, Sebastian Arcus wrote:
I have a really simple rule looking for custom text string contained
in spam urls in the body of the email, like so:
body SHORT_BITCOIN_DATING /specific_string_here/i
score SHORT_BITCOIN_DATING 3
On Sat, 31 Mar 2018, Sebastian Arcus wrote:
I have a really simple rule looking for custom text string contained in spam
urls in the body of the email, like so:
body SHORT_BITCOIN_DATING/specific_string_here/i
score SHORT_BITCOIN_DATING3.0
describe SHORT_BITCOIN_DATINGBod
I have a really simple rule looking for custom text string contained in
spam urls in the body of the email, like so:
body SHORT_BITCOIN_DATING/specific_string_here/i
score SHORT_BITCOIN_DATING3.0
describe SHORT_BITCOIN_DATINGBody URL signature of spam
I just realised that
12 matches
Mail list logo
