From: Yuri Csapo <ycsapo@exchange.mines.edu>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: sendmail blues
Date: Fri, 6 Nov 2009 14:54:26 -0700 [thread overview]
Message-ID: <4AF49B12.8050405@exchange.mines.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]
Hi all, I've an unusual (for me) problem:
- I'm running RHEL release 3 (taroon). I know, I know. Nothing I can do - it's the application
vendor's requirement.
- This application also MUST have some Sun MTA installed and running, even if we don't use it - and
we don't. This MTA sits on ports SMTP, SSMTP, IMAP and POP, HTTP and HTTPS and provides services to
the application only, NOT TO THE OS.
- We still need to be able to mail admin stuff such as logwatch and others. RedHat comes with
sendmail and we are trying to keep this box as close as possible to default configuration.
- The sendmail queue runner by itself is not enough because I can't find a way to make it expand
aliases - root messages end up going to root@mines.edu, which is not where I want them to go.
- Sendmail won't start because the silly Sun app is squatting on port 25.
- If I use DaemonPortOptions to tell sendmail to listen on a different port then I get sendmail to
start but I haven't found a way to make the queue runner send to that port on localhost. The runner
ends up connecting to port 25, which is the Sun MTA, who proceeds to deny the connection.
Does anybody know how to do one of the following:
- make the sendmail queue runner expand aliases
- make the queue runner send to a port other than 25
- make sendmail behave like in the good old days and forgo the need for the queue runner
Some options that have crossed my mind but which I'm trying to avoid:
- redirect port 25 using iptables
- modify sendmail's source and recompile (ugh)
- give up on sendmail and install exim or postfix or something that can be understood by someone who
hasn't read the Bat Book in the last 6 years and who is not particularly inclined to read it again.
Any other ideas?
TIA
Yuri
--
Yuri Csapo
Academic Computing & Networking
Colorado School of Mines
CT-256
Phone: (303) 273-3503
Fax: (303) 273-3475
Email: ycsapo@mines.edu
Please use the following link to open a service request:
http://helpdesk.mines.edu
===========================================
With a PC, I always felt limited
by the software available.
On Unix, I am limited only by my knowledge.
--Peter J. Schoenster
[-- Attachment #2: ycsapo.vcf --]
[-- Type: text/x-vcard, Size: 200 bytes --]
begin:vcard
fn:Yuri Csapo
n:Csapo;Yuri
org:Colorado School of Mines;CCIT
email;internet:ycsapo@mines.edu
title:System Administrator
tel;work:(303) 273-3503
x-mozilla-html:FALSE
version:2.1
end:vcard
next reply other threads:[~2009-11-06 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 21:54 Yuri Csapo [this message]
2009-11-06 22:48 ` sendmail blues Gerardo Juarez-Mondragon
2009-11-06 23:51 ` Yuri Csapo
2009-11-06 23:51 ` Max Gribov
2009-11-06 23:53 ` Yuri Csapo
2009-11-07 0:08 ` Max Gribov
2009-11-07 11:10 ` Glynn Clements
2009-11-07 12:49 ` Yuri Csapo
2009-11-08 7:13 ` Glynn Clements
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF49B12.8050405@exchange.mines.edu \
--to=ycsapo@exchange.mines.edu \
--cc=linux-admin@vger.kernel.org \
--cc=ycsapo@mines.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).