Jump to content

mrmaxx

Memberp
  • Posts

    820
  • Joined

  • Last visited

About mrmaxx

  • Birthday 09/02/1964

Contact Methods

  • Website URL
    http://
  • ICQ
    0
  • Yahoo
    jmaldrich

Profile Information

  • Location
    Dalton, GA
  • Interests
    Photography, my cats, computers, my house... :-)

Recent Profile Visitors

3,031 profile views

mrmaxx's Achievements

Advanced Member

Advanced Member (3/6)

0

Reputation

  1. Anyone know the ETA on IP V6 reporting? Even guesstimate would be nice. I have a couple nice, juicy spams waiting to report, but SC wont' accept them because they are IP V6.
  2. +1 Googleplex! I just had a spam fail to parse for *exactly* this reason! Can we not just ignore IPV6 until such time as they start handing them out? Of course, you should continue working on the IPV6 support code, but don't break parsing just because one INTERNAL handoff in IPV6.
  3. Ok. Problem is resolved... turns out that Petzl got it right... The user had subscribed to a pay service that handles keeping antivirus, etc up-to-date and when I called that service they walked me through how to fix it so the computer would boot back up normally... had to remove a driver file that their software installed and once that happened, we were good to go... 'Preciate it!
  4. One of my users at work asked me to look at his machine from home which is running Windows Vista Home Premium. It was working fine until Tuesday night / Wednesday when it got an update from Microsoft. After that, it rebooted and now it will only give a blue screen at boot with error 0x0000007E. Google search doesn't turn up much helpful. I've got the original install media, but would rather not reinstall Windows if I can help it. This is remarkably similar to a problem that Windows XP users are having with KB977165. Anyone here know how to fix this problem on Vista machines? I'd really rather avoid reloading the whole computer. I just did that for a machine at work yesterday and it took all day to load Windows and get all the updates!
  5. Not to be flogging a deceased equine, but when I went into my SpamSource configs, I noticed there was a button marked "repair" and upon clicking on that, it gives some options for repairing mangled messages, such as reformatting headers, etc. Should any of those options be enabled?
  6. FWIW, Don D'Minion has given his blessing to SpamSource. Of course, it's still a good idea to double-check everything before hitting "send reports." Still, I thought I'd pass it along. Moderator edit 12-3-09 - Actually Don has NOT given his blessing to any third party tool that would attempt to fix the problem with Outlook's failure to maintain proper headers, but he did provide a list of third party tools that try to address the problem. see Here is the boilerplate on Outlook... Note: discussion that follows has not been edited, but this initial post was edited to avoid "a misrepresentation of what was actually said" - dbiel -
  7. Yeah... I've got a new antivirus I'm testing. It's Vipre from SunbeltSoftware. I'm not sure where that BCC line came from, but... anyway, I'll copy my post and email it to the deputies for review. I suspect they will want more than one sample before giving SpamSource their blessing.
  8. Question -- I've got SpamSource 4.0.10.98 installed on my Outlook 2007. Does that fix the problem or is it still forbidden to submit via email from Outlook? Since I receive my work email on another computer that doesn't use Outlook as well as my main machine which *does* use OL2007, I can submit from that machine, if necessary, but it would be nice to be able to submit from my desk at work. :-) Note: I have compared the results of two spam messages I received at work and initially used SpamSource to forward to SpamCop from my Outlook 2007. At a glance, the results are identical. I *did* cancel the ones I forwarded using SpamSource to be sure I did not violate any rules, however I did end up reporting them using "forward as an attachment" from my linux box at home. Further, reports can be reviewed as follows -- Outlook version (NOT reported): http://www.spamcop.net/sc?id=z3315769724z3...f7f64272f63645z Non-Outlook version: http://www.spamcop.net/sc?id=z3315804596z3...ca12e2a134942ez I'd give you the other spam, but I cancelled it before I parsed it so SpamCop does not have any traces of it from the Outlook version.
  9. Neither of those two things describes my issue. This is mostly normal mailing list traffic which is being sent to my Yahoo account. I'm not getting an "invalid login" error either. I did get a message, something like "error 4" one time, but I had just reset my password on both Yahoo and SpamCop so there was a decent chance I hadn't gotten the passwords synchronized yet.
  10. FYI, it appears Yahoo has broken things again. I've got a bunch of email in my Yahoo account. I don't see any errors in my pop list, but it also doesn't appear to be downloading Yahoo mail any more either. I'm still on Yahoo "classic" but they've changed things around again. Probably in order to get us to pony up the $20(US) for "enhanced" access (including pop access.)
  11. Kewl. It does appear to be b0rken at this time, unfortunately. I have a bunch of email in my Yahoo account, and I guess I'm just going to have to read it on Yahoo's site for now.
  12. And as stated in my PM reply... no problem. I wasn't sure if it belonged in the Feature Request section or in the e-mail section. :-) Keep up the good work, Wazoo.
  13. Recently I got in a hurry and didn't pay attention to what I was doing and whitelisted & released a bunch of spam from my held mail folder. I'm slowly deleting the bad whitelist entries, but it would be nice if SpamCop would "auto-clean" my whitelist or at least give me the OPTION to do it when reporting spam. Heck, even if I had to report 'em one-at-a-time, it would be worth it if there were a checkbox to "remove this entry from the personal whitelist" or something? Just a thought. It would help people like me who get in a hurry and whitelist a whole bunch of spam. Another idea would be a "filter" in the whitelist to show all the "new" whitelist entries for the past X days (say 30) for those of us who have done stupid stuff like this so we don't have to wait for spam to get through on the whitelist. Thanks Maxx
  14. Yeah... me too. *sigh* Oh, well... Wish I could remember Julian's email... Hmm... <EVIL GRIN>
  15. Nooo, not really. I mean a real "Oops. We see the problem, we know where the problem is, should be fixed in a bit." That was just a "Oops. I can verify the problem. Bug Report filed." I do that all the time with MY users, so I know exactly what that means... it means "I've informed someone who can actually DO something about the problem and it'll get fixed when they get around to fixing it." What I would recommend doing is backing out the changes until you can fix it so that there are no unintended consequences, such as those that we are seeing. That's just my 2¢ though.
×
×
  • Create New...