PDL Messages Looping

[code0]

I'm doing a phased migration from Exchange 5.5 to Scalix 11GA and it seems that PDL messages are looping when it's sent FROM a Scalix account. If it is sent from an Exchange account, it works normally. I see errors about the looping in my Sendmail logs, but that is it. The other odd thing is that the Sendmail logs show only the loops for Scalix users on the PDL - it never even gets to the Exchange server. Any thoughts? I've attached logs below..

BTW, Scalix server is set up for scalix.domain.com and the Exchange server is mail.domain.com.


/var/log/mail
-------------
Feb 7 10:13:27 scalix sendmail[5404]: l17GDQeL005404: from=<jbailey@domain.com>, size=7382, class=0, nrcpts=1, msgid=<H0000067000049f5.1170864766.scalix.domain.com@MHS>, proto=ESMTP, daemon=Daemon0, relay=localhost [127.0.0.1]
Feb 7 10:13:29 scalix sendmail[5410]: l17GDQeL005404: to=<IS@domain.com>, delay=00:00:02, xdelay=00:00:01, mailer=scalix_mime, pri=127382, relay=scalix, dsn=2.0.0, stat=Sent (Ok)
Feb 7 10:28:43 scalix sendmail[5619]: l17GDYiB005456: SYSERR(root): Too many hops 26 (25 max): from <jbailey@domain.com> via localhost, to <IS@domain.com>
Feb 7 10:28:43 scalix sendmail[5619]: l17GDYiB005456: l17GShVM005619: DSN: Too many hops 26 (25 max): from <jbailey@domain.com> via localhost, to <IS@domain.com>

scalix:~ # omsearch -e S=is -m @ALL-ATTR@
-----------------------------------------
COMMON-NAME=IS cn-Recipients/OU1=exchange/S=IS/ALIAS=IS/INTERNET-ADDR=IS@domain.com/CN=Information Services/LDAP-OBJECT-CLASS=distributionList=mhsDistributionList=scalixDistributionList=top=ldapsync-migration/GLOBAL-UNIQUE-ID=cn\=IS,cn\=Recipients,ou\=MCIS,o\=Marshall County/FOREIGN-ADDR=cn\=IS,cn\=Recipients,ou\=MCIS,o\=Marshall County/HOST-FQDN=scalix.domain.com/LOCAL-UNIQUE-ID=364/ENTRY-TYPE=4/DL-POLICY=0/IA-FORMAL=IS@domain.com/S-SDX=I200/DBV-ID=33554516

scalix:~ # omshowlog -l 9
-------------------------
Yields nothing useful

[gordon]

Exact same problem here. Code0, looks like you and I are running in to many of the same problems during our phased migration and finding solutions has been somewhat troublesome. Generally this forum is a wealth of information but these migration issues are making me tear my hair out.

[code0]

I can agree with that... I also had a non-scalix issue earlier.. Apparently Exchange just decided to remove the alternate recipient information for one of my users...

[gordon]

I really want to love Scalix and migrate to the Small Business version but before that can happen I must have a successful co-existence with Exchange 5.5. The product needs to be throughly evaluated and tested by myself and the users before we can make the leap. This PDL message loop is stopping me dead in my tracks and if I can't get it resolved then I will have to ditch Scalix. I just wish the official Scalix support reps would change their "View Exchange Migration Questions" filter from 0 to 1.

Here is the bounce back I get when trying to send an email to a PDL that is supposed to forward to an Exchange Distribution List:

The original message was received at Mon, 12 Feb 2007 11:00:27 -0500
from localhost.localdomain [127.0.0.1]

----- The following addresses had permanent fatal errors -----
<mis@mydomain.com>
(reason: 554 5.4.6 Too many hops)

----- Transcript of session follows -----
554 5.4.6 Too many hops 26 (25 max): from <monitorweb@mydomain.com> via localhost, to <mis@mydomain.com>

[code0]

FYI... Opened a support request and got the following response:

(slightly paraphrased)

The documentation isn't really clear on this, but the proper way to make this work, is to simply create a user in Scalix with the name of the mailing list (Deleting the entry that was synced) and then use sxaa to create a redirect rule to redirect mail to the Distribution List on Exchange. They said you can take it one step further and create a PDL in Scalix with the same name as the Distribution List in Exchange and make the one user with the redirect rule a member of that list.

Pretty much, I've just used omdelent to delete the "locked" PDL that omldapsync pulls in and added a user with "DL-" as the prefix forwarding to the Exchange server. I could have set up PDLs to forward to these users, but I decided not to recreate the PDLs until we are finished with migration. Here's an example of what needs to be done for a DL:

Code: Select all

omdelent -e S=IS
omaddu -n 'DL-Information Services/scalix/IA="DL-Information Services" <IS@scalix.domain.com>' -p pdlpassword --class limited
sxaa --user "DL-Information Services" --redirect IS@domain.com


[gordon]

code0, you are the man. That solution is working beautifully for me. Now I can actually roll this out to some of my users and let them stress test it.

[bguerreiro]

HI all.
Has anyone found another solution?
I have 200+ Distribution Lists, and having to recreate all of them...

TIA.
Bruno Guerreiro