[TriLUG] Sendmail Config Question

[Jon Carnes]

You could definitely do this with some sort of Milter, but you would
probably have to build your own.

There are other ways of modifying aliases, but I think they would all be
by-passed by using a Smart Relay (since the mail would not be for local
delivery).

Hmmm... This might be of some help to you:
  http://www.sendmail.org/m4/userdb.html

I think in particular, you want to look at the FEATURE(notsticky)
Isn't Sendmail fun?

Jon

On Thu, 2003-04-24 at 11:11, Jaimie Livingston wrote:
> Thanks Jon,
> 
> <snip>
> 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 at haht.com mail into the inside of HAHT.
> 
> Something like foo at haht.com ==> foo at exchange.haht.com
>                foo.bar at haht.com ==> foo at exchange.haht.com
> 
> Then have the MX for the domain exchange.haht.com point to the
> interior appliance that is doing your spam filtering.
> <snip>
> 
> I considered this, but it just seemed wrong at the time. I'll
> reconsider it.
> 
> 
> <snip>
> > 1) relay SMTP traffic for approved domains in relay-domains
> >    (relay-domains currently includes haht.com, as well as the
> >    other approved domains)
> 
> This is a no-brainer.  Put these domains in your /etc/mail/access file
> with keyword RELAY.
> <snip>
> 
> 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.
> 
> <snip>
> > 2) resolve aliases for a subset of @haht.com addresses 
> >    (i.e. jaimiel at haht.com to jlivingston at haht.com)
> 
> 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?
> 
> The internal server should be able to handle all your aliasing.
> <snip>
> 
> 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. 
> 
> <snip>
> 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.
> 
> <snip>
> 
> If I were starting from scratch, this is what I would do.
> 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.
> 
> 
> 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.
> 
> Jaimie