On 8 Jan 2001, at 12:51, John R Levine wrote:
> > Our ms-exchange server has a forwarding address [EMAIL PROTECTED] -->
> > [EMAIL PROTECTED]
> > This is done for the convenience of our internal users.
> > An unwanted side effect is that requests sent to [EMAIL PROTECTED] from the
> > internet are processed in a simmilar manner as the requests from our
> > intranet.
>
> > According to our Exchange people there is no solution in Exchange available
> > for this problem.
>
> He's probably right, you pay all that money and it still doesn't do what
> you want.
We ran into another one like that: apparently it is very hard in Exchange
to set up a domain and forward all email for the domain to a default
mailbox... go figure...
> Fortunately, if your Majordomo list runs on a Unix or Linux machine, you
> can easily solve your problem with the popular freeware procmail package.
> (Most Linux and BSD systems already have it installed.) Procmail can
> easily check the From: line to see if the address matches @.*.klm.nl
> (i.e., it's a KLM address) and if so pass it to Majordomo, otherwise use
> formail, another part of the procmail package, to send back a fixed
> response.
This is probably OK, but I'd probably use the last [most recent] received-
by line. I find 'From' lines are a bit too variable and by and large I
try to avoid using them for anything. If you use the last received-by
line that your server stampted on the mesasge, you can use the source-IP
as a pretty unequivocal indication of whether the message is internal or
not...
/bernie\
--
Bernie Cosell Fantasy Farm Fibers
mailto:[EMAIL PROTECTED] Pearisburg, VA
--> Too many people, too few sheep <--
