Re: Spam Detector
stu357
Enthusiast - Level 3

So far, here is list of the domain names and thier IP addresses that have initiated spam mails. The information can be found in the email message header. I have enough expereince writing programs that decompose the syntax of a language to know that to write a program that automates picking out this data is rather straightforward. I do not know why it is beyond the technical capabilities of the Verzon technical staff unless there is a reason for not doing it. Possibly, ISPs are legally constrained from blocking emails. A user can but not an ISP. It would be professional to have a Verizon representative respond to that. I can also accept that it is in Verizon's financial interests not to do so. Again, a professional response would be welcomed.

Received from:                                                       ISP and Location

p74NQn6GSS.com ([unknown] [45.64.114.248])   India
 aceyeson.net ([unknown] [103.18.216.148])    India
broachat.net ([unknown] [103.18.217.137])
cytellin.net ([unknown] [103.18.218.101])
foyiller.net ([unknown] [103.18.219.57])
softlayer.com ([unknown] [119.81.45.57])    SoftLayer Dutch Holdings B.V., Singapore
oX2FqMmfM6.com ([unknown] [150.107.106.15])
batastea.net ([unknown] [161.48.68.35])   
76282141215592.com ([unknown] [162.251.1.18])    Virtual VM, Portland, OR
justomra.net ([unknown] [192.25.241.228])    Hewlett-Packard Company, Palo Alto, CA
bioinost.net ([unknown] [192.39.8.59])
bullanus.net ([unknown] [192.39.9.193])
culprico.net ([unknown] [192.72.33.96])
falcidge.net ([unknown] [192.74.210.144])
ensurvin.net ([unknown] [192.171.184.214])    JANET, UK
brionsor.net ([unknown] [192.197.144.120])     US
cariston.net ([unknown] [193.8.212.12])
centains.net ([unknown] [193.39.240.249])

dismarfa.net ([unknown] [194.39.77.230])
cytobiti.net ([unknown] [193.39.95.241])  
canethea.net ([unknown] [194.59.211.212])
cargangi.net ([unknown] [194.127.128.66])
cormerno.net ([unknown] [198.17.239.248])
gicasenh.net ([unknown] [198.89.84.216])  
indynell.net ([unknown] [198.252.183.159])
acryllin.net ([unknown] [199.68.14.201])  
agilover.net ([unknown] [199.68.15.176])
forstove.net ([unknown] [199.187.188.94])
garrefla.net ([unknown] [199.187.189.95])
grasture.net ([unknown] [199.187.190.86])
hayestim.net ([unknown] [199.187.191.239])
burnscan.net ([unknown] [199.201.187.212])
hapencyc.net ([unknown] [203.7.154.216])  
allendat.net ([unknown] [203.24.29.89])   
arlynetp.net ([unknown] [203.24.30.172])
banjaccu.net ([unknown] [203.24.31.132])
backsopt.net ([unknown] [203.24.28.33])
abolsati.net ([unknown] [203.30.187.161])
bursinet.net ([unknown] [203.57.85.148])
adflacil.net ([unknown] [205.142.12.104])
aeringth.net ([unknown] [205.142.13.107])
erimcave.net ([unknown] [205.236.181.175])   Montréal, Canada
EcVsXDiv5.com ([unknown] [212.174.35.65])  
DMuue0V7t.com ([unknown] [212.175.124.191])
ZFAWKRiu.com ([unknown] [212.175.61.68])    Turk Telekom, Turkey

I continue to ferret out this information whenever I receive spam email from one of my Verizon email accounts that is downloaded to my local email client...Thunderbird. Thunderbird readily identifies 99% of them. I do not have Thunderbird configured to delete emails on the Verizon server. I do that manually. Interestingly, most, 98%, of the spam emails are not listed in my emails received at the Verizon server. I don't understand why? An explanation from the Verizon technical staff would be appreciated.

0 Likes
Re: Spam Detector
tns2
Community Leader
Community Leader

@stu357 wrote:

So far, here is list of the domain names and thier IP addresses that have initiated spam mails. The information can be found in the email message header. I have enough expereince writing programs that decompose the syntax of a language to know that to write a program that automates picking out this data is rather straightforward. I do not know why it is beyond the technical capabilities of the Verzon technical staff unless there is a reason for not doing it. Possibly, ISPs are legally constrained from blocking emails. A user can but not an ISP. It would be professional to have a Verizon representative respond to that. I can also accept that it is in Verizon's financial interests not to do so. Again, a professional response would be welcomed.

Received from:                                                       ISP and Location

p74NQn6GSS.com ([unknown] [45.64.114.248])   India
 aceyeson.net ([unknown] [103.18.216.148])    India
...

ZFAWKRiu.com ([unknown] [212.175.61.68])    Turk Telekom, Turkey

I continue to ferret out this information whenever I receive spam email from one of my Verizon email accounts that is downloaded to my local email client...Thunderbird. Thunderbird readily identifies 99% of them. I do not have Thunderbird configured to delete emails on the Verizon server. I do that manually. Interestingly, most, 98%, of the spam emails are not listed in my emails received at the Verizon server. I don't understand why? An explanation from the Verizon technical staff would be appreciated.


I haven't researched yourlist but quite possible these are perfectly valid ISP's.  If so Verizon couldn't use the list to block all email from them.  All ISP have some abusers that spam the world.  And the smaller ones are bad at policing their users.

0 Likes
Re: Spam Detector
stu357
Enthusiast - Level 3

These are all vaid IP addresses.I have begun comparing the IP addresses from the "Received from;" and the "Originating IP". So far, I've found the same. Also, I have found that the combination of the domain names and the origination IP address are unique.

I am not asking Verizon to block these. I am looking to Verizon to tag them as spam and move them to my spam folder on their email server. Thunderbird does not bring down spam to my PC .I'll go to the mail server occassionally to check my spam folder to see if any emil was not spam.

Also, I've observed that the  domain name of the "Received: from" differs from that of the "Return-path:" address in the header, Maybe the Verizon technicians could tag these as spam when this is the case.

Since advertising revenue continues to drive much on the Internet, maybe ISPs should charge spam producers for each email received. Blocked if no pay. Let the advertisers support the Internet. Just an idea. Advertizing income is important for Google, FaceBook, Hulu and others. Why shouldn't ISPs gain from it too.

So many people are making advertizing money at the expense of the end-user. Hulu provides an option, Hulu+. Subscribe to Hulu+ and get less advertisements in their content. Even the United States Post Office receives benefits from processing spam snail mail. Why shouldn't the ISPs? With the ever increasing use of the Internet, bandwidth has to be increased. Who is going to pay for it? I vote for the advertisers and not the end-users. If Verison were to remove their spam detection and lower their cost to me I could live with that. Thunderbird would become my primary defense. In the open source software arena a solution will always emerge.

Keep in mind that the ISPs aren't spamming the world. It is companies that subscribe to the services offered by the ISP. Another consideration: ISPs provide differing subscription fees based upon the number of emails and recipients. The more emails ones sends by individual recipent, the more it costs. The Internet has a finite bandwidth. The more one pumps data into it, the more they should pay to use it. Now, one can assert that the government should be responsible for providing adequate bandwidth. Is it not just another commercial transportation highway? The cost for doing that, then, passes onto the tax payer. Intuitively somewhere along the way those companies that have the most to gain, namely profits, should be contributing more to supporting that highway. Trucking firms pay more in gasoline taxes.What is going to happen when trucks are electrified. There is always something. This argues against net neutrality. Someone has to pay for increasing the bandwidth. Who will it be?

0 Likes
Re: Spam Detector
tns2
Community Leader
Community Leader

Their are now such thing as Valid spam producers that can be charged.  If they are spamming the ISP's usually will cancel the users access.  Of course some minor ISP and particular some in foreign countries may feel no need to do anything. 

Verizon can't use the fact its from these ISP or that the return address is different (at least by itself) to decide to treat these as spam.  Lots of such cases are valid.  Many GOOD companies that people do business with (i.e. non-spamming companies) use a third party to send mail to their customers.

0 Likes
Re: Spam Detector
stu357
Enthusiast - Level 3

My impression is that there are companies who originate unsolicited email advertisements as a business venture. My current research with this forum topic reinforces this impression especially when I see the grouping of IP addresses. They are no different than companies who snail mail advertisements to my residence.They pay the USPS to deliver such mail. USPS does not offer any service to hold such mail.

Verizon offers spam detection as part of thier service. The user determines how spam is to be managed. It is not Verizon's responsibility to determine how spam is managed. Verizon's responsibility is to detect it and manage it as the user has indicated.From my expereince Verizon is not meeting its responsibility. I don't understand why. The technology to do so is relatively straightforward. Too many others are doing it. Thus, the technolgy does not appear to be proprietary.

Today I became aware that I'm receiving spam emails in which my email address is not included in the header. Why am I getting it?

My feeling is that if Verizon is not willing to provide a viable spam detection service then it should withdraw it completely.

In writing this I realized that Verizon does not display most spam when I go to my email account directly on the server. It does, though, send it to my Thunderbird client on my PC. I will have to check out the POP3 settings on the server. I'll get back to you.

Thank you for taking the time and effort to engage in this thread.

Re: "Many GOOD companies that people do business with (i.e. non-spamming companies) use a third party to send mail to their customers." Thunderbird seems to do well in discerning the difference. Why can't Verizon?

0 Likes
Re: Spam Detector
tns2
Community Leader
Community Leader

Rules are

Legal SPAM (and I think Verizon is not allowed to restrict such.  I actually see almost no spam of this kind as unsubscibe does work including, for many companies, a single unsubscribe for all of them.)

must have

  1. Unsubscribe compliance.  I.e include way to unsubscribe.  Not that I trust such from serious spammers.
  2. Content compliance.  Accurate from lines, Relative subject lines, and valid physical addresses.,  Label if adult contents.
  3. Sending behavior rules.  A bunch of these.

A bunch of exempts including companies you do business with, religeous, charities, political.

And yep Thunderbird and other clients often do better prevention.  BUt they aren't subject to the rules that could get Verizon in trouble if they blocked valid email.  And yes Verizon may be playing it to conservatively.

0 Likes
Re: Spam Detector
stu357
Enthusiast - Level 3

A couple of things first. I am not asking Verizon to block emails. I'm asking Verizon to flag them and let me subsequently confirm the flagging or to unflag them as not spam. In general, I do not "unsubscribe" from email lists from unknown sites. I do not believe it wise to complete/confirm the communication loop. I just trash the emails as I do snail mail without opening to see their content.

So the crux of the problem it is that Verizon does not want to proactively suggest emails as being spam, "valid" or not. I assume by "valid" you mean emails that are sent as advertisements by an established company. One can readily accept that it is in the best financial interest of Verizon not to do so.

OK, it is what it is. Verizon, should do at least the following:

1. Better manage their email users expectations. Inform their users that they do not proactively suggest that an email is spam but will honestly apply filtering and blocking rules established by the users.

2. Provide the users with more effective means for filtering and blocking emails. Namely, based upon my casual review of headers of spam emails:

(a) A selectable option to filter/block any mail that is sent without a date stamp. That is currently detectable for Verizon inserts into the header: "Date-warning: Date header was inserted by vms (Verizon).mailsrvcs.net".

(b) A selectable option to not receive any email that is not specifically sent to that email address. Namely, the header does not not contain the line:
"Original-recipient:....".

(c) Provide the means to filter/block emails sent from specific IP address in which wild card character can be used. For example, I have received spam from:

acryllin.net ([unknown] [199.68.14.201])  
agilover.net ([unknown] [199.68.15.176])
forstove.net ([unknown] [199.187.188.94])
garrefla.net ([unknown] [199.187.189.95])
grasture.net ([unknown] [199.187.190.86])
hayestim.net ([unknown] [199.187.191.239])
burnscan.net ([unknown] [199.201.187.212])
contomen.net ([unknown] [199.233.148.139])
baryersc.net ([unknown] [199.246.32.151])
blueboxa.net ([unknown] [199.246.33.104])

I would like the ability to tag as spam any emails received from 199.187.*.* or maybe even 199.*.*.*.

Note that in these examples, the domain names are meaningless to be used to qualify an email. Also, a full IP address is meaningless. It is only necessary to turn off one's modem at the end of the work day and turn it back on the next to get a different IP address.

Since these advertising companies can readily send out emails for different clients, to ask an email user to identify each individual client email is placing an obstacle in the way of the user. Here is where the "rubber meets the road". Verizon has a choice. Either make it easy for the users to tag emails as spam or not. The domain name in the "Return-path" line in the header or "From" address in the email is as meaningless as the domain name in the "Received" line of the header.

3. Provide the user to export and import the created filtering/blocking rules. In my case, I have several subordinate email address. I would like the means to have the same filtering/blocking rules apply to all of them.

Given your status within the Verizon forum activity, I suspect that you have contact with key Verizon decision makers. I would appreciate it if you would forward this suggestion for their consideration. Keep in mind that my objective for beginning this thread  was to seek ways to improve the "Spam Detection" service provided in Verizon email.

P.S. It as been a long time since I've articulated program specifications. There might be gaps in my thinking.

0 Likes
Re: Spam Detector
stu357
Enthusiast - Level 3

In an earlier entry, you suggested that the IP address in the "Receive;"and "X-Originating:" line might not the actual ones. Then, what information is in the header that enables one to identify it as spam?

Is it feasible to expect Verizon to flag potential spam emails without incurring any legal or financial problems? Verizon has available considerable data...every header that it processes...in which to mine for meaningful information. I'm not suggesting that it mines the contents of emails like other email providers appear to do.

Thanks.

0 Likes
Re: Spam Detector
stu357
Enthusiast - Level 3

7/22/14

I don't know if it was something that I did or that Verizon did but for the past two days, spam detection on Verizon email is as I would expect /want it to be. Spam emails are being directed to my SpamDetector folder and they are not being downloaded onto my PC client.

On Sunday I cleared all the entries in my email settings for filtering and blocking. Then I added the following as filters:

If Subject Contains <my email address@verizon.net> move to SpamDetector
If To does not contain <my email address@verizon.net> delete

If From Contains 5.*.*.* move to SpamDetector
If From Contains 23.*.*.* move to SpamDetector
If From Contains 31.*.*.* move to SpamDetector
If From Contains 37.*.*.* move to SpamDetector
If From Contains 45.*.*.* move to SpamDetector
If From Contains 77.*.*.* move to SpamDetector
If From Contains 91.*.*.* move to SpamDetector
If From Contains 92.*.*.* move to SpamDetector
If From Contains 93.*.*.* move to SpamDetector
If From Contains 103.*.*.* move to SpamDetector
If From Contains 107.*.*.* move to SpamDetector
If From Contains 117.*.*.* move to SpamDetector
If From Contains 119.*.*.* move to SpamDetector
If From Contains 144.*.*.* move to SpamDetector
If From Contains 149.*.*.* move to SpamDetector
If From Contains 150.*.*.* move to SpamDetector
If From Contains 161.*.*.* move to SpamDetector
If From Contains 162.*.*.* move to SpamDetector
If From Contains 192.*.*.* move to SpamDetector
If From Contains 193.*.*.* move to SpamDetector
If From Contains 194.*.*.* move to SpamDetector
If From Contains 195.*.*.* move to SpamDetector
If From Contains 198.*.*.* move to SpamDetector
If From Contains 199.*.*.* move to SpamDetector
If From Contains 202.*.*.* move to SpamDetector
If From Contains 203.*.*.* move to SpamDetector
If From Contains 205.*.*.* move to SpamDetector
If From Contains 206.*.*.* move to SpamDetector
If From Contains 212.*.*.* move to SpamDetector

I'm not sure if the wild-card IP addresses are being applied. I periodically scan the contents of the SpamDectector folder to insure that no valid email is flagged as spam.

Has anyone else experienced improvements in Verizon's spam detection?

0 Likes
Re: Spam Detector
billfly
Newbie

I have the opposite problem with Verizon Spam Detector.  I forward a single email to a single person or reply to am email and the Spam Detector rejects it as SPAM.  I am so sick and tired of my email to one person being returned to me as undeliverable.  I was replying to a job interview email, and had it rejected back.  I think Verizon should not treat a single email to a single person from me as Spam.  It is really irritating and a violation of my right of free speech.

0 Likes