Re: Flame Bait: Using Qmail as a front-line mail server
--- Sean Chittenden [EMAIL PROTECTED] wrote: * Exchange box is firewalled and boarded up and placed behind wallboard Except you can't do that with an NT box because you'll need access to reboot it every so many days and you can't do that remotely out of the box ;). Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
Re: Flame Bait: Using Qmail as a front-line mail server
enough anti Microsoft shit and lets get on with life. Ross [moved to mutt from Outlook for this listperfer Outlook] On Thu, Aug 09, 2001 at 09:17:24AM +0100, Adam Nealis wrote: --- Sean Chittenden [EMAIL PROTECTED] wrote: * Exchange box is firewalled and boarded up and placed behind wallboard Except you can't do that with an NT box because you'll need access to reboot it every so many days and you can't do that remotely out of the box ;). Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
Re: Flame Bait: Using Qmail as a front-line mail server
Steve writes: 1. Is it possible to list the Qmail server as the primary MX record and still forward the mail to its final destination? All my research says no, but I need to be certain. Use smtproutes. It essentially functions as an MX record with priority -1 (in other words, a stronger priority than any possible MX record). The other way you could do it is with split DNS. djbdns (http://www.djbdns.org) makes split DNS trivially easy. -- -russ nelson [EMAIL PROTECTED] http://russnelson.com Crynwr sells support for free software | PGPok | 521 Pleasant Valley Rd. | +1 315 268 1925 voice | All extremists should Potsdam, NY 13676-3213 | +1 315 268 9201 FAX | be shot.
Re: Flame Bait: Using Qmail as a front-line mail server
On Mon, Aug 06, 2001 at 09:00:46PM -0400, Steve wrote: 1. Is it possible to list the Qmail server as the primary MX record and still forward the mail to its final destination? All my research says no, but I need to be certain. Yes, use smtproutes. See the manual page for qmail-remote.
Re: Flame Bait: Using Qmail as a front-line mail server
1. Is it possible to list the Qmail server as the primary MX record and still forward the mail to its final destination? All my research says no, but I need to be certain. Yes, use smtproutes. See the manual page for qmail-remote. Or create a ton of forwarding rules (.qmail for starters). qmail works as a great buffer between the internet and an Exchange server. * [EMAIL PROTECTED] - qmail box * qmail box looks up .qmail file for user * qmail forwards to [EMAIL PROTECTED] * corp.example.com is exchange and accepts mail for the user from corp.example.com * Exchange routes all outgoing mail to the qmail box as [EMAIL PROTECTED] * Exchange box is firewalled and boarded up and placed behind wallboard -sc -- Sean Chittenden PGP signature
Flame Bait: Using Qmail as a front-line mail server
First, let me say I've searched the archives, Google and numerous other sources BEFORE I decided to post this. I do not desire the attacks that the qmail list is infamous for. The company I work for, a mid-sized ISP, uses Sendmail as the primary MTA for our clients. Given the downturn in the economy, my superiors are very reluctant to budget any kind of switch to Qmail despite my best efforts. As a result, I am stuck with running Qmail on secondary servers. Now the point: Unfortunately, our systems were extremely overloaded by the SirCam virus, and I have been tasked with finding a solution. While I could simply find one that incorporates with Sendmail, I believe this will simply overload our primary mail server. Therefore, I want to use one of the servers running Qmail to do the virus scanning and then send the mail to the primary mail server. Both incoming and outgoing mail must be scanned. Here is my question: 1. Is it possible to list the Qmail server as the primary MX record and still forward the mail to its final destination? All my research says no, but I need to be certain. 2. If #1 is possible, could your generously provide some real world suggestions on how this can be done? Thank you, -- Steve
Re: Flame Bait: Using Qmail as a front-line mail server
1. Is it possible to list the Qmail server as the primary MX record and still forward the mail to its final destination? All my research says no, but I need to be certain. It's trivial. smtproutes is your friend. 2. If #1 is possible, could your generously provide some real world suggestions on how this can be done? It'd be helpful to know the real names of the domains and machines involved, then we could give you a real world config entry, but assuming the MX domain is example.com and the ultimate mail server running sendmail is sendmail.example.com, then: echo example.com:sendmail.example.com /var/qmail/control/smtproutes No restarts are needed. Just change your MX to point to the qmail machine and you're done. Of course you need to make sure that example.com isn't in locals and virtualdomains. It'll be interesting to know how you plan to catch Sircam with this though... Regards.
Re: Flame Bait: Using Qmail as a front-line mail server
On 7 Aug 2001, at 1:09, MarkD wrote: 1. Is it possible to list the Qmail server as the primary MX record and still forward the mail to its final destination? All my research says no, but I need to be certain. It's trivial. smtproutes is your friend. So true! I use it to do just this... We have redundant servers on mutliple net- links. if one link dies, mail is routed via MX entries to the secondary server, which then forwards it via out internal network to the final destination server. Works like a charm. The other nice thing is that if it's the primary server itself that died, then the seconary server will hold the mail until we bring the primary back on line. 2. If #1 is possible, could your generously provide some real world suggestions on how this can be done? It'd be helpful to know the real names of the domains and machines involved, then we could give you a real world config entry, but assuming the MX domain is example.com and the ultimate mail server running sendmail is sendmail.example.com, then: echo example.com:sendmail.example.com /var/qmail/control/smtproutes No restarts are needed. Just change your MX to point to the qmail machine and you're done. Of course you need to make sure that example.com isn't in locals and virtualdomains. Good point... If you have your Sendmail boxes domain listed in the secondary servers locals or virtualdomains files, you will end up delivering the mail locally to the secondary server. Just remember locals take priority over virtualdomains, and virtualdomains take proirity over smtproutes. It'll be interesting to know how you plan to catch Sircam with this though... Definately, please post! BTW, for the record, I switched all my primary Sendmail boxes to qmail for little or no cost. (I chose to pay to register 3 e-smith servers, but you can grab the iso for free from their ftp site) The other nice things is that I find qmail can handle running on lower end equipment and still give you the same if not better performance than a Sendmail box. Cheers Dean Dean Staff Protus IP Solutions 210 - 2379 Holly Lane Ottawa, ON K1V 7P2 Canada 613-733- ex 546 Fax 613-248-4553 e-mail: [EMAIL PROTECTED] Web: http://www.protus.com
Re: Flame Bait: Using Qmail as a front-line mail server
-BEGIN PGP SIGNED MESSAGE- Dean Staff wrote: qmail can handle running on lower end equipment Except for its unfortunate habit of laying bare the i/o bottlenecks you never knew you had. ;-) - -d - -- David Talkington http://www.spotnet.org PGP key: http://www.prairienet.org/~dtalk/dt000823.asc -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQEVAwUBO2+BNr1ZYOtSwT+tAQHgnAf+LRLuElYi7P7LLjqNH+xfjCalJBlbThtq 7stgiatYclo2AOJZVE1XRft3aDbNr0CzGRRBpJQG99H4tsRF75PlrQ4sjiufti19 jxVC2ZpAEIb3sTm0JNt5W98WZXZqqeUeqgicSYRPNXRgum7rdpIKEYoMNhmge3d9 z5Grm6um+pbBEZWpw3ZynFrLfAwRPfkV7+4Uy9migY6xTfZiuEXnZaT59qrr7nAA 5OlO31P8n4XcATZtzRhVV0sDwyF2F2ktuxRO/PG5qWGcP+/IQvUbrzS4LMfWEmOK sCruWYoHsmW9ZxgsIz/44PH7hKhImBfCr/5Mm+QO5061XaSIPgiIYA== =NxFz -END PGP SIGNATURE-
