After browsing by all 142 of the posts at mail-archive.com (that would be 135 or so hits on Sandy's .sig!) that include "exchange2aliases", I've spotted the missing link.
I noted the absence of it myself while trying to provide all the diagnostics; Sandy instructed in his inaugral post: "All, I've posted exchange2aliases, a VBScript that helps automate the cumbersome task of rejecting unknown users for remote domains. The script is designed specifically for those running IMail MXs, with or without Declude, in front of Exchange mailbox servers. In order to use the script, you first change your remote domains from classical store-and-forward domains with no local presence (save a HOSTS entry) to IMail virtual hosts with no users, a simple change. You'd then create a new recipient policy for your Exchange organization that allows users to receive mail at, for example, exchange.example.com in addition to their primary address at example.com (many Exchange setups already have such a policy in place because they use a .local AD domain). Make sure that IMail sees the MX for exchange.example.com as the Exchange server's internal IP, or hard-code the mailroute in HOSTS if you want. When you then run Exchange2aliases, either scheduled or ad hoc, it will scan all of the Exchange addresses for AD and SMTP domains you specify and create corresponding IMail aliases for each--thus allowing for envelope rejection on the IMail box. By default, exchange2aliases clears and replaces the entire _aliases table in IMail every time you run it, which would typically be the preferred behavior, but this behavior may be disabled using a command-line switch. The exchange2aliases command-line options are visible by running 'cscript exchange2aliases.vbs' after your download. Please post support questions as [OT] to the IMail or Declude forums to create a public archive. Regards, Sandy" So, the extra Exchange recipient policy is what I'm missing. Also, I introduced the alias loop because after failing to get it to work, I cribbed the idea of the alias from the recent ldap2alias discussion. Andrew 8( -----Original Message----- From: Colbeck, Andrew Sent: Saturday, November 13, 2004 8:05 PM To: '[EMAIL PROTECTED]' 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. --- [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.
