email to sms gateway issues

dieselmachine2

    I run a website online that deals with labor dispatch, and one thing we offer is SMS notifications when new jobs are available. All numbers we send to must be confirmed by the end user before we will allow notifications to be sent to them, so there is zero chance that someone is receiving 'spam' messages they didn't want to receive. Until recently (about a week ago maybe), things were working fine for 8 years. For those 8 years, the setup was:

     

    - my domain was in the envelope sender

    - the dispatchers info was in the From: header

    - my domain has Reverse PTR, SPF, and DKIM set up

     

    Those messages are now being rejected as 'spoofs', presumably because the 'From' header doesn't line up with the envelope sender. While it may be a bit overzealous to trash those, especially given the SPF verification passes, I have been trying to work around the issue. In the meantime, I am using a 'noreply' for the from address, so the messages are getting through, but no one can reply to them, and my users are pissed off (as they should be).

     

    So where I'm at now, I have been trying to implement SRS in order to deal with your heavy-handed, ill-thought-out approach to dealing with SPAM. So the dispatcher can send the message, the envelope sender continues to be based at my domain, and the From header is rewritten via SRS to appear to be at my domain, while containing enough info for me to forward the message back to them when the reply comes in.

     

    Step 1: dispatcher sends a message. This works

    Step 2: user replies. Tmo sends it to my server, and I am able to reverse the SRS address and initiate the forward. This works.

    Step 3: I then forward the message UNMODIFIED to the destination, using my server's envelope sender (for SPF checks). Altering the From: header from the original sender is ABSOLUTELY NOT AN OPTION because it would break any DKIM signature for any messages I am forwarding. So this part breaks, because Tmo, for some reason, can't figure out what to do with this message.

     

    This is an example of the message send from tmobile to my server:

     

    S: 220 mail.example.com ESMTP Postfix (Ubuntu)

    C: EHLO da3p-tmo-mm3-sfw001.syniverse.com

    S: 250 mail.example.com\r\n

        250-PIPELINING\r\n

        250-SIZE 10240000\r\n

        250-VRFY\r\n

        250-ETRN\r\n

        250-ENHANCEDSTATUSCODES\r\n

        250-8BITMIME\r\n

        250-DSN\r\n

    C:  MAIL FROM:<btv1==8190f953ef1==1PHONENUMBER@tmomail.net> SIZE=518\r\n

        RCPT TO:<SRS0=Kb27=NM=tmomail.net=PHONENUMBER@example.com> ORCPT=rfc822;SRS0+3DKb27+3DNM+3Dtmomail.net+3DPHONENUMBER@example.com\r\n

        DATA\r\n

    S:  250 2.1.0 Ok\r\n

        250 2.1.5 Ok\r\n

        354 End data with <CR><LF>.<CR><LF>\r\n

    C:  Received: from tmobile.net ([10.164.3.161]) by da3p-tmo-mm3-sfw001.

            syniverse.com with ESMTP id 0qe6yfmnCwSHUuup for <SRS0=Kb27=NM=tmomail.net=PHONENUMBER@example.com>; Tue, 12 Jan 2016 10:13:31 +0000 (GMT)

        To: SRS0=Kb27=NM=tmomail.net=PHONENUMBER@example.com

        From: 1PHONENUMBER@tmomail.net

        Content-Type: text/plain

        Date: Tue, 12 Jan 2016 10:13:31 GMT

        Subject: RE:testing

        Message-ID: 20160012101331845490@mavenir.com

        Sender: 1PHONENUMBER@tmomail.net

        X-Virus-Scanned: by bsmtpd at syniverse.com

     

        Jfkfjjt\r\n

        .\r\n

        QUIT\r\n

    S:  250 2.0.0 Ok: queued as DBD7418110

        221 2.0.0 Bye

     

    And this is an example of the bounced forwarding attempt:

     

    S:  220 Syniverse ESMTP Service CHI01

    C:  EHLO mail.example.com

    S:  250 ch3p-tmo-mm3-sfw001.syniverse.com Hello www.example.com [xx.xx.xxx.90], pleased to meet you\r\n

        250 SIZE 3145728\r\n

        250 PIPELINING\r\n

        250 8BITMIME\r\n

        250 HELP\r\n

    C:  MAIL FROM:<SRS0=19rQ=NM=tmomail.net=btv1==8190f953ef1==1PHONENUMBER@example.com> SIZE=808\r\n

        RCPT TO:<PHONENUMBER@tmomail.net>\r\n

        DATA\r\n

    S:  250 Sender <SRS0=19rQ=NM=tmomail.net=btv1==8190f953ef1==1PHONENUMBER@example.com> OK\r\n

    S:  250 Recipient <PHONENUMBER@tmomail.net> OK\r\n

    S:  354 Start mail input; end with <CRLF>.<CRLF>\r\n

    C:  Received: from da3p-tmo-mm3-sfw001.syniverse.com (dal-tmo-mm3.syniverse.

            com [173.209.216.234])

            by mail.example.com (Postfix) with ESMTP id DBD7418110

            for <SRS0=Kb27=NM=tmomail.net=PHONENUMBER@example.com>; Tue, 12 Jan 2016 05:13:31 -0500 (EST)

        X-DKIM: Sendmail DKIM Filter v2.8.1 mail.example.com DBD7418110

        Received: from tmobile.net ([10.164.3.161]) by da3p-tmo-mm3-sfw001.

            syniverse.com with ESMTP id 0qe6yfmnCwSHUuup for <SRS0=Kb27=NM=tmomail.net=PHONENUMBER@example.com>; Tue, 12 Jan 2016 10:13:31 +0000 (GMT)

        To: SRS0=Kb27=NM=tmomail.net=PHONENUMBER@example.com

        From: 1PHONENUMBER@tmomail.net

        Content-Type: text/plain

        Date: Tue, 12 Jan 2016 10:13:31 GMT

        Subject: RE:testing

        Message-ID: 20160012101331845490@mavenir.com

        Sender: 1PHONENUMBER@tmomail.net

        X-Virus-Scanned: by bsmtpd at syniverse.com

     

        Jfkfjjt\r\n

        .\r\n

        QUIT\r\n

    S:  550 rejecting spoofed message

    S:  221 ch3p-tmo-mm3-sfw001.syniverse.com Goodbye www.example.com, closing

            connection\r\n

     

    What do I need to do to get around your ill-conceived rules? Why don't you just implement DKIM? It's obvious that I haven't manipulated any of the headers, I've left everything intact, and my SPF checks out, so if that's not enough for you, why not implement DKIM so you can VALIDATE YOUR OWN MESSAGES? This is absolutely ridiculous! You gave me the message-ID, i gave it right back, you can VERIFY that it's a forward, not a spoof! Do you not realize how asinine this approach is?

     

    How do I work around this engineering catastrophe? (The answer is not 'rewrite the from header on a forward', because that would screw over the responsible adults who actually implemented DKIM).

     

    I'm sorry if I sound upset here, but it's because I AM. I've done every single thing by the books to give anyone the ability to validate the content coming out of my server, and your actions have directly impacted my business. This server has been sending these messages for 8 years, and it has a great email reputation, but you've somehow implemented a disastrous policy without really knowing what you were doing.

     

    Please tell me how to work with this new terrible system so my users can message eachother and reply to the messages.

      All replies

      • tmo_lauren

        Re: email to sms gateway issues

        Greetings!

         

        Looks like our good friend Ryan replied to your comment over here email to tmomail.net rejected for banned content

         

        I'd suggest following his advice, and apologies for any confusion on how to file the ticket!

         

        -Lauren

        • dieselmachine2

          Re: email to sms gateway issues

          It's NOT OKAY to require users to use twitter or facebook to submit tickets. Some of us don't want to use those services. Standard email, or a web-based form on the site, should have been top priority, with inconvenient options (those that require the user to sign up with a service he doesn't want) should have gone on the backburner.

           

          If I have to post here every 36 hours to prevent some sneaky employee from marking it "answered", i'll do it. I've seen how the employees here behave, and it's shameful. This whole company seems to have a serious problem with basic human decency. This issue is not resolved, and most definitely not answered.

            • dieselmachine2

              Re: email to sms gateway issues

              This thread is still not answered ( I will post once a day to make sure an employee doesn't mark it 'answered due to 36 hours of inactivity' in an attempt to make the problem disappear).

               

              The ticket number is 14541030. We'll see if they ever get back to me.

                • e2k

                  Re: email to sms gateway issues

                  Post every day will often delay a response. The community managers tend to look at posts without replies (for a day or 2) before those with replies.

                   

                  As for T-Force using social media, you do not have to use the social media channel for anything else. You can just choose a username, contact T-Force, and never use it again. No one (other than T-Mobile) will be able to associate your real name or email address with the social media account.

                    • dieselmachine2

                      Re: email to sms gateway issues

                      I have to post everyday, because as evidence has shown, the reps are lurking, waiting for that 36 hour period to expire so they can shut down a ticket and never acknowledge it again. It's happened with nearly every ticket I've seen that has been related to the email->sms gateway, and I can't chance that happening here.

                        • tmo_lauren

                          Re: email to sms gateway issues

                          Hey there!

                           

                          I had replied on the same thread I linked to above that Ryan had also replied on.

                           

                          We haven't done the 36 hour close in some time since we have restructured, so that message hasn't been used in several months and won't be making an appearance here, even if you take a few days off from posting. Promise!

                           

                          So feel free to pop in as you see fit, but you don't need to post every day for us not to close it. We'll keep it open as needed.

                            • e2k

                              Re: email to sms gateway issues

                              tmo_lauren wrote:

                               

                              We haven't done the 36 hour close in some time since we have restructured, so that message hasn't been used in several months and won't be making an appearance here, even if you take a few days off from posting. Promise!

                               

                              Thanks for updating us on the new protocol

                                • tmo_lauren

                                  Re: email to sms gateway issues

                                  That's why you mostly just see MC, myself, Ryan, and a little bit of Phill out here. T-Force sticks to FB and Twitter for the most part and are the ones who have account access.

                                   

                                  You'll notice I got the spiffy new Community Manager badge rather than T-Force badge now ;D

                                   

                                  Thanks as always for being so helpful e2k

                                    • tmo_lauren

                                      Re: email to sms gateway issues

                                      Just checking in to see if we have any new news!

                                       

                                      -Lauren

                                        • dieselmachine2

                                          Re: email to sms gateway issues

                                          No, the engineers closed 2 consecutive tickets on me, the first because it "wasn't reproducible", and the second because they determined it was a "device issue", despite it being server-to-server communication (which I'm sure they were aware of).

                                           

                                          After relenting and joining twitter so I could finally submit my packet capture log that no one wanted to take, I had someone open a third ticket after verifying that the issue wasn't only my device, but also my girlfriend's device, as well as those of every single t-mobile user who uses my dispatch system. I was told via twitter that I'd hear back "by tuesday". That was 10 days ago, so 2 consecutive tuesdays have happened with no response (to be fair, this one isn't quite over yet, so anything could happen, LOL).

                                           

                                          I also heard from a source at T-mobile that the issue is occurring upstream at synuniverse, and the issue was escalated, so what will become of that, no one knows. But no, the issue is most definitely still not resolved.

                                            • dieselmachine2

                                              Re: email to sms gateway issues

                                              So the 4 tickets they've closed on me so far without fixing the issue are 14541030, 10867119, 10862640, and 10826251. I even sent them a 4 step process on how to reproduce the issue, but it looks like engineering has no oversight whatsoever, and can just trash tickets without ever bothering to test the issue.

                                               

                                              This is absolutely infuriating. Now I'm on twitter with someone who says engineering is refusing to help unless I test my SIM in another device, despite the fact that the issue doesn't even involve my phone.

                                               

                                              I can't believe they can get away with this. Someone needs to be fired for how they're handling this.

                                               

                                              If the problem is communication between network servers, and the engineers are demanding changes to device configurations, there is something horribly wrong. I can only assume at this point that they're laughing the entire time as they waste my f'ing time, before throwing out yet another ticket. I've seen no indication whatsoever that they even bother to perform the reproducible test steps.

                                                • dieselmachine2

                                                  Re: email to sms gateway issues

                                                  New ticket is 11001092, bet they close this one without testing as well.

                                                   

                                                  At least this time they can't claim my SIM card has anything to do with it.

                                                   

                                                  God I hate T-mobile engineers.

                                                    • e2k

                                                      Re: email to sms gateway issues

                                                      I suggest you contact T-Mobile corporate and start from the top. This is called Executive Customer Service.

                                                       

                                                      I won't post details here, but if you just do a little Googling, you'll find the appropriate contact information.

                                                        • tmo_lauren

                                                          Re: email to sms gateway issues

                                                          I actually think we may be making some headway on my side!

                                                           

                                                          Hang tight for me, I think we are getting closer to a resolution and I will be popping back in here soon. I may not get a reply before end of day today and it's the weekend coming up,but if you don't hear from me today, it should be next week!

                                                           

                                                          -Lauren

                                                        • srickar

                                                          Re: email to sms gateway issues

                                                          Hi Diesel.....I made some modifications to the setup and not seeing any further 550 rejections. It was not for SPF violation either. There were also prior successful messages routing through.  Please be patient, these systems are dynamically trying to combat false negative and false positive spam threats and no employee is trying to deny legitimate traffic. A global expression could override "safe" traffic based on traffic trends.

                                                           

                                                          Please review and maintain SMTP setup with RFC822 header standards. With that said, can you please PM me with your concerns and I will try to address them.

                                                            • dieselmachine2

                                                              Re: email to sms gateway issues

                                                              It's been a few week now, and everything seems to be going smoothly. I haven't had a single complaint from my Tmobile users, so thank you a million times over for fixing this.

                                                               

                                                              Also, when you say 'PM me with concerns', can you explain to me how to PM someone here? I actually tried to find that option a looooong time ago when I found another post you made on this forum (email to tmomail.net rejected for banned content) that indicated you might be the 'go to' guy for problems of this nature, but I was unable to find any way to send a PM, so I resorted to posting in the same thread.

                                                               

                                                              Also, while we're on the subject of header standards, all of tmomail.net's outbound messages have non-compliant message IDs (lacking the angle brackets), so google is rewriting them. The result looks like this when i message my gmail from my phone:

                                                               

                                                              Message-ID: <56c667ec.86c70d0a.d4e39.3812SMTPIN_ADDED_BROKEN@mx.google.com>

                                                              X-Google-Original-Message-ID: 20160119005507112154@mavenir.com

                                                               

                                                              I'm not sure who this mavenir.com entity is, but it looks like they might need to read some RFCs.

                                                                • tmo_lauren

                                                                  Re: email to sms gateway issues

                                                                  Greetings!

                                                                   

                                                                  At the top of the page next to your name there is a little magenta box with a message number in and that takes you to your inbox! Alternately you can use the link here https://support.t-mobile.com/inbox to get to inbox. You have to respond to an existing message, or both members must follow each other otherwise messaging will not be enabled.

                                                                    • ronwave

                                                                      Re: email to sms gateway issues

                                                                      I run a animal clinic where clients make online appointments, besides the email I receive I need to receive SMS notifications. I cannot be in the computer all the time. So I found useful receive SMS notifications. The email I use is 1PHONENUMBER@tmomail.net but this error keep coming. How can I fix this issue? This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: 1PHONENUMBER@tmomail.net: SMTP error from remote server for TEXT command, host: d79033b.ess.barracudanetworks.com (64.235.154.105) reason: 550 permanent failure for one or more recipients (1PHONENUMBER@tmomail.net:b locked)

                                                                        • thundertiger

                                                                          Re: email to sms gateway issues

                                                                          Just FYI it is always best to start a new thread instead of replying to an old thread.

                                                                           

                                                                          But if I understand you correctly it sounds like you are adding a 1 to your 10 digit phone number? 1(555)(555-5555)@tmomail.net?  

                                                                           

                                                                          If so, then you only want to use your 10 digit phone number when using the tmomail.net.   (areacode)(phonenumber)@tmomail.net

                                                                           

                                                                          No spaces, dashes, or parenthesis of course.

                                                                           

                                                                          Kelly

                                                                          1 of 1 people found this helpful
                                            • Also have this problem, stop working recently.

                                              • srickar

                                                Re: email to sms gateway issues

                                                ronwave thundertiger @tmo_marissa

                                                 

                                                Anyone still need assistance? Sorry, I don't always have a chance to check threads on here.

                                                 

                                                Adding 1 to email address is not necessary. There are server rules that strip off pretreatment digits from the full 10 digit number. Likewise, with dashes and other unnecessary characters. If you are receiving 550 bounceback, please send me a follow request and likewise I can do the same. This will allow you to send me a PM with your private details on the message blocks.

                                                 

                                                Thanks,

                                                Sean

                                                  • executor-brandon

                                                    Re: email to sms gateway issues

                                                    Delivery Host: d79033b.ess.barracudanetworks.com

                                                    Delivery IP: 64.235.153.2

                                                    Size: 829 bytes

                                                    Result: ECDHE-RSA-AES256-GCM-SHA384:256 CV=yes: SMTP error from remote mail server after end of data: 550 permanent failure for one or more recipients

                                                    Same error just happened to a texting service I manage today to 1250 T-Mobile subscribers.

                                                     

                                                    The big issue here is that regular messages are accepted but these "blocks" are blocking an UNSUBCRIBE link REQUESTED by the T-Mobile customer in which the FCC will have a field day with.

                                                     

                                                    We reported T-Mobile's actions to the FCC online and have prepared a certified letter via USPS to have this issue corrected immediately.

                                                     

                                                    It's one thing to block all messages from a texting service but it's a big NO NO to ONLY block messages containing UNSUBSCRIBE links!

                                                     

                                                    We have notified all 1250 of our T-Mobile subscribers to call 611 and also report their issue to the FCC and seems to be going well.

                                                     

                                                    Will keep everyone updated on our progress.

                                                     

                                                    *edited to remove personal info - Marissa

                                                      • srickar

                                                        Re: email to sms gateway issues

                                                        executor-brandon,

                                                         

                                                        I have read your request and have reviewed the blocks. Right away, I recommend editing your subscriber numbers from this message. Based on the sensitive content and mutual subscriber privacy, it may get cached on search engines.

                                                         

                                                        It appears the domain in question is sending bulk solicitation material "HAPPY HOUR TODAY...", which was caught by automation spam filters. There are certain spam characteristics on these messages such as repetitive content and using ALL CAPS which is a flag to any 3rd party spam engine. To reiterate, T-Mobile is not specifically blocking the sending domain - it's due to the message content, volume, DNSBL, and formatting.

                                                         

                                                        • I reviewed automated unsubscribe blocks, and those messages are indeed delivering with a neutral score.
                                                          • I reviewed a variety of bulk recipient messages and did not locate any unsubscribe messages being blocked.
                                                            • I disagree with the provided header example. The snippet provided above is for a block relating to inbound "HAPPY HOUR TODAY...", with many recipients, which should not be confused with a single subscriber unsubscribe email attempt. A single unsubscribe would not be sent to more than 1 requester.
                                                            • As shown below, 3 individual unsubscribe requests with blank subject delivered with no scoring attempt.



                                                        • Emails are addressed to a large "undisclosed-recipients" list in each payload which is another bulk spam characteristic.
                                                        • Sending large volumetric sales related payload and suspicious message formatting, i.e. all caps.
                                                        • I see where messages were passing on 1/17 and then a gradual aggregate spam score was received approximately 1/21.
                                                        • Aggregate spam scoring is based on dynamic scoring pertaining to IP source, volumetric limits, and dynamic ISP DNSBL reputation related blacklists.
                                                        • T-Mobile and our global spam vendor reserve the right to dynamically protect subscriber base from messaging campaigns that meet or exceed any or all of these items listed above.

                                                         

                                                        • 3rd party email messages from external SMTP sources are subject to dynamic email filtering and should not be confused with SMS subscription based shortcode content. SMTP email messages are subjected to filtering because of the nature of external SMTP cloud sources.
                                                        • P2P email gateways are for (Person to Person) contact and not for one-directional automation volumetric content.
                                                        • Commercial trafficking is sanctioned through A2P short code, and not through long code (10-digit numbers).
                                                          • Sending bulk content is considered enterprise class messaging (A2P - Application 2 Person), that should actually be sent through shortcode and not through consumer based email gateways.
                                                            • Shortcode providers are prepared to maintain subscription requests based on STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT commands that source SMTP email relays do not track or recognize for FCC CAN-SPAM compliance.
                                                            • Sending bulk email to long 10 digit wireless recipients are not part of CTIA FCC SMS compliance. Only shortcode is valid in stop/start related scenarios.
                                                        • Third-party services can send bulk SMS subscription messages, but such vendors are unaffiliated with T-Mobile and we can't make recommendations. Examples include: Openmarket, 3Ci, mGage, Twilio, SAP, iConectiv, Vibes Media, Syniverse, CLX.

                                                         

                                                        Please refer to FCC and CTIA standards below starting at section 4.1 regarding the use of subscription based services through shortcode. FCC based email domains have separate but distinct FCC restrictions regarding solicitation to CMRS (Commercial Mobile Radio Service) domains. To recap, email does not qualify for wireless A2P subscription guidelines. Rather, please work on migrating your bulk traffic to legitimate shortcode provider. 

                                                         

                                                        Domain Name Downloads | Federal Communications Commission

                                                        This is a list of Domain Names to which marketers may not send unsolicited e-mail because the messages go to wireless devices, including cell phones and pagers. These names were provided by wireless providers to protect their customers. This is not a list of spammers.

                                                        The purpose of the domain name registry is to protect cellular and other commercial mobile radio service (CMRS) wireless consumers from unwanted commercial electronic mail messages, by identifying, for those who send commercial electronic mail messages, Internet domain names used to transmit electronic messages to CMRS consumers. For more information, click on the CAN-SPAM link on the left side of this page.

                                                        tmomail.net was posted on 02-07-2005

                                                        https://www.ctia.org/docs/default-source/default-document-library/170119-ctia-messaging-principles-and-best-practices.pd…

                                                        Ensuring your SMS Messaging Service Complies with the TCPA - TextIt Blog

                                                        1 of 1 people found this helpful
                                                          • executor-brandon

                                                            Re: email to sms gateway issues

                                                            Unfortunately this blog does not allows edits or deletes from what I can see, if you know where to edit/delete posts then please let me know so I can mask those phone numbers.

                                                             

                                                            • Emails are addressed to a large "undisclosed-recipients" list in each payload which is another bulk spam characteristic.

                                                                 (This is only to 16 other UNDISCLOSED RECIPIENTS, prevents cross-reply texting upon group messages. Kinda like BCC instead of CC)

                                                            • Sending large volumetric sales related payload and suspicious message formatting, i.e. all caps.

                                                                 (The ALL CAPS aka SHOUTING issue has just been resolved. We were worried about that in the beginning but all clients were SHOUTING in every message and didn't have issues.)

                                                            • I see where messages were passing on 1/17 and then a gradual aggregate spam score was received approximately 1/21.
                                                            • Aggregate spam scoring is based on dynamic scoring pertaining to IP source, volumetric limits, and dynamic ISP DNSBL reputation related blacklists.

                                                            (We have removed and replaced 2 IP addresses between those times that were "smtp relay" attacked.  All of our IP addresses are now closely monitored by Cloudmark and Barracuda)

                                                             

                                                            I believe this issue this is constant shouting. Hopefully this corrects all form future messaging. Thank you so much for your reply I have called T-Mobile tech support, opened tickets, wrote to Barracuda and this is the only logically answer found. Bravo!

                                                        • magenta3930257

                                                          Re: email to sms gateway issues

                                                          Hi Sean, --- please see the message below. It looks like my sms is being rejected as spam. However it is my small home automation which generate email to sms gateway mesage. Please look into this and advice.

                                                           

                                                          Thanks,

                                                          Gery

                                                           

                                                          This message was created automatically by mail delivery software.

                                                           

                                                          A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

                                                          removed.number@tmomail.net:

                                                          SMTP error from remote server for TEXT command,

                                                          host: d79033b.ess.barracudanetworks.com (209.222.83.70)

                                                          reason: 550 permanent failure for one or more recipients (removed.number@tmomail.net:blocked)

                                                           

                                                          --- The header of the original message is following. ---

                                                           

                                                          Received: from infongp-us28.perfora.net ([74.208.114.115]) by

                                                          mrelay.perfora.net (mreueus003 [172.19.143.3]) with ESMTPA (Nemesis) id 0MMV5c-1ei4bX1d6M-008IPW for <removed.number@tmomail.net>; Wed, 24 Jan 2018

                                                          04:40:41 +0100

                                                          Received: from 2601:243:c00:f6a8:a9e1:f591:9cf7:f796 (IP may be forged by CGI script)

                                                              by infongp-us28.perfora.net with HTTP

                                                              id 0EYpSD-1fEM5i0zIp-00aFZl; Tue, 23 Jan 2018 22:40:41 -0500

                                                          X-Sender-Info: <164026931@infongp-us28.perfora.net>

                                                          Date: Tue, 23 Jan 2018 22:40:41 -0500

                                                          Message-Id: <0EYpSD-1fEM5i0zIp-00aFZl@infongp-us28.perfora.net>

                                                          Precedence: bulk

                                                          To: removed.number@tmomail.net

                                                          Subject: Your garage status

                                                          From: Your garage <webmail@removed.personal.info>

                                                          X-Sender: PQ <webmail@removed.personal.infowebmail@polquest.net>

                                                          X-Mailer: PHP/5.4.45

                                                          X-Priority: 0

                                                          MIME-Version: 1.0

                                                          Content-Type: text/html; charset=utf-8

                                                          X-Provags-ID: V03:K0:7+B2X/OPUk2RSWdIvaDxH3QucdC15upnySXFfrUIlu3ThGV6hhf

                                                          HjE62RRPROa4GKAJ7A61GyPcJFJfYtx97BAH6wwQEiPmWN2JpAgw4zIa1znealmyAX/tcZC

                                                          0HTVFvhy4xtFOXWNBL0neX6y3Vt7egjHDQcVNt9KIWkGFQ2GAps2TKBr/VzJgWqm7Chw/k9

                                                          MPtXuPii7pSYPtOyidMieU+kexdpPssd578fDh+poc=

                                                          X-UI-Out-Filterresults: notjunk:1;V01:K0:3wC0XgChE/o=:mTlXEzC22lZNSMtyEMfxaZ

                                                          JlMKHnRHo2+nfoX1ZUq238U36kclY5z9WSXC3axQ6kqfu1I1GFqxCeoTSc5CHSfkJXRLbN+D0

                                                          wjbZgFQAyFcFGTBVoUkfrVibqxxLjeIb65AWRLKmkcLUgKSRwjoRm5z9KdHajLJvuPO/R713O

                                                          7uMjJpeTp+DMKiLsXBNWN9VBX7bWcMCvZdal9y71Q11SU2wWTQb56UDV47tjSVwa0A5d8Suci

                                                          CDybS/Ijvb692nvH4/9zVlKEPrdtPMU/mTkISFOcpV0xyMgQYyAg4kLsMVHBeAp5rdQbe8ZWw

                                                          7mor69Z6F7AFnCgz6fFPnBQWr1U/xcpPSitQm/oZHY2UuwneWXdbXQ+mSZnEmX/hPFp5k0ZFl

                                                          AOw7wjObvLixfpvuBwUwafm2sUqXI36wo7Lzs34+2ZVI6zji8b8lK5WBiIjmfPWuCMPL59n8Y

                                                          I8U1hBRM7UJFY/s+kAJCttfrIdADm27kZ1k7CJSZciNAZd0iaTR/IBRM+Rh6dKC1sir8mzDSn

                                                          v50wPr+Z+ypBNDdgjAkesMauUvwi1QQPq+P6J3cznT1aWJRUR9Bie4wE2DmV8dsaTVrH25VUF

                                                          rLRQxvkUkdgM9TSuBqre9PM1NQpyPqUCgkanB6xbpDggDmKgnINsbsR2wHLzLiOHsmc1A7TVl

                                                          sqW4j5YBwEIA/iGxMBrpKOsYze8pTJ3NZk8Xg2Oy/jxf+TNKwZ/ITDPdz1LtnmqMeAY1F1Jx/

                                                          9bsAZxs2Y+gDvmffiSGeywKG9HJe8k0UJbywWvK+5DOWemnb8G87f8pkTCU=

                                                            • srickar

                                                              Re: email to sms gateway issues

                                                              Hi.

                                                              Thanks for bringing this to my attention. Many legitimate services share ISP outbound email connections with spammers and unfortunately, perfora.net was used for mass phishing attack last year.  Perfora.net was intentionally blocked because there was a spam attack originating directly from perfora outbound SMTP servers. Normally I try to block specific sources but the attack was widespread across Perfora spamming tmomail.net recipients over 200k messages per day. The attack reluctantly required to block a large block of Perfora IP addresses in the 74.xxx range.

                                                               

                                                              I have unblocked perfora.net, but if it occurs again, I will be forced to block any mass source of spam. Since spammers rely on this type of breach, they seek IPs that cannot be outright blocked that would impact legitimate traffic use.

                                                              1 of 1 people found this helpful
                                                                • magenta3930257

                                                                  Re: email to sms gateway issues

                                                                  Thanks. It works now.

                                                                  • magenta4399938

                                                                    Re: email to sms gateway issues

                                                                    Sorry to dogpile onto this thread — I too am experiencing a similar issue.

                                                                     

                                                                    Here's the response I'm getting:

                                                                    Original-Envelope-Id: <6f17c2bc-68cb-3cae-892c-5335052eff11@fused.com>

                                                                    Reporting-MTA: dns;out-3.smtp.fused.com

                                                                    Arrival-Date: Thu, 15 Mar 2018 08:40:21 -0500

                                                                     

                                                                    Final-Recipient: rfc822;14236197147@tmomail.net

                                                                    Action: failed

                                                                    Remote-MTA: d79033b.ess.barracudanetworks.com

                                                                    Diagnostic-Code: smtp;550 permanent failure for one or more recipients (1xxxxxxxx@tmomail.net:550 Sender IP reverse lookup rejected)


                                                                    I'm sending from david@fused.com.
                                                                    Mind sorting? Note that fused.com doesn't host any free email accounts or such, so whitelisting would be optimal

                                                                      • srickar

                                                                        Re: email to sms gateway issues

                                                                        Header as received:

                                                                        Received: from out-3.smtp.fused.com (bb-3.out.fused.email [69.162.149.152]) by mx2003.ess.tym.cudaops.com (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 15 Mar 2018 13:32:51 +0000

                                                                        Received: (Haraka outbound) with LOCAL id BA44E6C7-8F46-4CA0-9408-3A6F2CD88073.1; Thu, 15 Mar 2018 08:32:50 -0500

                                                                        Authentication-Results: out-3.smtp.fused.com; iprev=pass; auth=pass (plain)

                                                                        Received: from users-MacBook-Pro.local (host-204-93-127-55.APIOLT4.epbfi.com [204.93.127.55])

                                                                        by out-3.smtp.fused.com (Haraka/2.7.3) with ESMTPSA id BA44E6C7-8F46-4CA0-9408-3A6F2CD88073.1

                                                                        envelope-from <dxxxx@fused.com> (authenticated bits=0);

                                                                        Thu, 15 Mar 2018 08:32:49 -0500

                                                                        To: xxx619xxxx@tmomail.net

                                                                        From: "dxxxx@fused.com" <dxxxx@fused.com>

                                                                         

                                                                        Sender IP: 69.162.149.152 (bb-3.out.fused.email)

                                                                         

                                                                        $ host fused.com

                                                                        fused.com has address 52.119.44.6

                                                                        fused.com mail is handled by 10 mail.corp.fused.com.

                                                                         

                                                                        $ dig -x 69.162.149.152

                                                                         

                                                                         

                                                                        ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4 <<>> -x 69.162.149.152

                                                                        ;; global options: +cmd

                                                                        ;; Got answer:

                                                                        ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2373

                                                                        ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

                                                                         

                                                                        ;; QUESTION SECTION:

                                                                        ;152.149.162.69.in-addr.arpa.  IN      PTR

                                                                         

                                                                        ;; ANSWER SECTION:

                                                                        152.149.162.69.in-addr.arpa. 86366 IN  PTR    bb-3.out.fused.email.

                                                                         

                                                                        I cannot whitelist external SMTP clients when the root cause is invalid SMTP server banner mismatch. The outbound MTA for fused.com is not matching reverse DNS. The reject message "550 Sender IP reverse lookup rejected" is generated based on presented information from the connecting SMTP. Need to update MX records.

                                                                         

                                                                        You would need to verify with Fused hosting as to the correct use of SMTP settings.

                                                                        $ dig txt fused.com +short

                                                                        "v=spf1 +ip4:52.119.44.4 +ip4:216.86.157.103 +a:srv3.fused.com +ip4:69.64.153.128/29 +include:_spf.fused.com +include:relay.mailchannels.net -all"

                                                                        "google-site-verification=OXNsoL4aXmPmuRG_zvVn8lJ1gmWZ1gtMPWCoKYNVMMU"

                                                                         

                                                                        Please visit this tutorial link to read up on why the rDNS is invalid. I dont know if you are using Fuse for hosting service or actually trying to send directly as a fused.com branded message or just need help with configuring the SMTP setup. But as configured, this setup is mismatched and will not be permitted by the hosts as per their MX setup.

                                                                         

                                                                        SMTP      - SMTP Banner Check

                                                                         

                                                                        SMTP Banner CheckReverse DNS does not match SMTP Banner

                                                                        $ drill mx fused.com

                                                                        ;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 61419

                                                                        ;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

                                                                        ;; QUESTION SECTION:

                                                                        ;; fused.com.  IN      MX

                                                                         

                                                                         

                                                                        ;; ANSWER SECTION:

                                                                        fused.com.      7200    IN      MX      10 mail.corp.fused.com.

                                                                • magenta4393668

                                                                  Re: email to sms gateway issues

                                                                  Our SPF records are setup correctly

                                                                  we are also seeing these 550 errors coming from ‘Exchange Online’.
                                                                  Is there something they can do to let our traffic through?