File: 5.html

package info (click to toggle)
lg-issue38 2-1
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 2,136 kB
  • ctags: 147
  • sloc: makefile: 34; sh: 34
file content (253 lines) | stat: -rw-r--r-- 10,126 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
<!--startcut ======================================================= -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<META NAME="generator" CONTENT="lgazmail v1.1I.e">
<TITLE>The Answer Guy 38: &quot;Integrating&quot; Linux/sendmail with MS Exchange</TITLE>
</HEAD><BODY BGCOLOR="#FFFFFF" TEXT="#000000"
	LINK="#3366FF" VLINK="#A000A0">
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<H4>"The Linux Gazette...<I>making Linux just a little more fun!</I>"</H4>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<center>
<H1><A NAME="answer">
	<img src="../../gx/dennis/qbubble.gif" alt="(?)" 
		border="0" align="middle">
	<font color="#B03060">The Answer Guy</font>
	<img src="../../gx/dennis/bbubble.gif" alt="(!)" 
		border="0" align="middle">
</A></H1> 
<BR>
<H4>By James T. Dennis,
	<a href="mailto:linux-questions-only@ssc.com">linux-questions-only@ssc.com</a><BR>
	Starshine Technical Services,
	<A HREF="http://www.starshine.org/">http://www.starshine.org/</A> 
</H4>
</center>

<p><hr><p>
<!--  endcut ======================================================= -->
<!-- begin 5 -->
<H3 align="left"><img src="../../gx/dennis/qbubble.gif" 
	height="50" width="60" alt="(?) " border="0"
	>&quot;Integrating&quot; Linux/sendmail with MS Exchange</H3>


<p><strong>From Kevin Harrison  on Fri, 05 Feb 1999  
</strong></p>
<!-- ::
&quot;Integrating&quot; Linux/sendmail with MS Exchange
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:: -->
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
jim;
</STRONG></P>
<P><STRONG>
Kia Ora from Auckland , New Zealand
</STRONG></P>
<P><STRONG>
I have inherited a box with Linux installed on it and we wish to integrate
the linux email (using <tt>sendmail</tt>) with the dreaded 
ms-exchange which runs
on NT....the main reason is so that LAN clients can receive email
notifications from jobs that will run on the linux box.
</STRONG></P>
<P><STRONG>
Are there any quick guides out there on this procedure..
<br>thanks mate
<br>Kevin Harrison, Downunder
</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" ALT="(!)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
There should be no special work in this regard.
</BLOCKQUOTE>
<BLOCKQUOTE>
Let's assume that your domain was "<tt>downunder.nz</tt>"
and that you MS Exchange server is configured as
the primary "<tt>MX</tt>" host for that domain (meaning that
all outside mail to "foo@downunder.nz" gets directed
to it).  Let's say your Linux system is named <tt>penguin</tt>.
So you can create an <tt>MX</tt> record for <tt>penguin.downunder.nz</tt>
and mail to foo@penguin.downunder.nz will go to the
Linux system rather than the MS Exchange server (which
we'll call "<tt>msnail</tt>" --- &lt;g&gt;for "MS Nt mAIL"&lt;/g&gt
<IMG SRC="../../gx/dennis/smily.gif" ALT=";)" 
		height="24" width="20" align="middle">.
</BLOCKQUOTE>
<BLOCKQUOTE>
Now mail coming <EM>from</EM> penguin, to <A HREF="mailto:foo@downunder.nz"
	>foo@downunder.nz</A> will
go automatically to <tt>msnail.downunder.nz</tt> where MS Exchange
will mangle it.
</BLOCKQUOTE>
<BLOCKQUOTE>
A better approach is to point your primary <tt>MX</tt> record to
<tt>penguin</tt>.  Penguin can then have a large aliases file for all
of the users and accounts that exist in your domain ---
directing the mail to the more specific hosts on which those
users get their mail.  Thus all the MS Outlook and MS Mail
users could get their mail from <tt>msnail</tt>, while your Linux
users can get theirs directly from <tt>penguin</tt> (either via
POP/IMAP or by logging in to their shell account and reading
mail with '<tt>elm</tt>', '<tt>pine</tt>', '<tt>mutt</tt>', 
or any mailer they like.
You heavy volume mail users who are using MS Outlook can
still get their mail directly from <tt>penguin</tt> (via POP).
</BLOCKQUOTE>
<BLOCKQUOTE>
The main advantages to this approach:
</BLOCKQUOTE>
<BLOCKQUOTE><BlockQuote>
Your Linux system probably has a much higher
stability and capacity than NT on comparable
hardware.  So your high volume mail users
won't be bringing down the system for everyone
else.  (It's very hard to flood a modern Linux
system with just e-mail).
</BlockQuote></BLOCKQUOTE>
<BLOCKQUOTE>
You have simple remote configuration and management
of your mail routing (telnet in and edit your
<TT>/etc/aliases</TT> file, then run '<tt>newaliases</tt>').
</BLOCKQUOTE>
<BLOCKQUOTE>
You can easily create "magic accounts" like
"info@downunder.nz" which feed into autoresponder
scripts (presumably in the simple procmail
scripting language).
</BLOCKQUOTE>
<BLOCKQUOTE>
You have no licensing constraints, costs or
restrictions.   If you want to add a hundred
new e-mail users, or a thousand --- you just
create the accounts on penguin and have your
account holders point their favorite mail readers
(Netscape Communicator, Pegasus, Eudora, even
MS Outlook) at it.
</BLOCKQUOTE>
<BLOCKQUOTE>
You have relatively easy and <EM>free</EM> access to
a number of evolving anti-spam systems (such as
the RBL (real-time blackhole list).  I haven't
heard of any patches or modules for MS Exchange
to enable RBL support --- and I suspect that
MS would only provide such services on a fee-driven
subscription basis (rather than as a community
service, like Paul Vixie is doing with the RBL).
</BLOCKQUOTE>
<BLOCKQUOTE>
The difference between these two approaches:
</BLOCKQUOTE>
<BLOCKQUOTE><BlockQuote>
In the first case we set up a different <tt>MX</tt> record
for <tt>penguin</tt>.  Anyone who needed to send mail <EM>to</EM> an
account on that system needed to use the full name:
	foo@penguin.downunder.nz.  Mail to 
	foo@downunder.nz
would go to the <tt>msnail</tt> host.  You might have some
options for autoforwarding from the MS box --- but
you'd have to talk to your MS wizards on how to do
it.  It probably involves filling in some GUI dialog
somewhere (requiring you to work at its console) and
its probably subject to MS pricing and licensing ---
i.e. you're paying extra for each account.
</BlockQuote></BLOCKQUOTE>
<BLOCKQUOTE>
In the second case we reverse that:  Mail defaults
to landing on <tt>penguin</tt>.  The further routing from
there is trivial (since <tt>sendmail</tt>, <tt>aliases</tt> and
<tt>.forward</tt> files have been used by the majority of
the Internet for over 20 years).
</BLOCKQUOTE>
<BLOCKQUOTE>
In summary:  MS Exchange can recieve SMTP (Internet mail)
so there is no trick to "integrating" them with '<tt>sendmail</tt>'
'<tt>qmail</tt>' or other Internet MTAs (mail transport agents).
I've heard some people complain about MS Exchange's
behavior (generating mail with "ugly" <tt>WINMAIL.DAT</tt>
attachments that the rest of the net doesn't care for),
compliance (subtle ways that it doesn't conform to the
RFCs and implementation conventions of other systems ---
but these might be argued as a "failure to be bug
compatible" --- so those are moot), performance (more than
100 "normal" e-mail accounts, or 50 "heavy users" will
probably require considerable hardware under NT --- while
an old 386 or 486 can handle those loads under Linux), and
robustness (my household POP server has been up for over
a 125 days; I have no idea why I rebooted it 4 months ago
but I know it wasn't for any real problem --- maybe it was
when I was rewiring and cleaning out the server closet).
</BLOCKQUOTE>
<BLOCKQUOTE>
So, what have you tried so far?  What sorts of problems
are you encountering?
</BLOCKQUOTE>
<!-- sig -->

<!-- end 5 -->
<!--startcut ======================================================= -->
<P> <hr> <P>
<H5 align="center"><a href="http://www.linuxgazette.com/copying.html"
	>Copyright &copy;</a> 1999, James T. Dennis 
<BR>Published in <I>The Linux Gazette</I> Issue 38 March 1999</H5>
<P> <hr> <P>
<!-- begin tagnav ::::::::::::::::::::::::::::::::::::::::::::::::::-->
<TABLE WIDTH="96%"><TR VALIGN="center" ALIGN="center">
<TD ROWSPAN="3" COLSPAN="4" WIDTH="24%"><A HREF="../lg_answer38.html"
	><IMG SRC="../../gx/dennis/answernew.gif"
              ALT="[ Answer Guy Index ]"></A></td>
  <TD WIDTH="6%"><A HREF="1.html">1</A></TD>
  <TD WIDTH="6%"><A HREF="2.html">2</A></TD>
  <TD WIDTH="6%"><A HREF="3.html">3</A></TD>
  <TD WIDTH="6%"><A HREF="4.html">4</A></TD>
  <TD WIDTH="6%"><A HREF="5.html">5</A></TD>
  <TD WIDTH="6%"><A HREF="6.html">6</A></TD>
  <TD WIDTH="6%"><A HREF="7.html">7</A></TD>
  <TD WIDTH="6%"><A HREF="8.html">8</A></TD>
  <TD WIDTH="6%"><A HREF="9.html">9</A></TD>
  <TD WIDTH="6%"><A HREF="10.html">10</A></TD>
  <TD WIDTH="6%"><A HREF="11.html">11</A></TD>
</TR><TR VALIGN="center" ALIGN="center">
  <TD><A HREF="12.html">12</A></TD>
  <TD>&nbsp;</TD>
  <TD><A HREF="14.html">14</A></TD>
  <TD>&nbsp;</TD>
  <TD><A HREF="16.html">16</A></TD>
  <TD><A HREF="17.html">17</A></TD>
  <TD><A HREF="18.html">18</A></TD>
  <TD><A HREF="19.html">19</A></TD>
  <TD>&nbsp;</TD>
  <TD><A HREF="21.html">21</A></TD>
  <TD><A HREF="22.html">22</A></TD>
</TR><TR VALIGN="center" ALIGN="center">
  <TD><A HREF="23.html">23</A></TD>
  <TD><A HREF="24.html">24</A></TD>
  <TD>&nbsp;</TD>
  <TD><A HREF="26.html">26</A></TD>
  <TD>&nbsp;</TD>
  <TD><A HREF="28.html">28</A></TD>
  <TD><A HREF="29.html">29</A></TD>
  <TD><A HREF="30.html">30</A></TD>
  <TD><A HREF="31.html">31</A></TD>
  <TD><A HREF="32.html">32</A></TD>
  <TD>&nbsp;</TD>
</TR></TABLE>
<!-- end tagnav ::::::::::::::::::::::::::::::::::::::::::::::::::::-->
<P> <hr> <P>
<!-- begin lgnav ::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<A HREF="../index.html"
	><IMG SRC="../../gx/indexnew.gif" ALT="[ Table Of Contents ]"></A>
<A HREF="../../index.html"
	><IMG SRC="../../gx/homenew.gif" ALT="[ Front Page ]"></A>
<A HREF="../lg_bytes38.html"
	><IMG SRC="../../gx/back2.gif" ALT="[ Previous Section ]"></A>
<A HREF="../lg_tips38.html"
	><IMG SRC="../../gx/fwd.gif" ALT="[ Next Section ]"></A>
<!-- end lgnav ::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
</BODY></HTML>
<!--endcut ========================================================= -->