Jump to content

rgvodden

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About rgvodden

  • Rank
    Newbie
  1. I just want to thank everyone for their time and assistance. -Graham
  2. Thanks Ellen, Point of Claification. I am not a Rightnow Technologies employee. I run a support department that uses their software, and is hosted on their servers. Cheers! -Graham
  3. Chris, I'll have our sysadmin whitelist this IP as soon as he returns from vacation (in Mexico). -Graham
  4. Hi Chris, Thanks for the heads-up. I'll pass that along to the support team at rightnow tech. The support system assigns an incident tracking number to every email it receives, and auto responds with that tracking number. If the original email contains a forged address (from a spammer, or as the result of a virus), how can they tell that they should not respond? Basically, you can't always compare the reply address to the email server, and expect them to line up. Many organizations legitamely relay through a single unified server which does not match the domain of the reply address. For example, our product is web-based, and emails are sent from our server, on belalf of our clients (using a reply address that they specify). So for 100% of the email sent to our clients' customers, the reply address does not match the server domain. This is a bit of a pickle.... -Graham
  5. Wow! Response within 2 minutes... Here's the report: Query bl.spamcop.net - 216.136.168.81 216.136.168.81 is utilsc01.rightnowtech.com (Help) (Trace IP) (Senderbase lookup) 216.136.168.81 listed in bl.spamcop.net (127.0.0.2) Since SpamCop started counting, this system has been reported about 10 times by about 10 users. It has been sending mail consistently for at least 93.8 days. In the past 720.2 days, it has been listed 22 times for a total of 21.7 days In the past week, this system has: Been reported as a source of spam less than 10 times Been witnessed sending mail about 140 times A sample sent sometime during the 24 hours beginning January 27, 2004 4:00:00 PM -0800:
  6. rgvodden

    A simple request

    Here's a thought: - Email the ISP in question - View the header of the email you receive in response. - note the IP address in the email header (or do a NSLookup on the server) - Search for that IP address on www.spamcop.net In theory, it should work.
  7. My Issue: I am the Support Department lead for a software company, and we use the RightNow Web knowledgebase and ticketing system. Yesterday, Rightnow's email server was blacklisted. This server is their primary email gateway for all of their hosted customers (see http://www.rightnow.com/customers/ for some of their clients), and as a result, my support department can not send email to anyone using the Spamcop as a blacklist agent. Now here's the kicker... WE use Spamcop as one of our blacklist agents, so my support team can not even receive notification of new incidents which require their attention. My Point: I am all for anti-spam. I just think that there also needs to be a registry, or a setting with higher tolerance for systems like RightNow's. Their primary product is a support system, and is relied on by companies like British Airways, Electronic Arts, AT&T, and the US Social Security office). Currently, we have to wait 48 hours before we can trust that our emails are reaching their recipients (people we are contractually obligated to respond to within 24 hours). The Discussion: What can be done to create a list of "approved" servers? Your thoughts are appreciated.
×