You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by giga328 <gi...@hotmail.com> on 2009/03/01 14:47:15 UTC

Webmail spammers

Hi all,

We have some strong spam attacks done by combination of our webmail, viruses
and open proxies.

Situation is like this:
Our outgoing SMTP server is open only for users from our IP addresses and is
filtered for rest of the world. Our webmail interface is open to whole world
as our users need to access it from anywhere (of course they have to log in
first).
Spammers are stilling passwords from some of our users by using viruses
(passwords are stolen, not guessed or brute force cracked).
Spammers have application which is able to authenticate to our webmail
interface and post email :)

After posting email by webmail interface, message is routed to our outgoing
SMTP server. It is scanned by spamd from SpamAssassin but it get low score.
Low score is from tests ALL_TRUSTED and/or BAYES_xx and/or AWL.
I'm not sure if we can remove webmail IP address from trusted networks
because we can get to much false positives by doing that (as we had in the
past).
For low scores BAYES_xx I have idea to lower default scores in cf. Any other
idea?
For AWL problem I have one question. If I understood right, AWL is based on
>From address. Is it possible to fast change algorithm of AWL to be bases on
unique combination of From and To addresses? Or maybe on even complicated
Header-From, Header-To, Envelope-From, Envelope-To tuple? In that way AWL
will much better track habits of users.

Or if anybody had same problems I'm open to any suggestions.

Regards,
Giga

-- 
View this message in context: http://www.nabble.com/Webmail-spammers-tp22273077p22273077.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


Re: Webmail spammers

Posted by jp <jp...@saucer.midcoast.com>.
We're seeing some of this too. The Nigerian phishes for a few accounts 
here and there probably acquired from a spammer email list, and uses one 
webmail system to email users on their other webmail system. They send 
something official looking asking for passwords, banking numbers, birth 
dates, etc all the information they can phish for. The return address is 
typically a phished webmail account they'd broken into somewhere else.

We put notices up to tell customers we won't ask for their password or 
other information via email because we either don't need it or already 
have what we need, and that method is not a good way to do it anyways.

The squirrelmail logs in the email headers the authenticated 
squirrelmail user and the web client's IP address, so it's easy to track 
which accounts were compromised. We lock their accounts and have a 
customer service person have an educational chat with the actual end 
user before assigning a new different password.

I think they manually log in, paste a message in, then paste in a string 
of email addresses to send it to. Their labor is cheap really, and they 
are effective at getting information out of people.

We have a manual block list of IP ranges that we don't allow to access 
the squirrelmail server. They are all african IPs. If we catch a 
phisher, we put the whole class-c or class-b from which they came into 
the block. We haven't had any complaints, and the incidences of abuse 
have dropped way off. I'm sure it's not due to end users wising up.

Unfortunately, if people's email accounts are getting phished, some 
manual customer service/education/management/care is needed, regardless 
of what email software we use or our collaborative computer science 
aptitude.

On Sun, Mar 01, 2009 at 02:50:37PM -0500, Joseph Brennan wrote:
>
>
>> If your users are consistently getting their passwords stolen, then  your
>> users are idiots and you will need to do something like add a  captcha to
>> the webmail login page.
>
>
> If it's the Nigerian gangs that have been attacking university web mail
> for about 12 months now, they are phishing your users with official
> looking notices that ask the user to send account and password.  If so,
> captcha won't do it.
>
> I agree it's not exactly a Spamassassin problem.  But chances are
> the outbound mail would score pretty high, and spam score could be used
> by some other filter as a trigger to stop the mail from going out.  And
> of course a sudden increase in volume from a user could also trigger.
>
> Joseph Brennan
> Columbia University Information Technology
>
>

-- 
/*
Jason Philbrook   |   Midcoast Internet Solutions - Wireless and DSL
    KB1IOJ        |   Broadband Internet Access, Dialup, and Hosting 
 http://f64.nu/   |   for Midcoast Maine    http://www.midcoast.com/
*/

Re: Webmail spammers

Posted by Michelle Konzack <li...@tamay-dogan.net>.
Am 2009-03-01 13:04:49, schrieb LuKreme:
> unless you are suggesting that they are MANUALLY logging into the  
> webmail to then send 1 billion spams, yes it will.

Break them out, by allowing to send only 10 messages per hour  from  the
Webinterface...  This is what I do here and it works quiet well,  except
for two users, but they have goten a higher quote.

Thanks, Greetings and nice Day/Evening
    Michelle Konzack
    Systemadministrator
    24V Electronic Engineer
    Tamay Dogan Network
    Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
<http://www.tamay-dogan.net/>               <http://www.can4linux.org/>
Michelle Konzack   Apt. 917                  ICQ #328449886
+49/177/9351947    50, rue de Soultz         MSN LinuxMichi
+33/6/61925193     67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Re: Webmail spammers

Posted by LuKreme <kr...@kreme.com>.
On Mar 3, 2009, at 3:32, "Benny Pedersen" <me...@junc.org> wrote:
> On Mon, March 2, 2009 17:27, Joseph Brennan wrote:
>> LuKreme <kr...@kreme.com> wrote:
>>> unless you are suggesting that they are MANUALLY logging into the
>>> webmail to then send 1 billion spams, yes it will.
>
> bots can do anything when login and password is known to them

No, that is the entire *point*of captcha systems.



Re: Webmail spammers

Posted by Benny Pedersen <me...@junc.org>.
On Mon, March 2, 2009 17:27, Joseph Brennan wrote:
> LuKreme <kr...@kreme.com> wrote:
>> unless you are suggesting that they are MANUALLY logging into the
>> webmail to then send 1 billion spams, yes it will.

bots can do anything when login and password is known to them

> That is an interesting point.  OK.  I don't know whether they do a
> manual login to get a session open before they run the software they
> use to dump spam.

if its so, then the sender have a finger that is a robot arm :)

-- 
http://localhost/ 100% uptime and 100% mirrored :)


Re: Webmail spammers

Posted by Joseph Brennan <br...@columbia.edu>.
LuKreme <kr...@kreme.com> wrote:

> unless you are suggesting that they are MANUALLY logging into the
> webmail to then send 1 billion spams, yes it will.

That is an interesting point.  OK.  I don't know whether they do a
manual login to get a session open before they run the software they
use to dump spam.


Joseph Brennan
Columbia University Information Technology


Re: Webmail spammers

Posted by LuKreme <kr...@kreme.com>.
On 1-Mar-2009, at 12:50, Joseph Brennan wrote:
>> If your users are consistently getting their passwords stolen,  
>> then  your
>> users are idiots and you will need to do something like add a   
>> captcha to
>> the webmail login page.
>
> If it's the Nigerian gangs that have been attacking university web  
> mail
> for about 12 months now, they are phishing your users with official
> looking notices that ask the user to send account and password.  If  
> so,
> captcha won't do it.

unless you are suggesting that they are MANUALLY logging into the  
webmail to then send 1 billion spams, yes it will.

-- 
Two, Four, Six, Eight! Time to Transubstantiate!


Re: Webmail spammers

Posted by giga328 <gi...@hotmail.com>.
Thank you Joseph,

I'm glad that it is social engineering and not some virus problem. I will
arrange that all users are informed that they will never be asked for their
passwords by email and we will see if in some time number of issues will
fall down.

Giga


Joseph Brennan wrote:
> 
> 
> If it's the Nigerian gangs that have been attacking university web mail
> for about 12 months now, they are phishing your users with official
> looking notices that ask the user to send account and password.  If so,
> captcha won't do it.
> 
> 

-- 
View this message in context: http://www.nabble.com/Webmail-spammers-tp22273077p22279565.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


Re: Webmail spammers

Posted by Joseph Brennan <br...@columbia.edu>.

> If your users are consistently getting their passwords stolen, then  your
> users are idiots and you will need to do something like add a  captcha to
> the webmail login page.


If it's the Nigerian gangs that have been attacking university web mail
for about 12 months now, they are phishing your users with official
looking notices that ask the user to send account and password.  If so,
captcha won't do it.

I agree it's not exactly a Spamassassin problem.  But chances are
the outbound mail would score pretty high, and spam score could be used
by some other filter as a trigger to stop the mail from going out.  And
of course a sudden increase in volume from a user could also trigger.

Joseph Brennan
Columbia University Information Technology




Re: Webmail spammers

Posted by LuKreme <kr...@kreme.com>.
On 1-Mar-2009, at 06:47, giga328 wrote:
> Spammers are stilling passwords from some of our users by using  
> viruses
> (passwords are stolen, not guessed or brute force cracked).
> Spammers have application which is able to authenticate to our webmail
> interface and post email :)


If your users are consistently getting their passwords stolen, then  
your users are idiots and you will need to do something like add a  
captcha to the webmail login page.

This has nothing to do with Spamassassin, as it is behaving  
correctly.  You are attacking this problem from the wrong end.

-- 
Did they get you to trade your heroes for ghosts? Hot
ashes for trees? Hot air for a cool breeze? Cold comfort
for change?


Re: Webmail spammers

Posted by Michelle Konzack <li...@tamay-dogan.net>.
Am 2009-03-01 15:31:45, schrieb giga328:
> 
> Nice idea. We were considering this for a long time because our mail server
> has built in support for email throttling. Luckily for me, configuring it
> will be done by my colleague as it is his part of the job. Tomorrow morning
> I will happily inform him that throttling is needed and suggested by someone
> who knows antispam :)

I have integrated a message counter directly into the Web-interface, and
I can set quotas per user (messages per hour and set it to 10) because I
have not a singel user which write more.

And of course, the send quota is schown  in  the  user  interface,  this
mean, if she/he can not more send, then there  is  something  wrong  and
because all outgoing messages are Fcc: in the $SEND folder...  the  user
know very well what happen to him.

Thanks, Greetings and nice Day/Evening
    Michelle Konzack
    Systemadministrator
    24V Electronic Engineer
    Tamay Dogan Network
    Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
##################### Debian GNU/Linux Consultant #####################
<http://www.tamay-dogan.net/>               <http://www.can4linux.org/>
Michelle Konzack   Apt. 917                  ICQ #328449886
+49/177/9351947    50, rue de Soultz         MSN LinuxMichi
+33/6/61925193     67100 Strasbourg/France   IRC #Debian (irc.icq.com)

Re: Webmail spammers

Posted by giga328 <gi...@hotmail.com>.
Nice idea. We were considering this for a long time because our mail server
has built in support for email throttling. Luckily for me, configuring it
will be done by my colleague as it is his part of the job. Tomorrow morning
I will happily inform him that throttling is needed and suggested by someone
who knows antispam :)

Giga


Raymond Dijkxhoorn wrote:
> 
> Hi!
> 
>> We have some strong spam attacks done by combination of our webmail,
>> viruses
>> and open proxies.
>>
>> Situation is like this:
>> Our outgoing SMTP server is open only for users from our IP addresses and
>> is
>> filtered for rest of the world. Our webmail interface is open to whole
>> world
>> as our users need to access it from anywhere (of course they have to log
>> in
>> first).
> 
> Count! MAke some scripts on your outbound SMTP and do per user (e-mail) 
> thresholds. So if you have a exploited account the damage is minimal.
> 
> Bye,
> Raymond.
> 
> 

-- 
View this message in context: http://www.nabble.com/Webmail-spammers-tp22273077p22279634.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


Re: Webmail spammers

Posted by Raymond Dijkxhoorn <ra...@prolocation.net>.
Hi!

> We have some strong spam attacks done by combination of our webmail, viruses
> and open proxies.
>
> Situation is like this:
> Our outgoing SMTP server is open only for users from our IP addresses and is
> filtered for rest of the world. Our webmail interface is open to whole world
> as our users need to access it from anywhere (of course they have to log in
> first).

Count! MAke some scripts on your outbound SMTP and do per user (e-mail) 
thresholds. So if you have a exploited account the damage is minimal.

Bye,
Raymond.

Re: Webmail spammers

Posted by Matt <lm...@gmail.com>.
Using Ratelimit in Exim MTA and plugin "Restrict Senders" in
Squirrelmail slows them down.  Spammers need to send out large number
of messages to get any payback.  Limiting the number they can send
with a compromised account really makes that account of no value to
them.

Matt

On Sun, Mar 1, 2009 at 7:47 AM, giga328 <gi...@hotmail.com> wrote:
>
> Hi all,
>
> We have some strong spam attacks done by combination of our webmail, viruses
> and open proxies.
>
> Situation is like this:
> Our outgoing SMTP server is open only for users from our IP addresses and is
> filtered for rest of the world. Our webmail interface is open to whole world
> as our users need to access it from anywhere (of course they have to log in
> first).
> Spammers are stilling passwords from some of our users by using viruses
> (passwords are stolen, not guessed or brute force cracked).
> Spammers have application which is able to authenticate to our webmail
> interface and post email :)
>
> After posting email by webmail interface, message is routed to our outgoing
> SMTP server. It is scanned by spamd from SpamAssassin but it get low score.
> Low score is from tests ALL_TRUSTED and/or BAYES_xx and/or AWL.
> I'm not sure if we can remove webmail IP address from trusted networks
> because we can get to much false positives by doing that (as we had in the
> past).
> For low scores BAYES_xx I have idea to lower default scores in cf. Any other
> idea?
> For AWL problem I have one question. If I understood right, AWL is based on
> From address. Is it possible to fast change algorithm of AWL to be bases on
> unique combination of From and To addresses? Or maybe on even complicated
> Header-From, Header-To, Envelope-From, Envelope-To tuple? In that way AWL
> will much better track habits of users.
>
> Or if anybody had same problems I'm open to any suggestions.
>
> Regards,
> Giga
>
> --
> View this message in context: http://www.nabble.com/Webmail-spammers-tp22273077p22273077.html
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
>
>

Re: Webmail spammers

Posted by Benny Pedersen <me...@junc.org>.
On Sun, March 1, 2009 14:47, giga328 wrote:
> We have some strong spam attacks done by combination of our webmail,
> viruses and open proxies.

do you just trust email senders if thay are loged in to not spam
check it before leaving your network ?

(rest skipped]

-- 
http://localhost/ 100% uptime and 100% mirrored :)


Re: Webmail spammers

Posted by Greg Troxel <gd...@ir.bbn.com>.
giga328 <gi...@hotmail.com> writes:

> I looked at Received headers and unfortunately, Received headers added by
> our webmail are not standard ones. Except for the proxy.IP in the following
> example, all IPs and all FQDNs are from our servers. Here is the (ugly)
> example:
>
> Received: from our.domain ([our.webmail.private.IP])
>  by our.mtaout.our.domain (server version) with ESMTP id
> <0K...@our.mtaout.our.domain> for
>  recipient@some.domain; Sun, 01 Mar 2009 16:34:59 +0100 (CET)
> Received: from [our.webmail.public.IP] (Forwarded-For: proxy.IP)
>  by our.webmail.our.domain (mshttpd); Sun, 01 Mar 2009 16:34:58 +0100
> From: our user <ou...@our.domain>
> To: recipient@some.domain
>
> At least, header and envelope from and to addresses can not be faked by
> using webmail.
>
> Any idea how can I make SpamAssassin to trigger DNSBL, DCC, Razor tests (or
> at least DCC, Razor tests) for proxy.IP?

Well, two simple ideas:

1) Fix your webmail code to put in regular received: lines, with an
authenticated sender tag, just like e.g. if it had some in tls/sasl to
postfix or sendmail

2) Write some perl code in spamassassin to recognize that webmail header.

I think option 1 is a better outcome, and probably easier, assuming you
have source for your webmail setup.


Re: Webmail spammers

Posted by giga328 <gi...@hotmail.com>.
Hi Greg,

I looked at Received headers and unfortunately, Received headers added by
our webmail are not standard ones. Except for the proxy.IP in the following
example, all IPs and all FQDNs are from our servers. Here is the (ugly)
example:

Received: from our.domain ([our.webmail.private.IP])
 by our.mtaout.our.domain (server version) with ESMTP id
<0K...@our.mtaout.our.domain> for
 recipient@some.domain; Sun, 01 Mar 2009 16:34:59 +0100 (CET)
Received: from [our.webmail.public.IP] (Forwarded-For: proxy.IP)
 by our.webmail.our.domain (mshttpd); Sun, 01 Mar 2009 16:34:58 +0100
From: our user <ou...@our.domain>
To: recipient@some.domain

At least, header and envelope from and to addresses can not be faked by
using webmail.

Any idea how can I make SpamAssassin to trigger DNSBL, DCC, Razor tests (or
at least DCC, Razor tests) for proxy.IP?

Regards,
Giga


Greg Troxel wrote:
> 
> 
> I don't think these mails should be hitting ALL_TRUSTED.  Your web
> server did not really originate them, but received them from some other
> host over a webmail subsmission protocol that is really just like SMTP
> submission in function.  So I think the web server should be adding a
> Received: header to show that, and that would enable spamassassin to
> look up the previous hop list in RBLs.
> 
> 

-- 
View this message in context: http://www.nabble.com/Webmail-spammers-tp22273077p22279486.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.


Re: Webmail spammers

Posted by Greg Troxel <gd...@ir.bbn.com>.
giga328 <gi...@hotmail.com> writes:

> After posting email by webmail interface, message is routed to our outgoing
> SMTP server. It is scanned by spamd from SpamAssassin but it get low score.
> Low score is from tests ALL_TRUSTED and/or BAYES_xx and/or AWL.
> I'm not sure if we can remove webmail IP address from trusted networks
> because we can get to much false positives by doing that (as we had in the
> past).
> For low scores BAYES_xx I have idea to lower default scores in cf. Any other
> idea?
> For AWL problem I have one question. If I understood right, AWL is based on
> From address. Is it possible to fast change algorithm of AWL to be bases on
> unique combination of From and To addresses? Or maybe on even complicated
> Header-From, Header-To, Envelope-From, Envelope-To tuple? In that way AWL
> will much better track habits of users.

The obvious solution is to ban your users from using Windows and change
all the passwords :-) Or get stronger authentication for sending mail.
But seriously:

I don't think these mails should be hitting ALL_TRUSTED.  Your web
server did not really originate them, but received them from some other
host over a webmail subsmission protocol that is really just like SMTP
submission in function.  So I think the web server should be adding a
Received: header to show that, and that would enable spamassassin to
look up the previous hop list in RBLs.

If your users are sending slightly spammy mail normally, I think you'll
have to work through that separately.  Perhaps you may need to drop
PBL/dialup type rules, or give them a pass when
WEBMAIL_AUTHENTICATED_USER fires (you probably have to write that too).
But using ALL_TRUSTED to give authenticated users effectively a free
pass seems like asking for trouble, since given bots and compromises
authenticated user != legitimate user.

I would not mess with BAYES scores unless you can articulate why they
are off.  Some spam scores low on bayes, but that doesn't mean it isn't
useful.  I don't think moving the BAYES_00 scores towards 0 will help
separate ham from spam in your case, and what you really need to do is
differentially increase the score of spam relative to ham, not just
increase it.

AWL applies to the combination of sender and IP address.  But, if the
Received lines above are missing, then the IP address is probably the
webmail server, and you're lumping all the user's mail in together.  Or
maybe AWL is previous hop and not last untrusted hop.  Unfortunately
legitimate users show up on different IP addresses, but what of course
you really want to avoid is giving negative points to a spammer because
they are using the same From: address.  Thus a legit user on a new
address won't get negative points for their previous mail.

Your basic problem is that from the point of view of the mail system,
previously reasonable users are starting to send spam, although perhaps
From odd addresses.  I would be tempted to write a new test
USER_LOW_VOLUME that watches how much mail a particular user has sent
and gives a few negative points, and maybe USER_HIGH_VOLUME that goes
positive when volume limits are exceeded.