Trying to send MMS to email recipients

Trying to send MMS to email recipients SearchSearch
Author Message
FRaveau
New member
Username: Fraveau

Post Number: 38
Registered: 06-2012
Posted on Thursday, January 24, 2013 - 10:30 am:   

Hi,

As the title says, I'm trying to use MMS 2 email. Everything looks fine but the mail doesn't seams to leave.

The MMSCDEBUG.log last signs of a sending are:

11:17:13:300 [5] QueryMXRecord: Querying host XX.2.0.1 for MX record of yahoo.com
11:17:13:300 [5] QueryMXRecord: MX Result for yahoo.com: mta5.am0.yahoodns.net 1
11:17:13:300 [5] QueryMXRecord: MX Result for yahoo.com: mta6.am0.yahoodns.net 1
11:17:13:300 [5] QueryMXRecord: MX Result for yahoo.com: mta7.am0.yahoodns.net 1
11:17:37:480 [5] QueryMXRecord: Querying host YY.2.0.2 for MX record of yahoo.com
11:17:37:480 [5] QueryMXRecord: MX Result for yahoo.com: mta7.am0.yahoodns.net 1
11:17:37:480 [5] QueryMXRecord: MX Result for yahoo.com: mta5.am0.yahoodns.net 1
11:17:37:480 [5] QueryMXRecord: MX Result for yahoo.com: mta6.am0.yahoodns.net 1
11:18:01:785 [5] ThreadRouteSMTPOut: Outbound route SMTP: setting retry for F1CB8B34.RFC

and it keeps retrying.

The MX nslookup looks fine:

> yahoo.com
Serveur : ns1.XXX.net
Address: XX.2.0.1

Réponse ne faisant pas autorité :
yahoo.com MX preference = 1, mail exchanger = mta5.am0.yahoodns.net
yahoo.com MX preference = 1, mail exchanger = mta6.am0.yahoodns.net
yahoo.com MX preference = 1, mail exchanger = mta7.am0.yahoodns.net

yahoo.com nameserver = ns4.yahoo.com
yahoo.com nameserver = ns5.yahoo.com
yahoo.com nameserver = ns2.yahoo.com
yahoo.com nameserver = ns3.yahoo.com
yahoo.com nameserver = ns8.yahoo.com
yahoo.com nameserver = ns1.yahoo.com
yahoo.com nameserver = ns6.yahoo.com
ns1.yahoo.com internet address = 68.180.131.16
ns2.yahoo.com internet address = 68.142.255.16
ns3.yahoo.com internet address = 121.101.152.99
ns4.yahoo.com internet address = 68.142.196.63
ns5.yahoo.com internet address = 119.160.247.124
ns6.yahoo.com internet address = 202.43.223.170
ns8.yahoo.com internet address = 202.165.104.22

What's wrong?

Thank you
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8047
Registered: 10-2002
Posted on Thursday, January 24, 2013 - 07:31 pm:   

Hi Franck,

Although the MMSCDEBUG.LOG does not make mention of it, NowSMS has tried to connect to SMTP port 25 on mta5.am0.yahoodns.net, mta6.am0.yahoodns.net and mta7.am0.yahoodns.net. And all attempts have failed.

You should be able to recreate the same problem with a TELNET client.

Why would this happen?

Well ... spam is a major problem in the e-mail world.

As a result, setting up your own mail server is quite a pain these days.

Most of the major e-mail services want to make sure you have a static IP address with a reverse DNS entry (in-addr.arpa) defined for it.

If your organisation has an existing mail server that can relay for you that is often the easiest solution.

-bn

Bryce Norwood
Now SMS/MMS Support
FRaveau
New member
Username: Fraveau

Post Number: 39
Registered: 06-2012
Posted on Thursday, January 24, 2013 - 08:45 pm:   

OK I see. I'll use the company mail server.

Is there any kind of authentication when relaying?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4268
Registered: 08-2008
Posted on Wednesday, January 30, 2013 - 07:34 pm:   

Sorry for the delay in response.

Below are configuration parameters for specifying a username and password for SMTP Authentication on the "SMTP Relay Host" that is configured for outbound SMTP e-mail delivery.

These parameters must be manually defined in the MMSC.INI file, under the [MMSC] header: RelayHostUsername=xxxxx and RelayHostPassword=xxxxx

--
Des
NowSMS Support
FRaveau
New member
Username: Fraveau

Post Number: 40
Registered: 06-2012
Posted on Thursday, January 31, 2013 - 01:10 pm:   

Hi,

The company SMTP requires to know the sender adress to relay. Therefore this option is heavy.

So I'm still trying to use the SMTP smart mailer (Antispam shouldn't be a problem as the server has a know public IP). When I try to use it using telnet I get the following error:

> telnet localhost 25

220 SMTP Ready
MAIL FROM:fraveau@XXX.com
250 Ok
RCPT TO:myadress@YYY.com
550 Recipient unknown or not local

Why do I get an error on the recipient?

Regards
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4273
Registered: 08-2008
Posted on Thursday, January 31, 2013 - 09:23 pm:   

Hi,

Make sure the server has a valid reverse DNS entry (in-addr.arpa). This is something that generally needs to be setup by your service provider as they own the block of IP addresses.

That said, this likely has nothing to do with your TELNET test.

To answer that, I need more specifics. How does myaddress@YYY.com relate to your NowSMS installation?

If YYY.com is not a local domain name associated with the NowSMS installation, that would trigger this error. (It will not act as a relay server.)

If myaddress is not a locally define "MMSC Users" account (or in some cases an "SMS Users" account), this can also trigger this issue ... unless the "MAIL FROM:" address is in the "Authorised E-Mail" sender list.

--
Des
NowSMS Support
FRaveau
New member
Username: Fraveau

Post Number: 42
Registered: 06-2012
Posted on Monday, February 04, 2013 - 02:58 pm:   

Hi,

So the SMTP smart mailer can't be used to send an MMS to eg fraveau@gmail.com isn't it?

In this case I really have to solve the company SMTP server issue...

Franck
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4282
Registered: 08-2008
Posted on Monday, February 04, 2013 - 04:11 pm:   

Hi Franck,

I'm not saying that it is not possible. There are just issues because when you use the SMTP smart mailer, you are essentially deploying your own SMTP mail server.

Let's go back to your first post in this thread.

Trying to send to yahoo.com returns the three mail server addresses listed in your post (mta5.am0.yahoodns.net, etc.).

Each of those mail servers has 8 different IP addresses associated with it.

You'll notice 24 second delays in the debug log after the first MX query and before we try the next name server to see if we get different results.

During those 24 seconds, the smart mailer in the MMSC is actually looping through all 8 IP addresses associated with all 3 server names, trying to connect to port 25 on any of those hosts.

The fact that it only takes 24 seconds for all of these attempts to fail is actually quite surprising to me. I'd suspect that you have a company firewall or ISP firewall that blocks port 25 connections.

There are companies that enforce these types of policies to prevent malware or botnets from being used to send out information.

There are ISPs who enforce similar rules on consumer accounts, wanting all outbound e-mail to be routed via the ISP relay SMTP servers for spam checking.

If all of your outbound SMTP attempts are just showing MX record lookups, but no actual SMTP data, then I think you're being blocked in this fashion, either by your company IT policy or an ISP policy.

In that case, I jumped the gun in discussing the other mail server issues.

In these scenarios, you see SMTP connections occurring, but with SMTP error codes being reported ... or with messages being routed to spam folders.

The most common requirement (not spelled out by standard, but "de facto") is that a mail server must have a reverse DNS name entry. (See http://en.wikipedia.org/wiki/Reverse_DNS_lookup for more explanation if you are not familiar with in-addr.arpa)

--
Des
NowSMS Support
FRaveau
New member
Username: Fraveau

Post Number: 43
Registered: 06-2012
Posted on Monday, February 04, 2013 - 04:30 pm:   

My first test is no longer relevant: I asked from that time to the comppany admin to open port 25 from the MMSC server. I not blocked anymore.

My current error when trying to use the smart mailer is the following:

> telnet localhost 25

MAIL FROM:+33123456789@mailMmsDomainName
250 Ok
RCPT TO:fraveau@yahoo.com
550 Recipient unknown or not local

Where +33123456789 is a declared MMSC user.

I understand fraveau@yahoo.com is not know by the MMSC but why should it be? We don't want to manage the recipients our customers are supposed to be able to send MMS to.

Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4283
Registered: 08-2008
Posted on Monday, February 04, 2013 - 09:06 pm:   

Hi Franck,

I guess I'm confused because I don't understand why the MMSC should accept such a message via SMTP.

It would accept a message TO that user (the phone number), and might generate a message FROM that user. However, it should not operate as an open relay.

Help me understand what you're trying to accomplish with this.

--
Des
NowSMS Support
sam
Frequent Contributor
Username: Samdsouza

Post Number: 114
Registered: 08-2006
Posted on Tuesday, February 05, 2013 - 07:43 am:   

Hi FRaveau

Check the following things:

1. Enable SMTP Smart Mailer on the MMSC settings of NowSMS.

2. In this +33123456789@mailMmsDomainName...is the mailMmsDomainName pointing in its DNS record to the IP address of the server where you installed NowSMS? If not then plz add the IP address of the server to that mailMmsDomainName DNS.

I got it working with the above setup.

Sam
sam
Frequent Contributor
Username: Samdsouza

Post Number: 117
Registered: 08-2006
Posted on Tuesday, February 05, 2013 - 07:59 am:   

FRaveau

Forgot to add this

3. What is the SMTP port you have defined on MMSC settings? Keep it 25 (default SMTP port)and add port 25 as an exception in windows firewall if its on. If you keep port 25 as SMTP port on NowSMS then you would need to disable other Mail services which would have 25 port defined for their use.
FRaveau
New member
Username: Fraveau

Post Number: 44
Registered: 06-2012
Posted on Tuesday, February 05, 2013 - 08:56 am:   

Hi guys,

I'm trying to do MMS to Email so the test sounds good to me: an MMSC user send a mail to an "external" email recipient, with no restriction on the domain of it, isn't?

My feedbacks on the points to check are:

1. Done
2. MailMmsDomainName is registered in MX DNS as the company mail server domain name ("Domain Name for MMS Email" in MMSC tab). It's not the domain name of the MMS server ("Local Host Name or IP Adress" in MMSC tab)
3. Port 25 is defined in MMSC and opened in firewalls. Admin see trafic go out when I tryed to use the company SMTP server.

I can send config files by mail if it helps.

Thank you
sam
Frequent Contributor
Username: Samdsouza

Post Number: 118
Registered: 08-2006
Posted on Tuesday, February 05, 2013 - 03:26 pm:   

Hi FRaveau

"an MMSC user send a mail to an "external" email recipient, with no restriction on the domain of it, isn't?

yes. this is correct. you can send to any external email recipient.

So we got this issue only

2. MailMmsDomainName is registered in MX DNS as the company mail server domain name ("Domain Name for MMS Email" in MMSC tab). It's not the domain name of the MMS server ("Local Host Name or IP Adress" in MMSC tab)


In Local Host Name or IP Adress the domain/IP can be different. Try keeping the IP address of the server instead of any domain name. if you keep domain name of the MMS server then the domain name has to point to the NowSMS server IP address

Now "MailMmsDomainName" the DNS record is an issue. For "MailMmsDomainName" do you have the A record? If yes then is this A record for MailMmsDomainName pointing to your NowSMS server IP?

Something like following in your DNS file for MailMmsDomainName:


@ A 1.0.0.127 (This should be the static IP address of your NowSMS server)
@ MX 1 MailMmsDomainName. (This is the Mail record)

So basically you might be missing the A record for "MailMmsDomainName"

go to www.network-tools.com put in "MailMmsDomainName" and give it a express test and see if the IP address you get in the ping matches with your NowSMS server IP or not.

Des correct me if my assumptions are wrong.

Regards
Sam
FRaveau
New member
Username: Fraveau

Post Number: 45
Registered: 06-2012
Posted on Tuesday, February 05, 2013 - 04:53 pm:   

"Local Host Name or IP Adress" = mms.mycompany.fr

I add a domain name that points to the public IP of the MMSC server. I prefered to use a domain name instead of a IP because this field is used to build the link in the legacy SMS isn't?

"Domain Name for MMS Email" = mycompany.fr

It's the domain name used by my company's SMTP server (ruled solution for MMS serv) so it doesn't point to the MMS server.

So the solution might be to add MX record to mms.mycompany.fr? I'll talk to the admin about that.

Thanks

Franck
FRaveau
New member
Username: Fraveau

Post Number: 46
Registered: 06-2012
Posted on Tuesday, February 05, 2013 - 05:03 pm:   

But again, it doesn't fit with my error "550 Recipient unknown or not local"...
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4284
Registered: 08-2008
Posted on Tuesday, February 05, 2013 - 09:25 pm:   

Hi Franck,

I think I understand the problem ...


quote:

I'm trying to do MMS to Email so the test sounds good to me: an MMSC user send a mail to an "external" email recipient, with no restriction on the domain of it, isn't?




Submit the via an MMS client and it will be sent.

The problem is that you're submitting via SMTP.

From an SMTP perspective, the MMSC will accept that phone number as a "TO" address, but not as a "FROM".

(The MMSC will generate an outbound e-mail with that phone number as a "FROM" address, but the message must be submitted via MMS.)

--
Des
NowSMS Support
FRaveau
New member
Username: Fraveau

Post Number: 50
Registered: 06-2012
Posted on Tuesday, April 09, 2013 - 09:07 am:   

Hi,

you said about configuring external smtp connection:

These parameters must be manually defined in the MMSC.INI file, under the [MMSC] header: RelayHostUsername=xxxxx and RelayHostPassword=xxxxx

Can I also configure a specific port and protocol for secure connection(SSL)?

Thanks
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4370
Registered: 08-2008
Posted on Tuesday, April 09, 2013 - 04:59 pm:   

Hi Franck,

Before I directly answer your question, I should mention that in the latest update has some new flexibility with regard to e-mail handling.

Historically, NowSMS has required a direct SMTP configuration.

That offers a lot of flexibility, especially for an MMSC configuration, because you can give each subscriber their own e-mail address.

However, as numerous discussion threads on this forum will attest, setting up and maintaining an SMTP mail server is hard work that is best left to e-mail specialists and IT departments.

With so many of our customers using externally hosted mail servers, setting up NowSMS as a stand-alone SMTP mail server can be a steep learning curve.

In response to this, we've added a new configuration option for e-mail to/from SMS or MMS.

Instead of functioning as a stand-alone SMTP mail server, the latest version of NowSMS can be configured to send/receive e-mail through a standard POP3 or IMAP mailbox. IMAP, in particular, is a good choice, especially if you use an IMAP server (hint: GMail) that supports the IDLE command. One of the limitations of POP3 or IMAP compared to SMTP is that new e-mail is not automatically pushed to NowSMS, instead we need to poll the server for new mail. However, with IMAP IDLE support, NowSMS can stay connected to the mail server, and the mail server pushes new e-mail messages as they are received.

Because all e-mail is routed through a single mailbox, instead of including the phone number in the e-mail address, it needs to be included in the subject line.

Anyway ... before I directly answered your question, I wanted to explain that this type of alternate configuration was now available. If you are interested, configuration details are described under the 2013-04-01 header at http://www.nowsms.com/download/changes.txt

Back to your question ...

The 2013-04-01 update does now support using SSL/TLS for relay server connections. Under the [MMSC] header, add RelayHostUseSSL=Yes

Alternate SMTP port numbers can be specified in the RelayHost setting using the format server.name:port

If port is not specified, port 587 is assumed if SSL/TLS is enabled, and port 25 is assumed otherwise.

The update is at http://www.nowsms.com/download/nowsms20130401.zip.

--
Des
NowSMS Support