Mmsc log - many emails rejected | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
Author | Message | |||
dinos New member Username: Dinaras Post Number: 35 Registered: 02-2006 |
Hello everybody, I have enabled email2sms on my nowsms. I see in mmsc-date.log many lines like this 2011-10-06 00:03:52,SMTPIN,X.X.X.X,Mailer-Daemon@domain.com,Mailer-Daemon,REJECTED,REJECTED In mmscdebug.log i see 08:27:19:890 [13] ThreadProcessConnectionSMTP: 220 SMTP Ready 08:27:19:890 [6] ThreadRouteSMTPOut: HELO mmsc.domain.com 08:27:19:890 [6] SendCommand: HELO mmsc.domain.com 08:27:19:890 [13] ThreadProcessConnectionSMTP: HELO mmsc.domain.com 08:27:19:890 [13] SendCommand: 250 Ok 08:27:19:890 [6] ThreadRouteSMTPOut: 250 Ok 08:27:19:890 [13] ThreadProcessConnectionSMTP: 250 Ok 08:27:19:890 [6] ThreadRouteSMTPOut: MAIL FROM:<Mailer-Daemon@email2mms.domain.com> 08:27:19:890 [6] SendCommand: MAIL FROM:<Mailer-Daemon@email2mms.domain.com> 08:27:19:890 [13] ThreadProcessConnectionSMTP: MAIL FROM:<Mailer-Daemon@domain.yuboto.com> 08:27:19:890 [13] SendCommand: 250 Ok 08:27:19:890 [6] ThreadRouteSMTPOut: 250 Ok 08:27:19:890 [13] ThreadProcessConnectionSMTP: 250 Ok 08:27:19:890 [6] ThreadRouteSMTPOut: RCPT TO:<Mailer-Daemon@email2mms.domain.com> 08:27:19:890 [6] SendCommand: RCPT TO:<Mailer-Daemon@email2mms.domain.com> 08:27:19:890 [13] ThreadProcessConnectionSMTP: RCPT TO:<Mailer-Daemon@email2mms.domain.com> 08:27:19:890 [13] SendCommand: 550 Recipient unknown or not local 08:27:19:890 [6] ThreadRouteSMTPOut: Recipient rejected 08:27:19:906 [13] ThreadProcessConnectionSMTP: 550 Recipient unknown or not local 08:27:19:906 [6] ThreadRouteSMTPOut: 550 Recipient unknown or not local Why do i get all this rubish? Under what conditions does this happen? It didnt use to be like that in the past. Thank you very much in advance Regards Dinos | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3502 Registered: 08-2008 |
Hi Dinos, I'd have to see more of the overall context, but Mailer-Daemon messages are generally auto-generated e-mail messages that occur when someone sends to an invalid e-mail address. (Or when a receiving e-mail system refuses to accept a message for spam reasons. One tip in this regard ... make sure you have a reverse DNS entry defined for your system. Many e-mail servers will refuse to accept e-mail from servers that do not have reverse DNS configured.) -- Des NowSMS Support | |||
dinos New member Username: Dinaras Post Number: 36 Registered: 02-2006 |
I have set mx record for email2sms.domain.com and email2mms.domain.com So you are suggesting to me to set A records also for these domain names? Thanks in advance | |||
dinos New member Username: Dinaras Post Number: 37 Registered: 02-2006 |
By the way, i just realised that the above behaviour started after i upgraded my nowsms to latest version e.g. 2011.07.05 Does that ring any bell? Thank you in advance Regards Dinos | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3504 Registered: 08-2008 |
Dinos, I can't provide any more insight without seeing more overall context. Mailer-Daemon messages are generally auto-generated e-mail messages that occur when someone sends to an invalid e-mail address. So I would expect that earlier in the log, there was an incident of someone sending to an invalid e-mail address. That's what I mean by needing more of the context in which this occurs. That said, the log looks like it might be sending messages to itself. I didn't think of that before, because the "MAIL FROM:" address wasn't a match. But I think that's only because you changed the domain name in your edits, and missed one. If this is somehow a Mailer-Daemon mail loop, create an "SMS User" account with a username of Mailer-Daemon. Check "Enable SMTP login for this user", and "Accept received messages for this user". I'll investigate what might cause a Mailer-Daemon mail loop. By "reverse DNS", I am not referring to an A or MX record. Reverse DNS uses the in-addr.arpa. It is a reverse lookup system where you can check the host name associated with an IP address. In normal DNS, for an A record, you lookup a host name to find the IP address. With Reverse DNS, you lookup an IP address to find an associated host name. Wikipedia has a good write-up on reverse DNS at http://en.wikipedia.org/wiki/Reverse_DNS_lookup In most cases, you have to talk to your hosting provider in order to get a reverse DNS entry defined. Whatever provider is responsible for allocating the block of IP addresses that your addresses come from is the party that has control over reverse DNS. -- Des NowSMS Support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3505 Registered: 08-2008 |
Follow-up ... If this is a Mailer-Daemon error loop that is occurring, instead of creating that "SMS User" account, I'd suggest this instead: Edit MMSC.INI, and under the [MMSC] header add: SystemUser1=mailer-daemon This will cause any message to mailer-daemon to be silently ignored. -- Des NowSMS Support | |||
dinos New member Username: Dinaras Post Number: 38 Registered: 02-2006 |
Hello Des, Today, i changed my alias toy Mailer-Daemon and i received in my mobile the email message that gets rejected. The message just contains the word ERROR about 30 times, and also says message to Mailer-Daemon could not be delivered. Does this help at all? I believe just silently ignoring the message is not a solution as clearly something is going wrong here Thank you very much Regards Dinos | |||
dinos New member Username: Dinaras Post Number: 39 Registered: 02-2006 |
Just to make a correction, message i received on my mobile was email2mms, so its Mailer-Daemon@email2mms.domain.com Also i had to change back my alias, as it was sending messages to me all the time. There is something that is generating this error or this message all the time for some reason | |||
dinos New member Username: Dinaras Post Number: 40 Registered: 02-2006 |
I finally managed to find out when this error happens. I went to MMSC settings, and disable "SMTP Smart Mailer" and used an smtp relay. Now i dont have the above described behavior, and everything works as expected. I suppose something is happening when smart mailer is used, but i am sure you will find it Thank you very much Regards Dinos | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3510 Registered: 08-2008 |
Dinos, You do want to have the messages to Mailer-Daemon rejected. They are a symptom, not the underlying problem. Essentially they are just a looping error. A message from Mailer-Daemon occurs when the system is unable to send an outbound e-mail message. A message to Mailer-Daemon occurs if the error message that was generated from Mailer-Daemon can also not be delivered. If this happens, there will be a loop. Trapping them is ok, but they really should be ignored/discarded, as they are a symptom, not a problem. (Future versions will ignore/discard them ... essentially implementing the SystemUser1=mailer-daemon setting mentioned above by default.) The underlying problem remains, there was an error delivering an e-mail message. Mailer-Daemon tried to report this error back to the sender, but the sender was also not reachable. This delivery failure could have been triggered by a lack of reverse DNS being setup. In any event, I think using an SMTP relay host is a good idea, if you have that option. Configuring an SMTP mail server can be a complex task, and if you can relay through an existing working mail server, that is much easier. -- Des NowSMS Support |