Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Verizon's Aggressive New Spam Filter Causing Problems

Posted by ScuttleMonkey on Mon Apr 24, 2006 11:02 AM
from the annoyances-and-other-corporate-bothers dept.
aviancarrier writes "Verizon DSL has turned on a very aggressive spam filter that is blocking lots of long-time legitimate emails. Emails get bounced with an error: 'XX@verizon.net: host relay.verizon.net[206.46.232.11] said: 550 Email from your Email Service Provider is currently blocked by Verizon Online's anti-spam system. The email "sender" or Email Service Provider may visit http://www.verizon.net/whitelist and request removal of the block.' That whitelist web page lets you request one address at a time to be whitelisted with no guarantee for their response time to process it. I have tested multiple email sources and only one got through. As a VZ customer, I just spent 28 minutes on a call to tech support, eventually got a supervisor who knows nothing about the new spam feature, and would only agree to email a manager who doesn't work weekends about it. I warned her that VZ has a public relations problem but she was too clueless to understand." Many users have submitted this problem so it seems to be a pretty far reaching problem. There is also a discussion going on over at Google about this problem.
+ -
story

Related Stories

[+] Ask Slashdot: How Pervasive is ISP Outbound Email Filtering? 281 comments
Erris writes "A member of the Baton Rouge LUG noticed that Cox checks the text of outgoing email and rejects mail containing key phrases. I was aware of forced inbox filtering that has caused problems and been abused by other ISPs in China and in the US. I've also read about forced use of ISP SMTP and outbound throttling, but did not know they outbound filtered as well. How prevalent and justified is this practice? Wouldn't it be better to cut off people with infected computers than to censor the internet?"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • I went to the referenced URL and it sure looks to me like, using the
    ISP form, you can request multiple domains and multiple IP addrs in a
    single request.

    Also, the discussion over at Google currently has a whopping 6 entries.

    Much ado about nothing?
    • This sytem from Verizon is a step in the right direction. AT&T's spam blocking is totally lame, wish they would learn a thing or two from their competitors. I do admin my own domains but keep my at&t for special purposes. It is possible to filter over 99% of spam through a combination of techniques.
      • Yeah, this system from Verizon is junk. It blocks legitimate email constantly. We currently have 2 businesses in the same building. For some reason, Verizon is constantly blocking one of our business domains from the other business domain. And no amount of phone calls or emails or removal requests have done anything for us. We will shortly be moving to a new provider.
      • Actually, no, the system from Verizon (VOL) is not a step in the right direction.

        Imagine the impact to email in general if EVERY ISP and company use such a bonehead system. Everytime you sent email to a new person (customer / client,) you would have to *find*, then fill out some bizzaro web form. MAYBE in a week or so you will finally be able to send your email. Exactly how does this help things???

        VOL's problem is that the group running their email service is a bunch of totally incompetant BOFH a-holes. Ins
        • Pesky Supervisors! (Score:3, Informative)

          by Anonymous Coward
          Error "550" has a couple of causes. The cause that you're experiencing is what is called a "whitelisting issue". Unfortunately, Tech Support has nothing to do with this process. Its entirely managed by the Verizon Anti-spam team. You can access and fill out a form at www.verizon.net/whitelist.

          I've spent a fair amount of time tracking down the error that you're looking at. Its primarily caused by 2 things. Your server sends Verizon spam or its misconfigured.

          1. Your server is a known open relay or h

    • Also, the discussion over at Google currently has a whopping 6 entries.

      Much ado about nothing?

      It has probably not reached epidemic proportions yet, but as a former Verizon DSL customer, it does not surprise met that their idea of SPAM filtering is to block most legitimate incoming traffic. They tend to have a brute force approach to technical problems. Their tech support has been spotty for a long time; I would sometimes get really sharp people who could scope something out in minutes, other times I wo

      • Perhaps the "we" that decided to run the story could have devoted a bit more time writing or editing the article synopsis? Perhaps even make it factually correct wrt to the ability to whitelist multiple domains/ip addrs with a single request (which the summary says must be done one by each)?

      • by ModExec (970413) on Monday April 24 2006, @12:42PM (#15191142)
        As a Verizon DSL custmoer, I can attest to there being a problem. For the past 18 months, Verizon has refused to pass along listserv messages forward to my verizon.net inbox from my university email account. Emails from individuals that are addressed to my univeristy made it through the spam filters fine. But emails from my university's listserver were blocked. All of them.

        I called Verizon about it in January after I realized it was happening. I suspected it had been going on since I got my DSL service, but at the time just assumed that I had been unsubscribed from all of my school's listservs (because of some crazy mix up regarding my academic year, my switch from an undergrad to a law student, etc. Don't ask...). Verizon opened an Operation Control Services (OSC) ticket to look into the matter. After four months of investigating, dozens of calls, hours of talking to tech no-support, and five OSC tickets later, the matter still is not resolved.

        During the time we were diagnosing the problem, OSC asked for the error code that my university received whenever it tried to forward messages. My college's IT department told me that they received an error 450 for every message: "Deferred: 450 Requested mail action not taken-Try later:sv11pub.verizon.net (from relay.verizon.net [206.46.232.11])." According to OSC, this meant that the Verizon mail server could not verify that the listserv messages being forwarded actually originated from the listserver domain. Given my school's list server set up, this makes perfect sense; users on the listserv may send an email to the server's listening account, which takes messages and creates a new message to blast the original message to all the listserv's recipients. The intermediate listening account seemed to be a legitimate way to relay messages to recipients.

        Apparently, that didn't fly with the Verizon servers. OSC engineers thoroughly explained the problem in my account's notes, "Sender cannot be verified, which is the cause of their mail issue. NOTE: 451 ... Requested mail action not taken: mailbox unavailable. Whitelisting will not help. They will need to correct the config on their mail server." This made no sense to me, to my school's IT department, and even to the Verizon tech who tried to interpret the notes. Apparently, what these notes meant to say was the university's servers did not comply with some sort of internet standards for mail routing. Despite there being a legitimate use for the messages, Verizon would not create an exception in the hallowed standard to accomodate the forwarded messages. Verizon's OSC recommended that I tell my school's IT department that it was their servers that did not comply with the standard -- that if they wanted Verizon to accept their forwards, they needed to reconfigure their listservers. This was incredible. For what it was worth, I relayed this to my school's IT department. Not surprizingly, they have made no changes. Why fix what works with 99.9% of the ISPs out there? Whoever said Verizon was using brute force tactics to do business has hit the nail right on the head.

        But this is not the only problem at Verizon. One month ago, they had to suspend their entire "Block Senders" database because it got so large that the Verizon server couldn't process the messages through it. As I understand it, the database caused a number of hiccups, blocking hundreds of legitimate messages and letting through as many or more spam messages. To this day, Verizon has not reintstated users' "block senders" email option.

        This is not to mention the fact that Verizon is notorious for not following up with its customers. Over the four months that I tried to get a resolution, only once did I ever receive a call from a member of the supervisor escalation group, informing me of any "progress." In an effort to keep myself in the loop, I would call the verizon tech no-support department, only to find that that my OSC ticket had been closed without notice and without resolu
      • You wouldn't have.

        Zonk on the other hand would run it today, and again tomorrow.

        *ducks*
  • 28 minutes? (Score:5, Interesting)

    by Jordan Catalano (915885) on Monday April 24 2006, @11:06AM (#15190429) Homepage
    Here's a trick for Verizon Online phone service: Call up, listen to menu items, then say -nothing-. Don't ask for an operator, don't enter in your phone number: just chill for about two minutes while the prompts repeat. In under three minutes, you'll be transfered to a live operator.
    • Re:28 minutes? (Score:5, Informative)

      by gEvil (beta) (945888) on Monday April 24 2006, @11:12AM (#15190478)
      Bookmark this page. [gethuman.com] It will be your best friend.
      • Re:28 minutes? (Score:5, Insightful)

        by LMacG (118321) on Monday April 24 2006, @12:43PM (#15191151) Journal
        [Full disclosure for the following comment -- I program voice response systems for a living. However, I only implement what they force me to, and sometimes that sucks.]

        From that page:

        We will soon publish a list of the best and worst mass-market consumer companies in the US based on how long it takes to get to a human on the phone and on the quality of support received.


        That's very nice, but it doesn't seem like a very intelligent way to measure customer service. As a trivial example, suppose you want to know your credit card balance. A decently programmed voice response system can give you that information quickly and clearly, and in much less time than it would take to get the same data from a human. If you're lucky, the IVR won't even try to sell you something that you don't need.

        Yes, I know that there are times when the available pre-programmed options are not useful and speaking to a representative is the only option. But do you want to have to wait in queue for an agent who has to handle ninety-twelve "what is my balance?" calls before it's your turn? Now ask yourself why the call centers are being outsourced to overseas providers ...

        This "I only will deal with a human" attitude is pointless. Better to demand that corporations fix their IVR systems, because they're not going away. (And maybe I'll get hired to write more VUI specs instead of having to implement what 'the business' thinks it wants.)
        • If it's a straightforward "what's my balance" question I won't even call - that's what the website is for (if they don't have a decent website, I don't do business with them). The _only_ time I call companies (I'm a geek, real human-human conversation scares me!) is when there's something wrong I need to speak with someone about. Thus, any system which hinders that is a PITA.
        • When I just need my card balance, I check the web site. I haven't _called_ for my balance in 8 years.

          When I call in, it's because I have a problem or a question that isn't answerable by automated systems. After spending the last few years exploring phone trees exhaustively before finally saying "Yep, they can't handle it" and getting to a rep, I'm perfectly happy to rate companies on how easy that last step is.
  • by terrahertz (911030) on Monday April 24 2006, @11:08AM (#15190445)
    ...you need to power-cycle your DSL modem, disconnect everything but a single ethernet cable from your modem to your PC, reboot your PC, count to 30 while hopping on one foot, and say the alphabet backwards first before anyone at Verizon will turn on their brains and acknowledge they have a problem. Plus...28 minutes on the phone?? Pffft. You don't get the "real" tech support until they keep you on the line for at least 60 minutes.

    Don't you know how they troubleshoot already?

    • "Sir... Sir... I'm going to have to ask you to find your Start Button."
      "I have OSX"
      "Sir... I understand, but I need to walk you through this. Please locate your Start button."
      "You don't understand - I'm on a Mac, I don't have a Start button."
      "Sir... You're not making this any easier. Once we go through this we can identify your issue."
      "Actually, my issue is that my cable modem arrived without a power supply."

      - Actual conversation I had with tech support. Long live tech support. Long live tech support scripts.
  • by Abalamahalamatandra (639919) on Monday April 24 2006, @11:09AM (#15190447)
    I ran a bulk-sending system (legitimate!) to email Frontier Airline's frequent flyer members, and Verizon was the biggest single problem getting mail through. I don't think I ever did get them to accept our runs at all.

    The big thing they already had in place was that they want to connect back on port 25 to the sending system AND make sure it responds initially with the same name it's using to send mail out. Not a bad thing overall, I suppose, but I can see how it would block quite a few messages from providers that use separate sending servers from their receiving servers. I finally had to set up SMTPFWDD on both outgoing servers to accept connections and silently drop any emails they get, that helped, but I think they still rate-limited heavily.

    I'd say if you depend on getting your email, Verizon's not a good ISP to use.
  • How about the holy-crap-thank-you-for-the-whole-error-message-wh ere-is-the-stack-trace department?

    - Andrew
  • Now thats rich. (Score:5, Interesting)

    by The Cisco Kid (31490) * on Monday April 24 2006, @11:10AM (#15190463)
    Verizon is a spam sewer itself.

    http://www.spamhaus.org/sbl/listings.lasso?isp=ver izon.net [spamhaus.org]
  • by Minwee (522556) <dcr@neverwhen.org> on Monday April 24 2006, @11:11AM (#15190471) Homepage
    "I warned [a tech support supervisor] that VZ has a public relations problem but she was too clueless to understand."

    Having worked in tech support for a large company, I can assure you that the position of supervisor for a tech support call centre really doesn't have nearly as much influence on coprorate public relations as you seem to think that it has.

    Most of the people in her position would be surprised to find out that any one from the head office even knows that they exist, let alone cares about what they do or asks their opinion on issues like PR. It's normal to be annoyed when a company like Verizon screws up like this, but lashing out at the tech support staff just because they're the easist people to reach really doesn't help anybody.

    • Having many friends who work in call centers for "tech support", they tell me this supposed "supervisor" is actually just the person sitting next to them.
    • Thats just another way of saying "I'm no good at my job". Whether you feel appreciated by your corporate overlords or not, you're a customer facing part of the company and you are therefore every bit as important to PR as sales. Even more so in a large way - anyone calling tech support *already has a problem* and your attitude and ability to solve that problem are a *huge* PR influence.
      • by bunions (970377) on Monday April 24 2006, @11:44AM (#15190730)
        Saying a phone line tech support manager is bad at her job because she can't do anything about an engineering 'feature' in under two days is impossibly naive.
      • It's much easier to cause a problem than to solve one. Sure, you could start a 'PR Nightmare' in a low-paying customer-facing position, but you're not empowered in the slightest to actually solve them. It's not as if the 'supervisor' in a tech support centre has the authority or influence to actually change anything, especially in a company as large as Verizon. Just as important to PR as sales? Not really. Sales (executives in the larger companies) get to actually change PR. Tech support merely tows t
    • Verizon keeps the support centers completely isolated from any of Verizon's actual workings. I'm pretty sure the support people have no ability to contact anyone at Verizon, no matter how far a call is "escalated." This way, Verizon can happily ignore complaints and/or drag its feet as much as it wishes. What are us customers going to about it? Verizon is an entrenched monopoly. It owns the lines. Except in some very rare cases, our only choice is to suck it down.

      What you say is true, of course. It's
    • It's normal to be annoyed when a company like Verizon screws up like this, but lashing out at the tech support staff just because they're the easist people to reach really doesn't help anybody.

      I disagree. Part of the what is so frustrating about dealing with a company like Verizon is the massive diffusion of responsibility. It is almost impossible to get a hold of someone who is really responsible and accountable to you, because everyone's job is so specialized and compartmentalized. If they can't sol
    • by Anonymous Coward
      Most of the people in her position are, in fact, employed by an outsourced call center - likely either in Canada or in Dallas/Ft. Worth; At best, they are the people who managed to make people /feel/ /better/ (not necessarily solve the problem) and get them to hang up quickly - over a period of nine months to a year, and are then bumped to a level II tech.

      I worked at one of these outsourcers. Most of the intelligent & ethical tech pros there were diligently finding other employment as fast as they could
  • by amstrad (60839) on Monday April 24 2006, @11:12AM (#15190488)
    Attempts to contact Verizon to verify claims have been met with resistance.
  • by aviancarrier (570516) on Monday April 24 2006, @11:19AM (#15190538)
    Sometime this morning two of my email addresses got whitelisted and could get through again to Verizon Online. Earlier in the morning I received form emails from Verizon's whitelist group saying they have attempted to contact the blocked company/domain.

    Regarding the person who accused me of being a spammer: No. Just a husband trying to email my wife's VZ account.

    Regarding the "lashing" out at the customer service supervisor: I was trying to get her to help her own company out. The fact that she was not told anything about a new level of spam filtering nor had (she claims) a way to contact a manager on a weekend about a PR problem may be a standard problem for that level of supervisor, but I wanted to give her a way to be a hero internally and stop a PR problem from getting worse.
    • Regarding the "lashing" out at the customer service supervisor: I was trying to get her to help her own company out. The fact that she was not told anything about a new level of spam filtering nor had (she claims) a way to contact a manager on a weekend about a PR problem may be a standard problem for that level of supervisor, but I wanted to give her a way to be a hero internally and stop a PR problem from getting worse.

      This has been posted a bit in the main thread, but I'll restate it: the "customer s

  • by gEvil (beta) (945888) on Monday April 24 2006, @11:22AM (#15190558)
    Emails to Verizon to find out more information have gone unanswered...
  • Just a quick note, I run an email service, and I've had the most problems getting past blocks from:

    AOL
    Excite
    Comcast

    The easiest was AOL, they have a number you can call 24 hours a day to get removed (but it takes 48 hours for the removal to take effect). The other two have been blocking mail from my servers for two weeks. I have filled out contact forms, and left voicemails to no avail.

    I haven't recieved a complaint about Verizon yet, but that could be because I have SPF records.
  • Unfortunately, email spam fighting is always more work than you'll ever have resources available for, and it'll never be 100%.

    Even if you let users manage it, about 60% of them won't have a clue, they'll bollocks it up for themselves, and they won't be able to distinguish between your web appliance and the OEM Norton Antispam which continually misconfigures itself again and again.

    I wonder if we should just ban email altogether so that we can actually get some other work done.
  • This is ironic considering Verizon is one of the major SOURCES of spam. We've ended up wholesale RBL'ing most of their DUL space. Here's a good Sendmail-based blacklist [blogspot.com] to start with.

    Generally speaking, I think it's a good idea to implement something like this, but the problem with Verizon is that they need to filter port 25 on their broadband IP space first and foremost, like AOL and Bellsouth and many other providers are starting to do.

    Ultimately, what Verizon is doing is not a bad thing. It will force
  • by AFCArchvile (221494) on Monday April 24 2006, @11:36AM (#15190665)
    I warned her that VZ has a public relations problem but she was too clueless to understand.


    Perhaps she was too jaded from hearing customers complain that Verizon has a PR problem.


    "We don't care. We don't have to. We're the Phone Company."


    From what I've heard (and what I experienced from having their service in the second half of 2000), this is nothing new for Verizon. They're only interested in the money-making aspects of the telecom business, and drag their feet on everything else. The setup of this aggressive new spam filter was probably one of those "money-making" items, since it means far less spam traffic and decreased accusations of hosting spam bots. Of course, when customers start complaining that they can't send email to specific addresses, they have to deal with Verizon's understaffed, undercapable customer service departments, who will most likely be faced with fierce opposition from the suits in opposing the "grand money-saving, liability-reducing spam filter".


    Also, keep in mind that when Verizon acquired MCI, they acquired UUNet, a tier-1 ISP with some serious spam problems of their own [infoworld.com]. I wouldn't be surprised if taking on UUNet's elephant-on-their-back was part of the rationale behind the new spam filtering policies.

  • This is a major PR issue! I'm sure if you contact them, the New York Times will run a front page article about the lack of a guaranteed response time for Verizon's whitelisting service. That is, unless anything else at all happens on the planet today.
  • At first I was thinking, "'discussion at google', doesn't he mean usenet?" But apparently he was correct since google seems to have extended usenet to have their own "groups" that aren't actually in the usenet heirarchy.

    Oh wow, now I see they are also hosting mailing lists as "groups" as well. Way to muddle the terminology; I guess that is the point. I hate marketing/advertising people.

  • As always, in such things I may be mistaken, or the condition may be transient, but I no longer seem to be able to access their web-based email with Firefox for Windows 1.0. It used to work perfectly. Of course, IE works...
  • Huh? (Score:3, Insightful)

    by voice_of_all_reason (926702) on Monday April 24 2006, @11:45AM (#15190733)
    Why is Verizon blocking any of it's customers' mail by default and then putting the onus on them to fix any problems that arise in the first place? This should be an opt-in service for those who want to make sure they don't miss anything.
  • My company implemented my blocking methods [freesoftwaremagazine.com] and saw an instant reduction in spam from a deluge to a tiny trickle. The three most effective filters are:

    1. Requiring HELO,
    2. Rejecting non-FQDN HELO strings ("foo.bar" will get you in, but "myleetmailserver" won't), and
    3. Rejecting HELO strings that blatantly lie (you're not "localhost" or my public IP address, no matter how many times you ask).

    More and more ISPs are starting to implement the same compliance checks. Would any of these reject your system's mail? Several of our customers had misconfigured outbound servers and we helped them fix their systems. We were only early adopters, though; if we hadn't caught the problem then a major ISP or five would have started rejecting their email without being so helpful.

    Maybe VZ is in the right this time. Are you sure they're not?

    • I been noticing that lately with AT&T (previously SBC) DSL where recruiter emails are landing in the spam box. Makes me wonder if I should respond to these emails if they can't get by a spam filter. Fortunately, nearly all of them are jobs that I wouldn't consider anyway.
    • Messages in bottles. (Score:5, Interesting)

      by Kadin2048 (468275) <slashdot@kadin.xoxy@net> on Monday April 24 2006, @11:23AM (#15190566) Homepage Journal
      Seems like it.

      I used to send all my email out of my own mailserver, out of my home firewall/router/"box-in-a-closet" machine.

      Recently -- like within the last six months or so, I've noticed an alarming number of domains that aren't receiving my emails. And no, I haven't been blackholed or otherwise put on anyone's shit list, nor am I running an open relay. The mailserver is perfectly well-behaved, standards compliant, and only relays from within my home LAN.

      I also don't mass-mail or do any other sort of sketchy activity, I just always liked having my own mailserver and never having to worry about when my ISPs (or Google's, or my web hosting providers') was going to flake out on me. But it's becoming nearly impractical to do. I'm never sure if an email that I sent out has actually gotten through, or if it's just been silently eaten by some spam filter somewhere.

      The worst offender that I've found so far is Comcast; I haven't been able to get any messages through at all to Comcast subscribers, and they don't provide back any sort of acknowledgment that a message has been blocked. Every time I send anything to them, it's firing a shot into the darkness.

      I hate spam as much as anybody else (probably more than some); I'm in favor of using some of those Federal "computer crimes" laws -- the ones that have harsher penalties for electronically violating a system than if you walked in and stole it in person -- against spammers. See what 20 years of pound-me-in-the-ass prison followed by another 10 or 15 of no-computer probation (and consequent unemployment) does for their attitude. Or there are the always popular vigilante death squads, I could find a warm place in my heart for them, too. Either of those would be preferable to the current patchwork system of blacklists, whitelists, greylists, RBLs, and unilateral policies on the part of ISPs that break up the nature of the network.

      Sending an email shouldn't be like tossing a message in a bottle into the ocean, but that's how it's getting to be with some ISPs.
      • If you are in an CIDR block that is listed in any of the big DULs, you're hosed.
      • by nuzak (959558) on Monday April 24 2006, @11:31AM (#15190630) Journal
        > I used to send all my email out of my own mailserver, out of my home firewall/router/"box-in-a-closet" machine.

        > The worst offender that I've found so far is Comcast;

        Sorry, but you're sending email from a residential IP with a rdns of something like "dsl-123-234-12-56.dyn.myisp.net" and you're calling comcast the offender?

        The days of running your own mail server on a residential account are over -- blame the thousands of zombie spammers on your /16 alone. Sorry that it's come to residential accounts being treated like second class citizens, but we gave this class of account YEARS to clean up its act, and it's only gotten worse.

        You can get mail hosting for like five bucks a month. It's the cost of spam. Deal with it, because we sure as hell are.

        Signed,
        the world's mail administrators

          • Not that simple. (Score:4, Insightful)

            by khasim (1285) <brandioch.conner@gmail.com> on Monday April 24 2006, @12:36PM (#15191095)
            Sorry, but the guy you replied to is doing nothing wrong and is going out of his way to make sure his server plays nice?
            It isn't about doing something "wrong".

            It's the fact that there is nothing to distinguish his email server from any of the hundreds (thousands?) of zombies on that same network.

            In cases such as this, the best solution is for the home user to over-comply. And that means learning about relaying and getting a relay account on a server that does not look like a zombie.
            And you accuse him (or her) of being an idiot and tell him it's all his fault anyway?
            This is not about anyone being an idiot.

            This is about making it as easy as possible for the other competent email admins to see that you are not a zombie.

            The more concessions you expect from all of them, the more problems you'll face.
            • by (negative video) (792072) <(me) (at) (teco-xaco.com)> on Monday April 24 2006, @01:39PM (#15191628)
              The more concessions you expect from all of them, the more problems you'll face.
              The complaint here was that certain ISPs are saying "Thank you, esteemed peer, for sending this valuable message which we will now deliver." when what they really mean is "Bugger off, spammy scum. Your message? Ha! We spit in the general direction of your message, which we will delete as soon as we finish wiping our ass with it." The behavior is singularly unhelpful.
      • by dekemoose (699264) on Monday April 24 2006, @11:36AM (#15190666)
        A large number of mail providers arbitrarily block any mail originating from net blocks identified as being used by "consumer" ISP's for dynamically assigned IP addresses. It's kind of lame, but also very effective at stopping large amounts of spam. Use your ISP's mail server as a smart host, or (if you don't trust the clue level of your ISP) one of the many SMTP relay services out there, I believe DynDns does one.
    • Hotmail's junk filters are valueless. Your only option is to block the sender's email, or slide the protection level, whatever that is, over some more.

      Just about any other service will let you filter on subject, header, body, filter out domain, etc.