<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [TriLUG] Sendmail Config Question</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Thanks Jon,</FONT>
</P>
<P><FONT SIZE=2><snip></FONT>
<BR><FONT SIZE=2>You might want to just treat everything as though it were a virtual domain. For that to work, you would have to have a secondary name for sending the foo@haht.com mail into the inside of HAHT.</FONT></P>
<P><FONT SIZE=2>Something like foo@haht.com ==> foo@exchange.haht.com</FONT>
<BR><FONT SIZE=2> foo.bar@haht.com ==> foo@exchange.haht.com</FONT>
</P>
<P><FONT SIZE=2>Then have the MX for the domain exchange.haht.com point to the interior appliance that is doing your spam filtering.</FONT>
<BR><FONT SIZE=2><snip></FONT>
</P>
<P><FONT SIZE=2>I considered this, but it just seemed wrong at the time. I'll reconsider it.</FONT>
</P>
<BR>
<P><FONT SIZE=2><snip></FONT>
<BR><FONT SIZE=2>> 1) relay SMTP traffic for approved domains in relay-domains</FONT>
<BR><FONT SIZE=2>> (relay-domains currently includes haht.com, as well as the</FONT>
<BR><FONT SIZE=2>> other approved domains)</FONT>
</P>
<P><FONT SIZE=2>This is a no-brainer. Put these domains in your /etc/mail/access file with keyword RELAY.</FONT>
<BR><FONT SIZE=2><snip></FONT>
</P>
<P><FONT SIZE=2>I should have said virtual-hosted domains rather than approved domains. We're already using the access file to relay for some domains, and we use the relay-domains for the virtual domains we host. </FONT></P>
<P><FONT SIZE=2><snip></FONT>
<BR><FONT SIZE=2>> 2) resolve aliases for a subset of @haht.com addresses </FONT>
<BR><FONT SIZE=2>> (i.e. jaimiel@haht.com to jlivingston@haht.com)</FONT>
</P>
<P><FONT SIZE=2>Why do you care about this (on this server)? This server is only acting as a relay to move mail into your other server. Shouldn't this be done at the other (exchange) server?</FONT></P>
<P><FONT SIZE=2>The internal server should be able to handle all your aliasing.</FONT>
<BR><FONT SIZE=2><snip></FONT>
</P>
<P><FONT SIZE=2>Unfortunately, the box in question is not a real SMTP server. It's an anti-spam appliance that has absolutely no capabilities to resolve aliases. </FONT></P>
<P><FONT SIZE=2><snip></FONT>
<BR><FONT SIZE=2>If not, then your best bet is to treat it like a virtual host (as pointed out above). Virtual hosts don't need real accounts on the box.</FONT></P>
<P><FONT SIZE=2><snip></FONT>
</P>
<P><FONT SIZE=2>If I were starting from scratch, this is what I would do.</FONT>
<BR><FONT SIZE=2>However, this is our production MX. I don't want to break it, nor do I want to have to rebuild our whole domain structure just to support this one piss-ant device.</FONT></P>
<BR>
<P><FONT SIZE=2>What I really want to know is if there is a way to have this server just resolve aliases for a subset of all the @haht.com address book, but not break the way it currently relays @haht.com messages that it cannot resolve. If the answer is no, then that's that.</FONT></P>
<P><FONT SIZE=2>Jaimie</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Jon Carnes [<A HREF="mailto:jonc@nc.rr.com">mailto:jonc@nc.rr.com</A>] </FONT>
<BR><FONT SIZE=2>Sent: Wednesday, April 23, 2003 8:15 PM</FONT>
<BR><FONT SIZE=2>To: trilug@trilug.org</FONT>
<BR><FONT SIZE=2>Subject: Re: [TriLUG] Sendmail Config Question</FONT>
</P>
<BR>
<P><FONT SIZE=2>You might want to just treat everything as though it were a virtual domain. For that to work, you would have to have a secondary name for sending the foo@haht.com mail into the inside of HAHT.</FONT></P>
<P><FONT SIZE=2>Something like foo@haht.com ==> foo@exchange.haht.com</FONT>
<BR><FONT SIZE=2> foo.bar@haht.com ==> foo@exchange.haht.com</FONT>
</P>
<P><FONT SIZE=2>Then have the MX for the domain exchange.haht.com point to the interior appliance that is doing your spam filtering.</FONT>
</P>
<P><FONT SIZE=2>The main disadvantage is that you need to define all the users here (and their various aliases) - of course you have to do that *somewhere* anyway.</FONT></P>
<BR>
<P><FONT SIZE=2>On Wed, 2003-04-23 at 18:18, Jaimie Livingston wrote:</FONT>
<BR><FONT SIZE=2>> HELO,</FONT>
</P>
<P><FONT SIZE=2>cute ;-)</FONT>
</P>
<P><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I need some Sendmail config help, and I am not finding the available </FONT>
<BR><FONT SIZE=2>> docs all that useful, most likely due to inexperience on my part.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I want to change the configuration of a sendmail server that is the </FONT>
<BR><FONT SIZE=2>> primary MX for haht.com and also provides some virtual hosting for a </FONT>
<BR><FONT SIZE=2>> few other domains. Currently, the server relays mail using the "smart" </FONT>
<BR><FONT SIZE=2>> relay host option in sendmail.cf thru a firewall into another SMTP </FONT>
<BR><FONT SIZE=2>> server. I would like to change the configuration to do the following:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> 1) relay SMTP traffic for approved domains in relay-domains</FONT>
<BR><FONT SIZE=2>> (relay-domains currently includes haht.com, as well as the other </FONT>
<BR><FONT SIZE=2>> approved domains)</FONT>
</P>
<P><FONT SIZE=2>This is a no-brainer. Put these domains in your /etc/mail/access file with keyword RELAY.</FONT>
</P>
<P><FONT SIZE=2>Don't put *any* of them in /etc/mail/local-host-names (unless you want to process them via the virtusertable).</FONT>
</P>
<P><FONT SIZE=2>If you want to by-pass DNS lookups (and using SmartRelay) you can add routes in the /etc/mail/mailertable.</FONT>
</P>
<P><FONT SIZE=2>> 2) resolve aliases for a subset of @haht.com addresses </FONT>
<BR><FONT SIZE=2>> (i.e. jaimiel@haht.com to jlivingston@haht.com)</FONT>
</P>
<P><FONT SIZE=2>Why do you care about this (on this server)? This server is only acting as a relay to move mail into your other server. Shouldn't this be done at the other (exchange) server?</FONT></P>
<P><FONT SIZE=2>The internal server should be able to handle all your aliasing.</FONT>
</P>
<P><FONT SIZE=2>If not, then your best bet is to treat it like a virtual host (as pointed out above). Virtual hosts don't need real accounts on the box.</FONT></P>
<P><FONT SIZE=2>BTW: you can put real accounts on the box and simply use the /bin/nologin shell (yah, you know that...)</FONT>
</P>
<P><FONT SIZE=2>> 3) relay/forward @haht.com messages to another SMTP server</FONT>
<BR><FONT SIZE=2>> (for anti-virus and anti-spam filtering)</FONT>
</P>
<P><FONT SIZE=2>You can use the virtual hosting trick, or setup a route in the mailertable, or use the smartrelay trick.</FONT>
</P>
<P><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The version of Sendmail being used is 8.12.9.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The current configuration does #1 and #3, but does not do #2.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I have experimented a little bit with the aliases file, the </FONT>
<BR><FONT SIZE=2>> virtualuser file, and the Smart relay option in sendmail.cf, but I </FONT>
<BR><FONT SIZE=2>> have not been successful getting all three requirements working.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> #1 seems easy enough.</FONT>
<BR><FONT SIZE=2>> #2 only works if I don't relay using the "Smart" relay host option in </FONT>
<BR><FONT SIZE=2>> sendmail.cf. Unfortunately, messages to @haht.com addresses not found </FONT>
<BR><FONT SIZE=2>> in the aliases file bounce.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> #3 works if I relay using the "Smart" relay host option in </FONT>
<BR><FONT SIZE=2>> sendmail.cf, but Sendmail won't resolve aliases for @haht.com </FONT>
<BR><FONT SIZE=2>> addresses using either the aliases file or the virtualusertable.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> I don't want to create user shell accounts on this server.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Can this be done?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Thanks in advance.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Jaimie</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> P.S. - While I generally appreciate alternatives (postfix, </FONT>
<BR><FONT SIZE=2>> spamassassin, procmail, or <your_choice_here>), my options in this </FONT>
<BR><FONT SIZE=2>> instance are constrained by outside factors. I have to use Sendmail, I </FONT>
<BR><FONT SIZE=2>> have to use the av/as product that is in place, and I don't have the </FONT>
<BR><FONT SIZE=2>> option to rebuild the system. I would appreciate it if evangelising </FONT>
<BR><FONT SIZE=2>> could be kept to a minimum.</FONT>
</P>
<P><FONT SIZE=2>Take care and good Luck - Jon</FONT>
</P>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2>TriLUG mailing list</FONT>
<BR><FONT SIZE=2> <A HREF="http://www.trilug.org/mailman/listinfo/trilug" TARGET="_blank">http://www.trilug.org/mailman/listinfo/trilug</A></FONT>
<BR><FONT SIZE=2>TriLUG Organizational FAQ:</FONT>
<BR><FONT SIZE=2> <A HREF="http://www.trilug.org/faq/TriLUG-faq.html" TARGET="_blank">http://www.trilug.org/faq/TriLUG-faq.html</A></FONT>
</P>
</BODY>
</HTML>