Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: NSP

error

 

 

Cisco nsp RSS feed   Index | Next | Previous | View Threaded


psirt at cisco

Aug 6, 2004, 6:41 AM

Post #1 of 6 (437 views)
Permalink
error

Dear user of puck.nether.net,

We have detected that your account was used to send a large amount of spam during this week.
Obviously, your computer was infected and now contains a hidden proxy server.

Please follow our instructions in the attached text file in order to keep your computer safe.

Sincerely yours,
puck.nether.net support team.


steve at telecomplete

Aug 6, 2004, 6:58 AM

Post #2 of 6 (432 views)
Permalink
Re: error [In reply to]

theres nothing more annoying than receiving a virus than not receiving the
virus...

who strips the attachments like this and why?!

Steve

On Fri, 6 Aug 2004, psirt [at] cisco wrote:

> Dear user of puck.nether.net,
>
> We have detected that your account was used to send a large amount of spam during this week.
> Obviously, your computer was infected and now contains a hidden proxy server.
>
> Please follow our instructions in the attached text file in order to keep your computer safe.
>
> Sincerely yours,
> puck.nether.net support team.
>
>


jay at west

Jul 1, 2008, 10:17 AM

Post #3 of 6 (424 views)
Permalink
Re: Error [In reply to]

Ziv Leyes wrote:
> I have the same fixed IP address at home for 3 years now and I also get mailer error messages lately claiming that MY message didn't reach the recipient and the reasons are many, such as unknown user, mailbox over quota, out of office auto reply, some are from anti-spam systems, but all of them are sent back to me because the sender address is my e-mail address, and the mail was sent from a lot of ip addresses, none of them are even close to mine. So I guess someone is using my e-mail address for sending spam, and I guess I'm not the only one, The reason for spammers to use a valid e-mail address is quite clear, a lot of anti-spam systems perform this kind of check, to see if the sender's address is real and has good "reputation"
>
> Damn them!

Damn both the spammers and the broken mail servers that accept the mail
first and then bounce it back to the forged "sender", thus being a
secondary source of spam.

The receiving mail system upon getting mail for an unknown user, mailbox
full, or anti-spam detection should reject the mail immediately, not
accept it and then later attempt to bounce it back to the purported sender.

Don't even get me started on "out of office" autoresponders.

--
Jay Hennigan - CCIE #7880 - Network Engineering - jay [at] impulse
Impulse Internet Service - http://www.impulse.net/
Your local telephone and internet company - 805 884-6323 - WB6RDV
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


petelists at templin

Jul 1, 2008, 11:34 AM

Post #4 of 6 (418 views)
Permalink
Re: Error [In reply to]

Jay Hennigan wrote:

> Damn both the spammers and the broken mail servers that accept the mail
> first and then bounce it back to the forged "sender", thus being a
> secondary source of spam.
>
> The receiving mail system upon getting mail for an unknown user, mailbox
> full, or anti-spam detection should reject the mail immediately, not
> accept it and then later attempt to bounce it back to the purported sender.

Then write an updated RFC that changes the standards to reflect this
behavior, and get it published and accepted.

pt
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


jasongurtz at npumail

Jul 1, 2008, 1:39 PM

Post #5 of 6 (427 views)
Permalink
Re: Error [In reply to]

> Then write an updated RFC that changes the standards to reflect this
> behavior, and get it published and accepted.

Looks like 5821 will have to do (3821/4821 already taken) and be great
when everyone's compliant by the year 2030. In the meantime, BATV (draft
is: draft-levine-smtp-batv-01) can be of help. Helpfully, it even breaks
most C/R systems as well :)

~JasonG

--
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


zivl at gilat

Jul 2, 2008, 4:26 AM

Post #6 of 6 (395 views)
Permalink
Re: Error [In reply to]

I'm not the one that is capable to do it and I don't wanna sound demagogic but I think the whole SMTP protocol should be re-written from scratch. We're talking about a protocol that is over 40 years old! And nowadays we need much more than a "simple mail transfer protocol"
Well, this goes also for TCP...
Ziv


-----Original Message-----
From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Jason Gurtz
Sent: Tuesday, July 01, 2008 11:40 PM
To: cisco-nsp [at] puck
Subject: Re: [c-nsp] Error


> Then write an updated RFC that changes the standards to reflect this
> behavior, and get it published and accepted.

Looks like 5821 will have to do (3821/4821 already taken) and be great
when everyone's compliant by the year 2030. In the meantime, BATV (draft
is: draft-levine-smtp-batv-01) can be of help. Helpfully, it even breaks
most C/R systems as well :)

~JasonG

--
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/





************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************








************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************



_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Cisco nsp RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.