Residential Svc - Increase e-mail alloed to > 100 users, - Cant send e-mails to neighbora

[steve_l1]

I live in a residential neighborhood with 74 homes and a Home Owner's association.  Each home will often have 2-4 or more e-mail addresses, one personal and one business for each spouse and possibly more for kids.  If you do the math, you may end up wiht 225-300 e-mail addresses on the HOA distribution.

One challenge whe have and response, regarding Vewrizon FIOS, to everyone in the neighborhood is that, if you get Verizon FIOS and verizon e-mail, you may not get e-mail to the neighbors, including crime watch notices, HOA activities, etc. due to the Verizon limit on Residential service to 100 e-mail addresses before violating the Verizon security policy.  This week, many people did not get notifications of the bobcats in the neighborhood.  Other weeks it has been Coyotes, thefts from cars, etc.

This is not a technical issue with Verizon.  You can get a higher limit, Verizon requires you to pay more and subscribe to business service.  But for residential users, it seems unfair to ahve to subscribe to a business service to be able to talk to your neighbors and share safety information.

Please consider a higher limit or other work around on the number of e-mail addresses allowed by Verizon e-mail.  Verizon is a public utility with the local franchise in Plano.  The alternative wold be to take this to the city as a safety and public service issues with the local Verizon FIOS service to be considered in the renewal process.

For reference, here were all of the e-mail addresses that did not get the respons and warning of the Bobcats in the neighborhood.  Hopefully no small pets were lost to the predators.

************** Verison Security Violation Pasted Below ****************************

Your message did not reach some or all of the intended recipients.

      Subject:    RE: Bobcat pic 4

      Sent: 9/8/2013 7:00 PM

The following recipient(s) cannot be reached:

     {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      '{edited for privacy}on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      '{edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

     {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      '{edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      '{edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      '{edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}' on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

     {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}' on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

     {edited for privacy}' on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

     {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy}' on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, reached maximum number of recipients for one session (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

     {edited for privacy}' on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

      {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

     {edited for privacy} on 9/8/2013 7:06 PM

            571 sorry, you are violating our security policies (#5.7.1 - chkuser)

[armond_in_nj1]

---

@steve_l wrote:

I live in a residential neighborhood with 74 homes and a Home Owner's association ... you may end up wiht 225-300 e-mail addresses on the HOA distribution. ... the Verizon limit on Residential service to 100 e-mail addresses before violating the Verizon security policy ... Please consider a higher limit or other work around ...

---

Just establish multiple mail lists.  In my HOA we use a separate list for each street (there are only three, and the total number of homes is roughly 150).  This procedure also makes editing the lists simpler, since one already knows the street address of the resident to be edited.

Another suggestion:  Whatever you decide, don't rely on webmail, Verizon or otherwise.  Use a real mail client and get the features you need in a reliable package.