On Wednesday 02 February 2005 12:08, Jeffrey L. Taylor wrote:

Quoting Jeffrey Laramie :

...

Hi All,

I have a problem with yast re-enabling postfix on it's own. This is on a mail server that runs XMail which has it's own local mail delivery daemon. I have disabled postfix since it's redundant and it binds to the port that XMail needs. However sometimes when I make a change using yast it insists on starting postfix behind my back. Any ideas?

What happens if you uninstall Postfix?

That will probably be my next step if I don't find a better answer. I'm reluctant to try that because of the dependencies that other packages may have.

Or "insserv -r /etc/init.d/postfix"?

It ran without complaint. We'll see if the behavior stops. Out of curiosity, is there any important differences between insserv and chkconfig? They seem to do pretty much the same thing. Jeff

The Wednesday 2005-02-02 at 12:43 -0500, Jeffrey Laramie wrote:

It ran without complaint. We'll see if the behavior stops. Out of curiosity, is there any important differences between insserv and chkconfig? They seem to do pretty much the same thing.

The second is an easier to use frontend. It can list all services, for example, and you don't need to provide the path to the service, just the name. -- Cheers, Carlos Robinson

Theo v. Werkhoven wrote:

Wed, 02 Feb 2005, by suse-linux-e@Trans-Star.net:

...

Hi All,

I have a problem with yast re-enabling postfix on it's own. This is on a mail server that runs XMail which has it's own local mail delivery daemon. I have disabled postfix since it's redundant and it binds to the port that XMail needs. However sometimes when I make a change using yast it insists on starting postfix behind my back. Any ideas?

$ rpm -q -provides postfix smtp_daemon postfix = 2.1.5-3

Make sure Xmail (whatever that may be, I thought it was just a CLI MUA) provides smtp_daemon in its init file.

Yes, it's an interesting all-in-one mail handler which replaces sendmail/postfix, fetchmail, and pop3 server daemons. It has it's own smtp engine so it doesn't need anything else. It's secure, well supported, reliable, and scales (at least) to the 20k message/hr range. Major flaws: mediocre documentation (I'm working on some but my time is all tapped out), and it doesn't handle IMAP. I understand that Debian includes it in their distro but there isn't a SuSE package. Here's the home page if anyone is interested: http://www.xmailserver.com/ Jeff Theo

* Jeffrey Laramie; on 02 Feb, 2005 wrote:

Hi All,

I have a problem with yast re-enabling postfix on it's own. This is on a mail server that runs XMail which has it's own local mail delivery daemon. I have disabled postfix since it's redundant and it binds to the port that XMail needs. However sometimes when I make a change using yast it insists on starting postfix behind my back. Any ideas?

If you want to use XMail then the best would be to uninstall postfix. However then you would run into the problem of programs needing smtp_deamon (it is just the cosmetic thing I ould guess as the XMail will do the job) So the second thing to do is install a fake_smtp_daemon rpm. Hence progroms requiring the smtp_deamon will be satisfied and you will be able to use your XMail with no problem at all. You can use the attached spec file to build your fake_smtp.rpm just make sure that it does not conflict with Xmail if it was installed with rpm. All credits goes to Christopher Mahmood (former Mailadmin of SuSE lists) -- Togan Muftuoglu | Unofficial SuSE FAQ Maintainer | Please reply to the list; http://susefaq.sf.net | Please don't put me in TO/CC. Nisi defectum, haud refiecendum

...

Yes, it's an interesting all-in-one mail handler which replaces sendmail/postfix, fetchmail, and pop3 server daemons. It has it's own

[..]

Not my kind of strong Brownian motion producer. I happen to believe in seperate apps all doing their own thing, and within their own (security) context, very well. You only have to look at Exchange to see what can go wrong when a MTA is mated with an agenda, MDA, contact database, authentication database, spell checker, game server, coffee machine and $YOUR_DEITY known what else.

I agree with you up to a point. I think in general it's a bad idea to integrate many different uses into one package. I think Mozilla is another example of that and Firefox was the solution. In this case, however, I see "mail server" as a single use. I think the reason it works well here is that the daemons take a few tuning parameters but otherwise run unobtrusively in the background (as you would expect). All the interaction between the daemons and the rest of the world is handled through "filters" (think modules or plugins) which you have complete control over. I've been on their mailing list for 3 or 4 years and I see requests for new or additional features but I've never seen anyone ask "Can I replace the XMail pop3 server with $POP_SERVER? For all I know you may be able to swap out components the way you prefer, but nobody's ever asked. Jeff