Jump to content
Sign in to follow this  
Frankenstien

TELUS Webmail & SpamCop reporting

Recommended Posts

I am new to SpamCop and am here because my ISP (TELUS.net) 's spam filtering is just not effective enough to stem the tide of spam I am receiving. I refuse to give up my established e-mail addresses and would like to take my defences to the next level.

I have adopted a protocol whereby I login to my ISP's (TELUS) Webmail interface where I can safely open and evaluate any e-mails I can't readily identify from the Inbox list as legitimate or spam.

TELUS has a Webmail spam reporting mechanism, however, each individual spam must be opened to report it, involving 3 webpage refreshes per spam / report and 1 more to delete any given spam. I have lobbied TELUS to offer a batch spam reporting command from the Inbox page, however, so far my idea has gone un-implemented.

In the meantime, I would like to participate in SpamCop's reporting system and am running into a problem. The SpamCop server wants the spam forwarded as an attachment and fails to recognize the spam if I simply forward spam from the opened spam at the TELUS Webmail interface to my established SpamCop reporting e-mail address.

What to do to get SpamCop reporting to work without pulling any spam local to my machine?

Thanks in advance for any help anyone can offer.

Share this post


Link to post
Share on other sites
The SpamCop server wants the spam forwarded as an attachment and fails to recognize the spam if I simply forward spam from the opened spam at the TELUS Webmail interface to my established SpamCop reporting e-mail address.

You have pretty much answered your own question as to why it is not working. To get it working, you may need to figure out how to get the message in a format that the spamcop tool can process. If you can not get your webmail app to forward as an attachment (I know Charter.net upgraded their webmail a while back and broke that functionality), you MAY not be able to submit via email.

The place to start is the spamcop FAQ, specifically, here.

I don't see Telus listed spacifically, but perhaps one of the other webmail apps is close enough to give you hints.

If you figure it out, please post the results back here so that others may use your information.

Share this post


Link to post
Share on other sites

Thanks for posting Steven ... apparently, TELUS' Webmail interface is incapable of forwarding items as an attachment. I am able to look at the full header by utilizing the Message Source command from within an opened spam - however, it displays as a new IE window and could only be cut and pasted into the open spam, then forwarded to my established SpamCop reporting e-mail address.

I haven't tested this yet as I have no new SPAMs to work with, however, I doubt I'll have to wait long. I'll let you and the forum know how I make out shortly.

Thanks again for your help Steven.

Share this post


Link to post
Share on other sites

OK ... that worked (pretty much, I think) ... I got a "Subject: SpamCop has accepted 1 email for processing" e-mail reply and clicked on the imbedded reportiing link. This took me to a SpamCop spam report to complete. However, I did notice one error:

"Finding links in message body

Parsing text part

error: couldn't parse head

Message body parser requires full, accurate copy of message

More information on this error..

no links found"

This is the first SpamCop spam report I've gotten this far with. Is the error referenced above a critical error, or, can it be ignored? Thanks.

FYI - I copied and pasted the full header info display (TELUS Webmail's 'Message Source' display) into the beginning of the body of the open spam e-mail.

Share this post


Link to post
Share on other sites

bummer ... I'll look at the webform next spam I get ... trouble is, if reporting is too time-consuming, it just isn't going to happen.

Thanks for your advice turetzsr.

Share this post


Link to post
Share on other sites
FYI - I copied and pasted the full header info display (TELUS Webmail's 'Message Source' display) into the beginning of the body of the open spam e-mail.

The spamcop parser is looking to see the original ascii source for the entire message, headers and body, to parse.

The email it receives should have the headers for your message to your reporting address, a blank line to indicate the start of the body of your submission, the headers of the spam message, a blank line to indicate the start of the body of the spam, and the body of the spam. Did you paste the entire contents of the "Message source" into the email?

You MAY be able to do it by creating a new message and pasting the Message source into there

-or-

by forwarding the message like you did and replacing the body with the contents of the Message source

-or-

by forwarding the message like you did and adding the Message source before the existing body.

The third one MAY be considered modifying the original message, especially if the body is parsed twice.

I would take one message, parse it with the web form and note the results before canceling the report. I would then try sending the same message one or more of these ways to see if the results match. Then use the best way that matches the web form.

You may also be able to submit multiple messages at once, but that should wait until you have it working for one at a time. For Lotus Notes, I need to export the message to a text file and then I can forward as many attached text files as needed to my submit address. Luckily, Postini removes most of the spam for me before it reaches my server.

Good luck and let us know how things work out.

Share this post


Link to post
Share on other sites
bummer ... I'll look at the webform next spam I get ... trouble is, if reporting is too time-consuming, it just isn't going to happen.

...Well, you needn't feel that you must report everything. Anything you can do is appreciated.

Thanks for your advice turetzsr.

...You are quite welcome.

...Actually, I prefer Steve T (see my sig) -- turetzsr is just my user id. :) <g>

Share this post


Link to post
Share on other sites

Steven ... thanks, all good info ... I'll try the webform next spam I see and also suggestions one and two to compare results ... I've been using the methodology you describe in suggestion three and that is what is producing the current error I describe above.

Hopefully suggestions one or two will be the charmer(s). I'll post back when I know more. Thanks again.

Share this post


Link to post
Share on other sites

One question...does the Message source include the body of the message as well as the headers?

I took your post

FYI - I copied and pasted the full header info display

to mean you only [pasted the headers into the body of the exising spam.

Share this post


Link to post
Share on other sites

Steven ... here's an example of a 'Message Source' display (only) from TELUS' Webmail interface for a newly arrived piece of spam e-mail:

Return-Path: <ejucghyfeaael[at]icq.com>

Received: from pcp08696952pcs.500ash01.tn.comcast.net ([69.137.109.13])

by priv-edtnes81.telusplanet.net

(InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP

id <20040615231810.IRXC23349.priv-edtnes81.telusplanet.net[at]pcp08696952pcs.500ash01.tn.comcast.net>;

Tue, 15 Jun 2004 17:18:10 -0600

X-Message-Info: olo8TLM9YR22bSHZ70LC025avl39q6n21Rc

Received: from pdncca7.catholic.com ([56.228.82.32]) by h83-d.icq.com with Microsoft SMTPSVC(5.0.2195.6824);

Tue, 15 Jun 2004 06:02:52 -0600

Received: from differentepithetduplicableuut3 (crotchety[128.123.102.58])

by yahoo.co.uk (qqen318) with SMTP

id <584786898168nd1548cn>

(Authid: AnnmariePatterson);

Tue, 15 Jun 2004 13:06:52 +0100

From: "Frances Herron" <ejucghyfeaael[at]icq.com>

To: "'K_mcg'" <k_mcg[at]telus.net>

Subject: dont ask me that hour submersible

Date: Tue, 15 Jun 2004 11:03:52 -0100

Message-ID: <1880EI13ICL9$55VJB37NTE3$b5vpv32ba[at]chokeconsularcunninghammb1zoy244>

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="--727639186435188"

----727639186435188

Content-Type: text/html;

Content-Transfer-Encoding: 7Bit

<html>

<body bgcolor="#000000">Cats are great K_mcg

<a href="http://Annmarie.aashipp.com/a">

<img src="http://GSl9qLYp0.asnems.com/sh81">

</a><br><br>

The backbone of surprise is fusing speed with secrecy. - Von Clausewitz (1780-1831) <br> The difference between fiction and reality? Fiction has to make sense. - Tom Clancy  <br> There is more stupidity than hydrogen in the universe and it has a longer shelf life. - Frank Zappa

</body>

</html>

----727639186435188--

... Steven ... that numeric string above is the end of the 'Message Source' display (only) ... FYI - the imbedded 'To' e-mail address, 'k_mcg[at]telus.net', is not mine but similar to mine. This is not something I have done to the 'Message Source' display to protect my real e-mail address - it's how it actually appears. I didn't even have to concern myself with exposing my real e-mail address. This kind of similar addressing is something I see quite a lot of in the spam e-mails I get.

Anyways, to answer your question, it appears the header and message body both appear in the 'Message Source' display.

Does this revelation dictate the testing of your earlier suggestions one or two?

Thanks, Steven

1636PDT15JUN04 edit - suggestion two being tested now

1640PDT15JUN04 edit - suggestion two failed identical to original failure

Edited by Frankenstien

Share this post


Link to post
Share on other sites

Well one thing that may be a problem is that mail headers when they wrap beyond a single line, should have whitespace at the beginning of the line. That it is not showing could be a function of the forum handling or of the copy/paste. It should look something like this:

Received: from pcp08696952pcs.500ash01.tn.comcast.net ([69.137.109.13])

     by priv-edtnes81.telusplanet.net

     (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP

     id <20040615231810.IRXC23349.priv-edtnes81.telusplanet.net[at]pcp08696952pcs.500ash01.tn.comcast.net>;

     Tue, 15 Jun 2004 17:18:10 -0600

Otherwise, it looks like it should parse just fine. Since I have a mailhost setup, I am unable to parse it myself after trying to fix it.

P.S. It may not be your email address you are revealing but it probably is someones. These usually happen because of a dictionary attack.

Edited by StevenUnderwood

Share this post


Link to post
Share on other sites

As StevenUnderwood states, this particular vehicle sucks for demonstrating what you might be seeing elsewhere, due to the tendency for this thing to make "white space" disappear. Howerver, even if we assume that some of the lines actually had the leading white-space to show the "continuation" ... there are some lines in your sample that show issues with line-wrapping, and I don't see what the cause would have been;

Received: from differentepithetduplicableuut3 (crotchety[128.123.102.58])

by yahoo.co.uk (qqen318) with SMTP

id <584786898168nd1548cn>

(Authid: AnnmariePatterson);

Tue, 15 Jun 2004 13:06:52 +0100

Third line should have fit onto line 2

Lines 4 and 5, I find a bit confusing, thinking that these data bits were also appended data associated with the "Received:" line, but why there seem to be additional CR/LF bits after each of these items ...????

Share this post


Link to post
Share on other sites

Steven ... here is a test of copy and paste of 'Message Source' ... the whitespace is preserved in the pasted 'Message Source' portion of the Forwarded spam and to this point in my paste of it into the forum Reply ... I will edit in my observations of the pasted text after I post this newest spam 'Message Source' example:

Return-Path: <KPRNIHOLDG[at]moose-mail.com>

Received: from cm203-168-174-210.hkcable.com.hk ([203.168.174.210])

by priv-edtnes44.telusplanet.net

(InterMail vM.6.00.05.02 201-2115-109-103-20031105) with SMTP

id <20040616022230.WFCS18079.priv-edtnes44.telusplanet.net[at]cm203-168-174-210.hkcable.com.hk>;

Tue, 15 Jun 2004 20:22:30 -0600

X-Message-Info: 588TPC3Pmltd44oZsJM98EZW598kuBqD941

Received: from pigeonhole.KPRNIHOLDG[at]moose-mail.com (q313.yi1137864859.akl-uzf.amw.KPRNIHOLDG[at]moose-mail.com [32.118.234.220])

by fattenconclusion.KPRNIHOLDG[at]moose-mail.com

id GXFON5341; Fri, 18 Jun 2004 13:07:20 -0500

[roustaboutHost SMTP Relay 6.28]

Reply-To: "Trent Thurman" <KPRNIHOLDG[at]moose-mail.com>

From: "Trent Thurman" <KPRNIHOLDG[at]moose-mail.com>

To: "K_l_tasker" <k_l_tasker[at]telus.net>

Subject: coffin

Date: Fri, 18 Jun 2004 23:07:20 +0500

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="--425968784714906388"

Message-Id: <20040616022230.WFCS18079.priv-edtnes44.telusplanet.net[at]cm203-168-174-210.hkcable.com.hk>

----425968784714906388

Content-Type: text/html;

charset="iso-2290-5"

Content-Transfer-Encoding: 7Bit

<HTML><b><FONT COLOR="#FF0000" SIZE=4 PTSIZE=12>

Va<font style=font-size:1px>e</font>1ium, X<font style=font-size:1px>k</font>ana<font style=font-size:1px>r</font>x</FONT><FONT COLOR="#8000ff" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">,..</FONT><FONT COLOR="#800040" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">..Br<font style=font-size:1px>t</font>and Name,</FONT></b><FONT COLOR="#ff0000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff; font-weight:700" PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">YES</FONT><b><FONT COLOR="#800040" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">....</FONT><FONT COLOR="#8000ff" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">the R<font style=font-size:1px>K</font>EAL STUF<font style=font-size:1px>2</font>F !!<BR>

</FONT><FONT COLOR="#ff0080" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">IONA<font style=font-size:1px>F</font>MIN</FONT><FONT COLOR="#8000ff" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">...</FONT><FONT COLOR="#008000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">Ten<font style=font-size:1px>d</font>uate, </FONT><FONT COLOR="#ff0080" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">Adipex, Fastin,...</FONT></b><FONT COLOR="#0000FF" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff; font-weight:700" PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">LE<font style=font-size:1px>b</font>VITRA</FONT><B><FONT COLOR="#008000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BR>

Lo<font style=font-size:1px>c</font>w Pr<font style=font-size:1px>O</font>ice, </FONT>

<FONT COLOR="#008000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=4 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0">

OVE<font style=font-size:1px>O</font>RNI<font style=font-size:1px>U</font>TE</FONT><FONT COLOR="#008000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0"> D<font style=font-size:1px>D</font>livery, PRIV<font style=font-size:1px>t</font>ACY !</FONT></B><FONT COLOR="#000000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><BR>

<BR>

</FONT><FONT COLOR="#0000ff" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=4 PTSIZE=14 FAMILY="SANSSERIF" FACE="Arial" LANG="0"><B>

<a href="http://www.ecqicd.matchless3341rx.us/b12">ME<font style=font-size:1px>l</font>DS_HE<font style=font-size:1px>b</font>RE</a></B></FONT><FONT COLOR="#000000" BACK="#ffffff" style="BACKGROUND-COLOR: #ffffff" SIZE=2 PTSIZE=10 FAMILY="SANSSERIF" FACE="Arial" LANG="0"></B><BR>

 </FONT><br><br><br>

<font style=font-size:1px>

stator bivalve duel mila greenish casino category axial cufflink deuce modern airmail attache apprise tideland bromine oaf compose pyle dubitable airfoil glandular marmalade bureaucracy daimler arsine victoria bodybuild infest romano custer spawn activation mare newtonian pennyroyal gaseous aloha imperceptible rouge meteoritic allspice advocacy heath FI4

baggage shanty aberrate eigenvector cove axes belch commendation dominick dahl dill guildhall dunlop moneymake magpie bolton gestapo quintus alcoa tnt spa acrylic JNG0

cayugalacquer

</font>

</HTML>

----425968784714906388--

2042PDT15JUN04 edit - the elimination of the whitespace is merely an artifact of the forum posting process ... F

Edited by Frankenstien

Share this post


Link to post
Share on other sites

as I pointed out before, there are some major issues ... but can't tell where they're coming from.. You said you'd say something about the white-space issues after posting, but I see no comments about the problem lines.

First bad section is;

X-Message-Info: 588TPC3Pmltd44oZsJM98EZW598kuBqD941

Received: from pigeonhole.KPRNIHOLDG[at]moose-mail.com (q313.yi1137864859.akl-uzf.amw.KPRNIHOLDG[at]moose-mail.com [32.118.234.220])

by fattenconclusion.KPRNIHOLDG[at]moose-mail.com

id GXFON5341; Fri, 18 Jun 2004 13:07:20 -0500

[roustaboutHost SMTP Relay 6.28]

next is;

Content-Type: multipart/alternative;

boundary="--425968784714906388"

This one looks short enough that the second line could have fit onto the first line, but somehow there's a newline code inserted in there, by something, sometime.

Share this post


Link to post
Share on other sites

Poster PM'd me, but I believe the question and answer would be better served by being placed out here in the open.

Wazoo ... thanks for helping out ... I edited in to my last post a one line comment about the whitespace - it appears to be an artifact of the forum posting process and, presumably, not a problem when I'm pasting into the spam to then be reported.

Yes and no ... the "leading white-space" that gets dropped "here" isn't necessarily an issue. But there are other "problems" showing in your samples that go beyond just this part of the white-space thing.

Your other observations about problems with certain elements being line-wrapped are, quite frankly, over my head and I can offer little on those points except to say that I am Selecting All, Copying and Pasting the TELUS Webmail Message Source display into the very first available line of the open spam before submitting to SpamCop.

I'm not 100% sure of what you might mean under the phrase "... of the open spam ..." (also noting that spam is a registered trademark of Hormel's spiced ham profuct) ... but this appears to be the probable source of the problem newline insertions. The catch is, it might be the web-mail display, it might be your OS and how it's handling the copy/paste instructions, and/or it could be this "open spam before submitting" thing ...

your sample;

Received: from pigeonhole.KPRNIHOLDG[at]moose-mail.com (q313.yi1137864859.akl-uzf.amw.KPRNIHOLDG[at]moose-mail.com [32.118.234.220])

by fattenconclusion.KPRNIHOLDG[at]moose-mail.com

id GXFON5341; Fri, 18 Jun 2004 13:07:20 -0500

should have looked more like;

Received: from pigeonhole.KPRNIHOLDG[at]moose-mail.com (q313.yi1137864859.akl-uzf.amw.KPRNIHOLDG[at]moose-mail.com [32.118.234.220]) by fattenconclusion.KPRNIHOLDG[at]moose-mail.com id GXFON5341; Fri, 18 Jun 2004 13:07:20 -0500

Something added in some newline characters, thus "breaking" the header structure.

The submissions are being accepted and I am following an e-mail hyperlink back to a SpamCop spam Report, however, the SpamCop Report composed contains the following error on a consistent basis:

"Finding links in message body

Parsing text part

error: couldn't parse head

Message body parser requires full, accurate copy of message

More information on this error..

no links found"

My understanding is that I may be successfully sending spam reports but that my reports are not registering statistically - apparently a critical failure of what we're trying to accomplish here.

That error message suggests that nothing was successfully parsed, thus you were offered no target selections were offered to send any reports. So would have to agree that thus far, you've wasted a lot of time and effort. One could offer that if you're doing a cut/paste operation, then you could then "massage" the headers such that these extra newline items are corrected, but ... that might put one in position for setting you up to get yourself in trouble for possibly making the wrong "corrections" or a few to many in the wrong place, and as such run afoul of some SpamCop "rules" about "material alterations" ... In that light, "we" have just been trying to point out what the SpamCop parser seems to be choking on ....

Share this post


Link to post
Share on other sites

Wazoo ... you're right ... I've shouldv'e just posted ... initially I was just going to alert you to the edit I added re: the whitespace ... then I got going wit the rest ...

Anyways, re: "... of the open spam ..." - what I have to do with the TELUS Webmail interface is open a spam e-mail, report it to TELUS using a link (command) present only in the open spam e-mail display, then, in the same open spam e-mail display, click on a link called 'Message Source' to display (in a new window) the full header (and body) info - this is what I'm Selecting All of and Copying (Ctrl C in Win98). I then close the 'Message Source' display window, and click on the 'Forward' link (command) in the still open spam e-mail display.

This opens a new e-mail (window/display) that I can paste the 'Message Source' info into at the absolute beginning of the body of the new e-mail. I am then entering my SpamCop submission e-mail address (from an Address Book entry) and sending the newly created 'Forward' e-mail.

I am not introducing any changes whatsoever.

What do you make of my procedure?

I tried substituting the 'Message Source' info for the existing body of the new 'Forward' e-mail - with the same error result in the SpamCop spam report.

Thanks for helping me to come to grips with this, eh?

Share this post


Link to post
Share on other sites
Wazoo ... you're right ... I've shouldv'e just posted ... initially I was just going to alert you to the edit I added re: the whitespace ... then I got going wit the rest ...

On the flip side, you probably won't believe how far I was into answering your PM before the thought came that it all should be in the Forum itself ... doing a "Back" .. and of course, only then thinking that a smarter person would have copied all the typing that had just been performed ... so got to start all over <g>

I am not introducing any changes whatsoever.

Ahh, but the opportunities for these other players to make changes ...

What do you make of my procedure?

You aren't kidding .. what a pain ... multiplied by the fact that it seems to be creating additional problems.

Thanks for helping me to come to grips with this, eh?

Wish I could offer something a bit easier to try, but sitting over "here" just isn't close enough to TELUS to see if there are other options that might be configurable ... but in the hopes of verifying that the issues actually are as we're conjecturing, a PM is being sent for something else to try. <g>

Share this post


Link to post
Share on other sites

Before getting the mail submission working, you should probably try pasting the "Message source" data directly into the web parser and see what that brings you.

If the source you are getting from the document is not recognizable from spamcop parser then as Wazoo stated, it may take a bit of massaging to get it to parse for each spam you are trying to report and it may not be worth it.

Another avenue could be to request from TELUS a method to Forward as attachment (message/rfc822) the full message source. They may be hesitant, however, as I think I remember them on the list several times before and they may not want to promote SpamCop usage.

*EDIT* The other way to report these to spamcop would require downloading them to a local client which you were trying to avoid originally. You should then be able to forward as attachment. If you have IMAP access to that mailbox, the spam could stay on the server and still forward it using your local client.

Edited by StevenUnderwood

Share this post


Link to post
Share on other sites

Steven ... I have yet to try the web parser ... keep forgetting at the opportune moment ... will make a point of trying it and report back here.

I've been communicating with a dude named Dale at Abuse Teluscom - 'abuse[at]telus.com' - he's the one who put me onto SpamCop in the first place - he keeps trying to get me to pull spam local to my machine to deal with it and I keep explaining to him that I want to deal with it server-side. Anyways, apparently, no mechanism exists to forward the 'Message Source' info as a standalone attachment, however, there is an 'Attachment' link (command) in a newly opened 'Forward' e-mail that allows one to browse to a file on one's own machine - I suppose I could save the 'Message Source' info as a local file and then attach it to a newly generated, blank, TELUS Webmail e-mail. However, one has to balance cost (in time) versus benefit. I seem to be in pretty deep time-wise.

Wazoo ... still waiting on a fresh peice of spam to try what you suggested ... shouldn't be long.

Share this post


Link to post
Share on other sites
Wazoo ... still waiting on a fresh peice of spam to try what you suggested ... shouldn't be long

No doubt, at least 30 here since my last post <g>

Share this post


Link to post
Share on other sites

Actually, you folks won't hear from me for several hours ... I'm in a full leg cast for a torn Achilles and have to go downstairs to do laundry - gotta stay there for the afternoon as I cannot get up and down the stairs very easily at all (haven't even tried it yet - wish me luck).

Will pick this up later.

Share this post


Link to post
Share on other sites

oh sure, remind me of the stuff I should be doing <g> ... dishes in the sink, laundry, yard needs mowed, destroying yet another wire clothes-hanger to re-connect the tailpipe to the rusted off collector point on the headers of a Ford van so I might get another couple of weeks without a ticket for excessive noise, tearing apart the cooling system on the pick-up to replace the leaking heater core ... on and on ... discussing with myself about the lunacy of sitting in the 90+(F) degree house in front of this system instead of doing at least one of these tasks <g> .. enjoy the downstairs time <g> good luck with the healing and recovery.

Share this post


Link to post
Share on other sites

Wazoo ... OK ... made it back up the stairs by dragging my sorry ass up step by step ... anyhow, I just CC'd you in on one of my SpamCop spam submissions, followed by another Forward of the spam all by itself with the words "from Frankenstien (forum) " appended to beginning of Subject line.

FYI - In the SpamCop spam submission, I have pasted the TELUS Webmail 'Message Source' display info in at the very beginning of the body of the spam message being forwarded, as I have described in detail earlier.

Share this post


Link to post
Share on other sites

From what I received, I would say that the SpamCop parser choked again. There is definitely something wanting to wrap / add a new-line / at about 80 characters ... the first bad split did reach out for 83 characters before breaking at a hyphen ... the other did split at 80 columns ... if there's not a line-length setting in the web-mail app, there may be something related to screen size / resolution ... or maybe just an old app written back in the days when an 80 column display was a defacto standard????

The second paste-in appears to be un-needed ... it gets wrapped by the lines;

----- Forwarded message from kzeutij[at]icq.com -----

----- End forwarded message -----

At best, this will be ignored ... at worst, even if you fix the headers, there may be some parser issues .... and all this section contains is a plain-text version of the HTML encrusted spam message ... again, not needed, and worse, the "Forward" lines included don't match up or take the place of "boundary lines" referenced/defined in the header.

Perhaps in talking to your TELUS guy, maybe there's an option to kick the web-mail app up to a 132 column line-length?? Though not sure I'd want to guarantee that this would "solve" the problem (off the top of my head, I'm thinking that the RFC line-length limit was something like 200 charachters)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×