email error message

Netmouse
Enthusiast - Level 3

Why did this start happening?  I got 2 emails today that have a similar error message.  .I received other email without this error.

Processing errors occurred during delivery:

  Recipient address  (it has my verizon email address correctly)

  Reason: Error in sieve filter: Insufficient arguments in call to function: header around input line 5 [(h eader:c ontains[ ^"X-Verizon-Spam"][""]

Delivery processing continued in spite of these errors.

14 Replies
heidivandy
Enthusiast - Level 1

I just got three of the same emails. These relate to messages that were comin in but it says they were messages I sent..

"

This report relates to a message you sent with the following header fields:

Message-id:

   <1793-160-S8ST9Q-JFIS9-17C2V-2XTJ6W-TZIM2G-H-M2-20140925-f28528ab45c80c593@e-dialog.com>

Date: Thu, 25 Sep 2014 06:21:30 -0400

From: "DICK'S Sporting Goods" <{edited for privacy}>

Very strange.

h2ogram
Enthusiast - Level 2

you are not the only one. Exact same situation But, according to net and what usually causes this sieve filter error I have not done anything on my end to cause it. Assume must be on verizon end but woud be nice to get a confirmaton from them. Hoping my email has not been compromised.

Tracysplace
Enthusiast - Level 1

Getting dozens of them, what is the deal?

Timhr950
Enthusiast - Level 1

Same problem here. Just appeared this morning, but the message does get through.

oreogizmo
Enthusiast - Level 3

Same thing happened to me.  It was mostly on my main email account, but there was one on my sub account.  This all happened around 3:15-3:30am EDT. 

cinderbloke1
Enthusiast - Level 2

Same here, I got one in each of three of my inboxes from <postmaster@verizon.net> between 1:51am and 3:33am, and all the errors related to an error in the "sieve filter", but with two different error descriptions.

The following 2 messages came in with exactly the same timestamps as the email to which they referenced ...

"Processing errors occurred during delivery:

  Recipient address: *MyValidEmailAddress*@verizon.net
  Reason: Error in sieve filter: Unknown function/variable found: value around input line 6 [mtest:v alue  "ge" :^comparator "i;ascii-]

Delivery processing continued in spite of these errors."

"Processing errors occurred during delivery:

  Recipient address: *MyValidEmailAddress*@verizon.net
  Reason: Error in sieve filter: Insufficient arguments in call to function: header around input line 5 [(h eader:c ontains[ ^"X-Verizon-Spam"][""]

Delivery processing continued in spite of these errors."

This one came in with a timestamp 4h28s later than the email to which it referenced ...

"Processing errors occurred during delivery:

  Recipient address: *MyValidEmailAddress*@verizon.net
  Reason: Error in sieve filter: Insufficient arguments in call to function: header around input line 5 [(h eader:c ontains[ ^"X-Verizon-Spam"][""]

Delivery processing continued in spite of these errors."

Each message referenced emails from known/verified senders. Would like to hear from Verizon what the cause was.

Karenrad
Enthusiast - Level 1

Same here - I got 5-6 of them. Just changed my password. Why isn't Verizon responding??

h2ogram
Enthusiast - Level 2

so..did you find that changing your password helped? You are no longer getting the errors? My errors were coming from places like walgreens email and koihls email etc. But one came from a private poersonal email as well.

somegirl
Champion - Level 2

@Karenrad wrote:

Same here - I got 5-6 of them. Just changed my password. Why isn't Verizon responding??


...because This is a peer-to-peer support forum. If you want to get a response from Verizon, you should contact them directly via one of the options on their Contact Us page.

cinderbloke1
Enthusiast - Level 2

@Karenrad wrote:

Same here - I got 5-6 of them. Just changed my password. Why isn't Verizon responding??


I contacted VZ CS this morning, described the issue, and pointed them to this thread. A supervisor called me back to suggest that I change my account password(s). After I spent more time detailing the content of the emails sent (ostensibly) by their system, he said he would escalate the issue and committed to getting back to me if/when they determine the cause of the issue. If he does, I plan to post their response here.

It's too bad VZ does not have an address to which we could forward suspect messages (as does VZW for spam text messages - which, BTW, seems to work to remarkable effect in curbing it) so they could dissect the full headers and content themselves.

h2ogram
Enthusiast - Level 2

Thanks for letting us know. I thiink what bugs me the most is they always say "change your password". It is like DISH when they ALWAYS say - turn your dvr off and on when it is obvisouly something on their side. I used to do system test on datacom software and hardware This seems like such an obvious Verizon problem to me. Esp since I have not done anything to my password and the problem seems to have gone away now that you have spoken with them.They should have had error reports kicking out warnings all over the place.

cinderbloke1
Enthusiast - Level 2

@h2ogram wrote:

Thanks for letting us know. I thiink what bugs me the most is they always say "change your password". It is like DISH when they ALWAYS say - turn your dvr off and on when it is obvisouly something on their side. I used to do system test on datacom software and hardware This seems like such an obvious Verizon problem to me. Esp since I have not done anything to my password and the problem seems to have gone away now that you have spoken with them.They should have had error reports kicking out warnings all over the place.


In a previous life I did quite a bit of "involuntary" system/network troubleshooting, and was quite proficient in crashing buggy software (which was, pretty much, all there was). It was amazing how many times it would get silently fixed, but the response would come back from the developers as ... "problem came clear while testing - that is all". Smiley Wink

h2ogram
Enthusiast - Level 2

yeah or they would say it was a documentation error.  or a no op error! I am so ancient I used t work the mainframes. Thanks for the walk donw memory lane.

cinderbloke1
Enthusiast - Level 2

Just as a quick follow up ... the VZ CS Supervisor did not call me back, as he promised he would, to let me know what the source of this error was. Since I've seen no further occurrences since, I suspect that it originated in their email system and has been corrected.

0 Likes
Reply