
April 7th, 2004, 03:41 PM
|
 |
Full Access
|
|
Join Date: Jun 2000
Location: London, UK
Posts: 2,019
Time spent in forums: 3 sec
Reputation Power: 11
|
|
Quote: Thanks for the reply.
From what I read, it is not recommended to run Sendmail and qmail - so basically you are suggesting that I replace Sendmail with qmail? |
Yes. I did it yesterday on a fairly busy production server handling a lot of outgoing mail and a handful of incoming mail boxes, and it took a few hours with no downtime at all. It's relatively straightforward; I can give you more in-depth advice and assistance if you need.
Quote:
That sounds like a larger project than I should try to tackle myself, but I can get help with that. It's a pretty busy live application server and I don't want to risk messing something up. |
This is always a risk. Providing you test everything immediately after the qmail upgrade, you will be OK, since you can just turn it off and bring sendmail back up until the problem is fixed. The way I handled yesterday's migration was to run qmail on an alternate port (say, 26) while it was in test mode, and manually deliver an email via telnet to port 26, and check that it arrived in the right mail box. This won't mess up any existing incoming mail, as that all comes in on port 25.
Quote: |
I was under the impression that I could do what I want to do using procmail along with sendmail, which seems a lot simpler. I'm curious as to why you recommend qmail? Can I NOT do what I want to do using procmail?? |
You probably can, but it is probably more hassle (though it might not sound like it!) to just replace the entire thing with qmail, which has this feature built in.
Sendmail and procmail are two complex pieces of software which have to be integrated together (Sendmail is also buggy and extremely complicated). qmail is one simple piece of software. You make the choice 
|