|
You are totally clear. If you wish to continue using the 170 for SMTP mail, I would definitely suggest getting off of the AS400's SMTP. Domino's SMTP is much more reliable and utilizes less resources. If you are going to move your SMTP mail routing, I would still use Domino's SMTP for the same reasons as previously stated. There are other factors for moving the SMTP to its own server, one is isolation (you can take down the SMTP Domino server without affecting your web site) and another is if the amount of SMTP traffic is significant, it may be easier to control resources on a separate server without affecting your web server. Thanks, Dave Guerrero Senior Consultant e-Business Solutions Computech Resources, Inc. MEovino@ESTES-EXPR ESS.COM To: DOMINO400@midrange.com Sent by: cc: owner-domino400@mi Subject: Re: Router Job in Domino subsystem drange.com 09/14/2000 06:53 AM Please respond to DOMINO400 Dave, Here's what we're doing (I hope I'm being clear when I explain this) We basically have two domino servers on two different 400's (we have a third on an NT box, but that shouldn't come into play here, we only use it for Domino.Doc) The Domino server on the 170 is connected to the internet, and it does HTTP serving, routes incoming mail from the internet to our 650 (where the users' mail files are) and routes outgoing mail from the 650 to the internet. We are serving static HTML pages, Domino web apps (some are just forms for collecting information and others contain content stored in Rich Text format that is created by our departments) and Net.Data CGI programs. When we were on 4.6.3, the 170 handled all of this pretty admirably, but since we moved to R5 things have slowed considerably. The Domino server on the 650 is connected to the 170 via our internal TCP/IP network (it is not accessible from the internet [I hope]). It handles our internal mail, takes incoming mail from the 170 and routes it to the appropriate user and sends outgoing mail to the 170 to be sent to the internet. To make matters more interesting, we could not get Domino's native SMTP on the 170 to successfully send mail to and receive mail from the internet, so we are still using the native 400 SMTP on the 170 to receive mail from and hand mail off to Domino SMTP on the 170. Confused yet? What we're thinking about doing is not using the 170 for mail at all. It would just handle webserving. Another box would just handle sending mail to and receiving mail from the internet. Mike E. If you have any mail that will need to move through that Domino server to another Domino server (whether mail files exist or not), you will need to keep the router task running. Although you didn't say it, most likely you are doing SMTP mail routing which in R5 is also handled by the router task. Moving the SMTP routing to a different Domino server should help alleviate the CPU percentage. Another possible impact is the amount of memory on the 170 and whether or not you run other applications on it. You did mention that you are serving a web site from the same server. The HTTP task on Domino also uses a lot of resources. Just from past experience, R5 does use more resources than R4 did. Hope this helps... +--- | This is the Domino/400 Mailing List! | To submit a new message, send your mail to DOMINO400@midrange.com. | To subscribe to this list send email to DOMINO400-SUB@midrange.com. | To unsubscribe from this list send email to DOMINO400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: meechamw@ptd.net +--- +--- | This is the Domino/400 Mailing List! | To submit a new message, send your mail to DOMINO400@midrange.com. | To subscribe to this list send email to DOMINO400-SUB@midrange.com. | To unsubscribe from this list send email to DOMINO400-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: meechamw@ptd.net +---
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.