| SMTP Problems |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| ZMI |
Hi, when the MMSC tries to send via SMTP, I get on the receiving end: Sep 17 19:51:13 rrws27 sendmail[15499]: NOQUEUE: pckl698.klinik.uni-regensburg.de [132.199.131.98] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA | |||
| ZMI |
The message does not always come, _but_ in every case no mail is sent. This bug was introduced in the b20030912 version and did not exist in the b20030801 and b20030728 versions. These version however procude a _non_ fatal Sep 17 20:11:24 rrws27 sendmail[15649]: h8HIBOI15649: lost input channel from pckl698.klinik.uni-regensburg.de [132.199.131.98] to MTA after rcpt at the other end. | |||
| Bryce Norwood - NowSMS Support |
Hi ZMI, I don't really understand how this correlates to the "sendmail" errors, but we did find that the SMTP interface was mostly non-functional in the version that was included in the beta2update.zip file. I updated the http://www.nowsms.com/download/beta2update.zip file earlier today with a new version of the MMSC.EXE. We added some logic to allow MM4 connections, or even the SMTP relay host to specify an SMTP port other than 25. Unfortunately, that change was not very well tested, and it only worked if a port was specifically specified (where it would not be in all existing configurations). Hopefully we'll get a full beta 3 version uploaded in the next couple of days as we go through and test all of the changed areas. -bn | |||
| ZMI |
OK, SMTP sending (what I am doing is that a VASP connection delivers a MMS targeted to a email address) now seems to work again (and uses the right source port). However, I still see Sep 18 19:30:42 rrws27 sendmail[14529]: h8IHUgI14529: lost input channel from pckl735.klinik.uni-regensburg.de [132.199.131.90] to MTA after rcpt Perhaps you might not say "quit" before you close the port. | |||
| Bryce Norwood - NowSMS Support |
ZMI, We definitely send a QUIT. The only thing I can see that might be an issue is that we do not wait for a response back to the QUIT ... after we send the QUIT we terminate the connection. I can't see why that would cause a problem. But I'm still a bit puzzled by the error message that you get because it says "after rcpt" ... The basic sequence of actions in an SMTP dialog is: HELO or EHLO MAIL FROM: RCPT TO: (one or more of these) DATA (send the content of the message) . Then "QUIT" if you want to end the session, or you may want to "RSET" and send another message (I'm not sure if "RSET" is required in that instance as I'm not an SMTP expert, but it seems like a good idea.) Anyway, if the input channel is lost after a "RCPT TO:" command, that doesn't make sense, because the "DATA" command would have had to follow in order to send the message. But it's always hard to guess what an error message in somebody else's software product means. Maybe we can try a more graceful closing of the port ... wait for the response before closing ... maybe that will make a difference. -bn | |||
| ZMI |
Maybe you only do not send QUIT if you received an error ("relay not allowed" in my case). As a side note: if definitly would be helpful if there could be an option to log the smpt, http, etc. error message the MMSC receives. | |||
| Bryce Norwood - NowSMS Support |
ZMI, That's definitely the case. Any errors, and we abort the connection. It would be nice to see that logged, but I'm not optimistic for that feature right now, as we're getting anxious to finally get this version released. -bn | |||
| ZMI |
> That's definitely the case. Any errors, and we abort the connection. OK, this is no problem here, although it does not seem to be right according to the rfc. Logging can wait for a future release... | |||
| Hisham Unregistered guest |
The question is, is there possibility that the handshake protocol of incomplete sending is not received by client and therefore, the sending is deemed sucessful hence the user claim of email in her Sent folder. Or are there possible problem with our SMTP application if it did not send the incomplete sending message to client. What does details "MTA to rcpt" means? | |||
| Caniffe Unregistered guest |
This issue can also occur if your DNS server fails to resolve the recipient MX records. Check via: dig mx domain.com Is the status reporting SERVFAIL? If so, remedy your resolv.conf or named.conf configuration as appropriate. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1182 Registered: 10-2002 |
Hisham, I'm sorry, but I don't understand the context of your question. Are you connecting to the Now SMS/MMS Gateway via SMTP? -bn | |||
