|
I think the terminology here is "Bind Specific". That's what you want to search on. There's a way to tell Domino only to bind to a specific IP address, and a way to tell the native SMTP the same. I just can't remember how off the top of my head. I have about a dozen interfaces defined for domino and other 400 stuff, and another dozen for IXS. Maybe the domino400 list would help? I'll pay attention to the details like you did and see if I notice the same error. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 08/19/2004 04:13 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To "'midrange-l@xxxxxxxxxxxx'" <midrange-l@xxxxxxxxxxxx> cc Fax to Subject RE: Little help on email using SNDDST or QtmmSendMail It's a good day, I learned something new on this exercise: I tried this on my test system and was surprised when STRTCPSVR *SMTP did not start everything right back up. In the joblog for QTSMTPSRVD I found a message: "SMTP unable to bind to Internet Protocol interface 0.0.0.0." followed immediately by SMTP unable to bind to any Internet Protocol interface." and "End of prestart jobs in progress." So I tried starting SMTP through iNav and got the same result. Paging through the SMTP properties tabs in iNav I found the bindings tab, which has two radio buttons labeled "Use all interfaces" and "Select an interface." Use all interfaces was checked. After I checked Select an interface and chose the proper IP address for my ethernet line SMTP started right up and went right back to work. My guess is that when I ended SMTP on the Series my Domino server grabbed the port, at least for its own IP address, causing the SMTP bind to fail on that IP address. I don't know if that's what happens in your case Rob, but in our case SMTP was apparently trying to bind on all lines, including a token ring line and an internal line to an IPCS that are no longer used. Regards, Scott Ingvaldson iSeries System Administrator GuideOne Insurance Group -----Original Message----- date: Thu, 19 Aug 2004 14:57:58 -0500 from: rob@xxxxxxxxx subject: RE: Little help on email using SNDDST or QtmmSendMail Well, maybe the other gent was right. That after SMTP gets started, then MSF recognizes this and no longer has issues and stops pumping out the message that the tcp jobs are not started. But if you do an ENDTCPSVR *SMTP and do a SNDDST as an email, and then do a WRKJOB QMSF see if you don't have something in one of the joblogs about smtp jobs not running. And see if STRTCPSVR *SMTP allows it to start sending, or if you have to do a ENDMSF / STRMSF *RESET after the STRTCPSVR also. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.