ejd91717
Member
Andy, We use sendgrid at work. Setup is a little complex but with this VZW issue, I'm trying them out for TTD
Had bounces start coming in today, and after getting a bunch following the nightly tests this evening I called and spoke with Jake, a Verizon Technical Expert | WEHD Analyst. He was high level support enough to see their SMTP logs, and confirmed this will be an issue, with a recommendation to move to EMAG. He did confirm that there is a public safety fee waiver, but it must be done via a Verizon Business account.
As far as the new enforced limits: 10 recipients per message, 10 simultaneous SMTP sessions, and 10 messages per SMTP session.
He did start a ticket to try to whitelist the GMail account we're using to send, but said the ticket will likely be delayed to act on, and may be denied once it is acted on.
Jake fully recognized the "cool" factor of what we all are doing, ultimately this is an attempt by VZW to move businesses sending high volumes of mail through their system to subscribe (purchase) the EMAG service.
EMail from Jake to EMAG Rep:
""I have been working with a volunteer firefighter for a local agency, they have been using Vtext to send emergency service pages via SMTP protocol to the volunteer firefighters and EMS, today it appears that we blacklisted the originating email address due to the number of messages that were sent from the address, this is standard VZW procedure and business customer like this should be moved to EMAG. This is a unique situation and he would like you to reach out and see if this is possible. I have CC’d him to this email. Thanks""
So, not good news, but confimation that VZW is aware, it's intentional, and not going away without a change to our setups.
I am going to attempt to do EMAG if there's no fee, will keep y'all posted. Process won't even start until Monday.
Also, just thought of this, I have a number of departments on one instance of TTD for cell messaging, plus six other instances of TTD and one 5TD primarily posting to Twitter / Audioboom. Of those publishing, I have a few tones also sending to my cell. Even those only sending to 1 VZW (me), my email, and the BooMail mail, those are also bouncing. Only thought there, once the limit was exceeded, then all future are blocked by CloudFilter for some (unknown) period of time. All sent through GMail from TTD/5TD.
While looking through my departments Iamresponding account I noticed there is a .biz address for "priority" texting for Verizon. I'm assuming this address will not work because it doesn't come from a email address designated by IAR to Verizon. Am I correct in thinking this?
Had bounces start coming in today, and after getting a bunch following the nightly tests this evening I called and spoke with Jake, a Verizon Technical Expert | WEHD Analyst. He was high level support enough to see their SMTP logs, and confirmed this will be an issue, with a recommendation to move to EMAG. He did confirm that there is a public safety fee waiver, but it must be done via a Verizon Business account.
I send mine AMR and have upwards of twenty people on one department that up until the first sent out with no issues. I've reached out to Verizon on two levels and waiting on a phone call. I'm hoping I can have a FREE solution for everyone soon. I have many media contacts that might help boost the interest in coming to a solution as well.May I ask how you got ahold of Jake and if he gave you his last name? I'm going to reach out to some people tomorrow and if I can find Jake it may help. (I work for Verizon but am making no promises on any potential for success in figuring this out)
The limits you spoke of make little sense for me. My setup is watching two different tone sets and the only recipient is me alone. Today I've had 50/50 success sending myself the .mp3. Almost every other attempt is working, every other attempt is bouncing.
What really bugs me is despite all these blocks two separate spam texts have managed to get through.
There were all of six total events today so far on the system I monitor. I'm not getting anywhere near the limits you spoke of, so either they're being more aggressive than they realize or they're just not telling us the true logic behind the rejections.
I have every intention of telling them that I'm getting rejected for sending .mp3 files to myself from myself. The content of those .mp3's is irrelevant. They need to show a reason for why we can't send ourselves .mp3's for non-commercial purposes in my opinion.
Well. The first night of trying didn't go as well as I had imagined. One said you had to get the "EMS" enterprise messaging service (Which cost money. Blech) He sorta played dumb about the 10 message limit issue.I send mine AMR and have upwards of twenty people on one department that up until the first sent out with no issues. I've reached out to Verizon on two levels and waiting on a phone call. I'm hoping I can have a FREE solution for everyone soon. I have many media contacts that might help boost the interest in coming to a solution as well.
May I ask how you got ahold of Jake and if he gave you his last name? I'm going to reach out to some people tomorrow and if I can find Jake it may help. (I work for Verizon but am making no promises on any potential for success in figuring this out)
Like some else said, maybe if enough of us call and complain something might happen.
You wouldn't happen to have Secure Mode turn on in your Dlink would you? FTPLib is just plain, unencrypted FTP. Your use of WINSCP has me thinking SSL or FTPS. However it does seem to say that you logged in and the error is coming from the server itself.I'm not able to get the redundant FTP feature working with my Dlink DNS-320 NAS drive. Here is what TTD is saying when running in Debug mode.
File "ftplib.py", line 471, in storbinary
error_perm: 553 Users may not upload files
I have the FTP login linked to a specific share folder and it defaults to that folder when I log in via WINSCP.
You wouldn't happen to have Secure Mode turn on in your Dlink would you? FTPLib is just plain, unencrypted FTP. Your use of WINSCP has me thinking SSL or FTPS. However it does seem to say that you logged in and the error is coming from the server itself.
3 Things to check:
1) Can you put anything there normally using winscp?
2) Can you log in with another client (eg. Filezilla)?
3) Are there any restrictions for filenames/size?
I am not sure what Andy uses for file names but https://kb.globalscape.com/KnowledgebaseArticle10303.aspx seems to indicate that the server is refusing the file and the error above "553 Users may not upload files" makes me think it is a permissions issue. Try those and lets see what happens.
EDIT:
Quick google search on that exact error indicates it may be firmware related: FTP ISSUE : "553 Users may not upload files" Check your version and consider the firmware update that is listed. From that forumn (DNS-320 Rev A - Firmware v2.05 Build 10 Security Patch Comments & Observations) It appears that 2.05 B10 is the latest they have found. Consider checking into that.
baileyLAX
Do you have the Verizon Wireless Contact info. All of our Verizon pages are getting bounced back and I don't have a Verizon phone (we are all AT&T) so Tech support will not let me get anywhere.