Andrew,
Is the only lines you altered in Sandy's script were:
cscript exchange2aliases.vbs storeforward.mydomain.com
LDAP://10.192.0.1/cn=users,dc=bentall,dc=local mydomain.com mydomain.com
Going for a test ride tomorrow.
Thanks for the aid,
Keith
-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Colbeck, Andrew
Sent: Sat 11/13/2004 11:04 PM
To: '[EMAIL PROTECTED]'
Cc:
Subject: [Declude.JunkMail] [OT] exchange2aliases for dummies
Sandy, I'm having problems in getting this working on a test machine.
I'm
missing some obvious step...
Recap:
My production environment is such that I run IMail+Declude as my
gateway, in
front of an Exchange 2000 environment, so I'm a good candidate for using
your exchange2aliases script. We gateway a half dozen domains through
the
IMail gateway, and some of those have a relatively small userbase, so
I'll
start with testing one of those.
In the production environment, the SMTP addresses for a user are
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] etc. and not in
the
Active Directory, i.e. not something like [EMAIL PROTECTED]
I installed a fresh copy of IMail v8.12 on the test machine.
For the "Official Host Name" I chose the same as my production box,
mail.bentall.com and it is listening on the local, non-routeable IP,
which
is the only IP on the test machine.
I then added a host, gave it an "Official Host Name" of
"storeforward.mydomain.com" and a "Host Alias" of "mydomain.com" and
set it
as a virtual host so that I wouldn't have to give it a unique IP.
Then I added an entry to the test machine's "hosts." file so that it
knew
that 192.168.116.100 is the IP for the internal Exchange 2000 that is
our
current gateway, e.g. "192.168.116.100 mydomain.com"
Then I set the log format to SYDMMDD.txt and turn on the Debug and
Verbose
options.
Then I ran exchange2alias like so:
cscript exchange2aliases.vbs storeforward.mydomain.com
LDAP://10.192.0.1/cn=users,dc=bentall,dc=local mydomain.com mydomain.com
I could then view all the lovely aliases in IMail.
I then used a command line utility, postie, to send a simple message to
that
test IMail server, with a bogus to: address:
postie -host:192.168.116.25 -to:[EMAIL PROTECTED]
-from:[EMAIL PROTECTED] -s:"This is the subject" -msg:"This is the
body."
-v:9
The message is refused. Joy!
I then used a command line utility, postie, to send a simple message to
that
test IMail server, with a valid to: address:
postie -host:192.168.116.25 -to:[EMAIL PROTECTED]
-from:[EMAIL PROTECTED] -s:"This is the subject" -msg:"This is the
body."
-v:9
The message is accepted (joy!), and the IMail log shows that it is
queued,
but also this:
11:13 19:24 SMTP-(0000000000000000) Info - Adding Queue file
C:\IMail\spool\Qcff500b70dc64580.SMD
11:13 19:24 SMTP-(cff500b70dc64580) processing
C:\IMail\spool\Qcff500b70dc64580.SMD
11:13 19:24 SMTP-(cff500b70dc64580) ERR alias loop in [EMAIL PROTECTED]
11:13 19:24 SMTP-(cff500b70dc64580) finished
C:\IMail\spool\Qcff500b70dc64580.SMD status=1
that there is an alias loop (boo!) and the message evaporates from the
spool
folder.
I've spent a *lot* of time on this now with a multitude of
combinations, and
it's just not working. I've tried a real host IP, I've tried adding the
"host alias" to the primary OHN that I had created for our default
domain,
and ...
What am I missing!?
Andrew 8)
---
[This E-mail was scanned for viruses by Declude Virus
(http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
<<winmail.dat>>
