cannot forward spam to spamcop via yahoo mail

[fragile]

In the last few days I have been unable to forward spam as an attachment to spamcop through using yahoo mail. I can send other email from yahoo with no problem and can forward as long as I don't do that Shift-Alt-F keystrokes for forwarding as an attachment.

Has anyone else experienced this lately? I had been using that keystroke combination for quite some time with no problem.

My Webpage

There is a screenshot of the error message.

thanks

[Farelf]

Still works for me fragile (trying just now) - once the addressing dialog is complete I use Ctrl-Enter to send, as advised by the pop-up balloon seen when hovering on the "Send" button.

[fragile]

Still works for me fragile (trying just now) - once the addressing dialog is complete I use Ctrl-Enter to send, as advised by the pop-up balloon seen when hovering on the "Send" button.

Thanks, well I seem to have narrowed it down to basically one type of spam I'm having the problem with. Actually it boils down to one particular message I seem to get over and over in my spam folder on yahoo. The sender calls himself Canadian Pharmacy and the subject is this: "Viagra (30 pills 100mg) USD 81.90 & Cialis (30 pills 20mg) USD 91.50".

I keep getting that same spam in my box almost every day and whenever I try to forward the attachment to spamcop, I get the message cannot be sent error from yahoo. I can forward any other spam from yahoo to spamcop no problem.

So I guess yahoo must be flagging that message somehow by sender or subject or something and identifying it as spam and not letting it through? I can't think of any other reason?

thanks

[Farelf]

Thanks for the follow-up.

...So I guess yahoo must be flagging that message somehow by sender or subject or something and identifying it as spam and not letting it through? I can't think of any other reason? ...

Maybe, I know nothing about Yahoo policies at this stage but wish providers in general would quit interfering with submissions as so many do. Okay, they are trying to prevent relaying but a little co-operation in spamfighting would help in that "war".

I would try pasting the source text into the submission form on your reporting account member page just to see how it parses - and to have the satisfaction of submitting a report for at least one instance and maybe grab a tracking URL for further discussion if required. Probably botnet, going by the mindless reiterations, with implications of endless "whack a mole" play - but it seems there are many kinds of botnet, some seemingly not entirely made up of illegally suborned machines (accordingly, perhaps, with different implications about the effectiveness of reporting the sending servers).

[cwg]

You get that message because the Yahoo inverse spam filtering agent detects you as trying to send spam.

[Farelf]

Ah, the botnet spamming one of my "free" webmail accounts (not Yahoo) has re-awoken. Not, as lately there, the tedious "Adriana" with her endless but cruelly unfulfilled promises to commit sundry indignities upon my pale and flaccid flesh but "Canadian Pharmacy" once more to the fore. Different subject line but it might be interesting to compare with "your" flavour:

http://www.spamcop.net/sc?id=z5511703815z9...50c571725087d5z

http://www.spamcop.net/sc?id=z5511712476z3...46a1cdbc57d6fez

"Mine" seems to be characterised by SC's continual "www.(such and such) is not a routeable IP address" in connection with the spamvertized link which is generally false and has been commented upon elsewhere. www.(such and such) is probably quite new in each instance (not that important to me and haven't checked), certainly in the second of the above was not yet fully promulgated and actually quite hard to resolve. Only to have SC devnull the found abuse address, probably because the IP address is in a transitional assignment or something (I don't know). Usually they resolve just fine - for anyone but SpamCop, it would seem.

Previously the sending servers were almost always listed in the CBL with indications of compromise (often with the specific exploit nominated). That seemed to stop just before it all went quiet with new, unlisted spambot servers appearing instead - and now, on resumption, they are again unlisted ones.