Re: Setting up Exchange 2003 to work with a SendMail gateway

Sorry, you want to have sendmail send all mail to Exchange?
If so, you just need to configure Sendmail to use Exchange as a smarthost
else configure all of the aliases appropriately.

I'd opt for the aliases as it's easier to manage. Just because you don't do
them one at a time it's not a big deal but it is the lowest impact in my
opinion because you're changing a feature normally associated with sendmail
administration vs. changing the routing which is done far less frequently.

You can find a lot of answers to sendmail questions at www.sendmail.org if
you need to.



"Brantley Allen" <pounds@xxxxxxxxxxxxxx> wrote in message
news:A136B18E-4B15-43FE-86E7-05E28DD6014B@xxxxxxxxxxxxxxxx
>
>
> "Al Mulnick" wrote:
>
>> Probably the hardest part will be reconfiguring the user agents to pick
>> up
>> mail only at the Exchange server. You'll also need to figure out what is
>> acceptable to you regarding picking up mail while external to your
>> network
>> (currently they get it via Sendmail POP/IMAP I assume) although RPC/HTTP
>> is
>> a nice feature to take advantage of.
>>
>> As for mail routing that's pretty easy. You want a smart relay
>> configuration.
>> Exchange: Add a SMTP address to your users (recipient policy + any
>> addresses
>> that are unique will have to be manually dealt with) for domain.com and
>> apply it to all users. Make it a primary address type and let Exchange
>> know
>> your Exchange server is authoritative for that domain (it's a checkbox.
>> See
>> the help files for more information). Don't remove the int.domain.com
>> but
>> just make it a secondary address.
>>
>> Inbound: You'll need to tell Sendmail (which version?) to deliver the
>> mail
>> it receives to your Exchange server vs. local mailboxes. Depending on
>> version and your exact requirements, you may choose different ways of
>> doing
>> this. You may want to just forward all mail that Sendmail receives that
>> is
>> destined for your domain to your Exchange server. I don't see a reason
>> to
>> rewrite any addresses based on your information, but that's possible.
>>
>
>
>
> This is what information I can't seem to find anywhere. Where can I find
> information on how to do this?
>
>
>
>
>
>
>> Outbound: route all mail from Exchange to your sendmail servers for
>> delivery. In Exchange, you'll create a connector and configure smart
>> host
>> delivery. There are KB articles on this as well as information in the
>> help
>> files.
>>
>> Is that what you're after? Or did I miss something?
>>
>>
>>
>> "Alexey Aksyonenko" <AlexeyAksyonenko@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>> message news:D838F153-D943-4CCA-A8C7-D4BF2B9F8B2F@xxxxxxxxxxxxxxxx
>> > Actually, maybe I am going the wrong way about explaining what I need.
>> > :-)
>> > What I have now are 2 SendMail servers. Each user has 2 mailboxes -
>> > one
>> > per
>> > server. One server is internal, with no access to the outside world.
>> > The
>> > other is external, and does not see inside the network. Everyone has 2
>> > e-mail addresses - user@xxxxxxxxxxxxxx and user@xxxxxxxxxx,
>> > respectively.
>> > This is a pain in the rear. I want to kill 2 birds with one stone. I
>> > want
>> > the benefits of an Exchange server internally. I also want to have
>> > only
>> > one
>> > mailbox per user - as far as the user is concerned - user@xxxxxxxxxxx
>> > I
>> > want
>> > that box to be on Exchange, and all e-mails sent from one network user
>> > to
>> > another are to remain on exchange. All e-mail to/from the outside
>> > world
>> > is
>> > to be routed through the SendMail server, but still with the same
>> > mailbox
>> > name - user@xxxxxxxxxxx My users already have network logins, of
>> > course,
>> > with the active directory domain of "int.domain.com". What I do NOT
>> > want
>> > to
>> > do is have to re-structure my entire network to accomodate this. I
>> > want
>> > the
>> > users to still log into the same domain when they log into the network,
>> > but
>> > log into maybe a "virtual" domain within Exchange. How do I set this
>> > up?
>> > --
>> > Alexey Aksyonenko
>> > Director of IT (MCP, MCDBA)
>> > COA Network
>> > www.coanetwork.com
>> >
>> >
>> > "Lanwench [MVP - Exchange]" wrote:
>> >
>> >>
>> >>
>> >> In news:40CFB0DF-8226-47DD-BFDD-5C9FBD25261C@xxxxxxxxxxxxx,
>> >> Alexey Aksyonenko <AlexeyAksyonenko@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
>> >> > But if I specify * for address space, wouldn't that forward ALL the
>> >> > correspondence to SendMail, including the intra-domain messages that
>> >> > I want to keep on Exchange?
>> >> >
>> >>
>> >> No, if you put * in the address space in the connector, only
>> >> Internet-bound
>> >> mail will go out that way....
>> >> >
>> >> >>
>> >> >>
>> >> >> In news:628032CA-110C-48D6-AA14-B59F6A105517@xxxxxxxxxxxxx,
>> >> >> Alexey Aksyonenko <AlexeyAksyonenko@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >> >> typed:
>> >> >>> Rather new to Exchange administration. I want to set up an
>> >> >>> Exchange
>> >> >>> 2003 server internally, with a Linux SendMail server as a gateway
>> >> >>> to
>> >> >>> the outside wold. Basically, I want all the e-mail that is being
>> >> >>> sent within my domain to remain on Exchange, but all mail going
>> >> >>> out
>> >> >>> to outside world to be routed to the SendMail, and also all
>> >> >>> incoming
>> >> >>> mail will be forwarded from SendMail to Exchange. There are a
>> >> >>> number of posts on this in Google Groups, but they mostly deal
>> >> >>> with
>> >> >>> the SendMail configuration, whereas I need to know the Exchange
>> >> >>> end
>> >> >>> of it. Can anyone help? (My Exchange server is already installed
>> >> >>> and operational by itself.)
>> >> >>
>> >> >> Set up an SMTP connector for outbound internet mail & specify the
>> >> >> sendmail server as the smarthost - use * as the address space.
>> >>
>> >>
>> >>
>>
>>
>>


.

Relevant Pages

  • Re: Configuring Sendmail under Solaris 9 to relay
    ... Sendmail passes the mail to a Microsoft Exchange Server, ... to relay the mail. ...
    (comp.unix.solaris)
  • Re: store problems
    ... grabbing the DNS of our ISP and NOT the exchange server, ... > prompt typ IPCONFIG /ALL and review your Network settings to the DNS Server ... YES I am refering to Outlook on local network. ...
    (microsoft.public.exchange.admin)
  • Re: drop bad email addresses
    ... I have an exchange server sitting behind a sendmail server running ... Currently all mail hits the mailscanner, ... I can change the output of the script, but can sendmail do anything ...
    (comp.mail.sendmail)
  • Exchange Active Sync behind ISA 2004 SP1 wont work
    ... over the GPRS network back to our Exchange server. ... ISA 2004 problem? ... Here are the rules in ISA for the Exchange server. ...
    (microsoft.public.isa)
  • Re: Exchange Server Reset question
    ... The network is switched, VLAN's, core switch routing module at the center ... towards performing something similar on the Exchange server in the event ... with AD as some computer accounts do? ...
    (microsoft.public.exchange.admin)