Message forward rule not working

[Tman45]

We are trying to send our voice messages to email. We have the FQDNs setup properly and the rule enabled. Desktop messaging alerts me to receiving a message but I get this error in CallPilot for the email forward:
Wednesday, February 20, 2013 1:55:45 PM 54825 Major IMA Send [IMA Send Thread] All recipients are invalid or do not exist on the remote site: domain. com
I am not sure why there is a 'space' as we have had our vendor check every config area and we can't find why this would have a space. In the log below I can't find any extra space - I did scrub the server and domain and IP info.
Thanks in advance for any help. We have Lotus Notes which you can tell in the 8th line as it says DOMINO. It appears that it establishes connection but can't find the mailbox.

Here is our log:
0201113-16:44:02 TID:04436 sock:-001 SEND MsgType: Normal
0201113-16:44:02 TID:05508 sock:-001 SEND Remote host=domain.com, Local domain=domain.com
0201113-16:44:02 TID:05508 sock:-001 SEND MIME file=D:\nortel\smtp\outgoing\.148612.19775_wav.mim
0201113-16:44:02 TID:05508 sock:-001 SEND Info file=D:\nortel\smtp\outgoing\.148612.19775.inf
0201113-16:44:02 TID:05508 sock:-001 SEND ulNumOfSndThreads=1, ulMaxNumOfSndThreads=20
0201113-16:44:02 TID:05508 sock:-001 SEND Delivery attempt type=2.1, last error=0
0201113-16:44:02 TID:05508 sock:-001 SEND Establishing TCP/IP connection, port=25, host=10.6.x.x
0201113-16:44:02 TID:05508 sock:1124 SEND-I Received SMTP reply, code=220, extension=0x0000 220 DOMINO.domain.COM Service ready.
0201113-16:44:02 TID:05508 sock:1124 SEND Connection established, host=10.6.x.x
0201113-16:44:02 TID:05508 sock:1124 SEND-O Sending, buffer=EHLO server.domain.com
0201113-16:44:02 TID:05508 sock:1124 SEND-I Received SMTP reply, code=500, ext=0x0000, auth=0x0000
0201113-16:44:02 TID:05508 sock:1124 SEND EHLO command not supported, trying HELO...
0201113-16:44:02 TID:05508 sock:1124 SEND-O Sending, buffer=HELO server.domain.com

0201113-16:44:02 TID:05508 sock:1124 SEND-I Received SMTP reply, code=250, authentication=0x0000
0201113-16:44:02 TID:05508 sock:1124 SEND About to read INF file...
0201113-16:44:02 TID:05508 sock:1124 SEND-O Sending, buffer=MAIL FROM: <1402xxx-xxxx@10.1.x.x>
0201113-16:44:03 TID:05508 sock:1124 SEND-I Received SMTP reply, code=250
0201113-16:44:03 TID:05508 sock:1124 SEND-O Sending, buffer=RCPT TO: <tgarst@domain.com>
0201113-16:44:03 TID:05508 sock:1124 SEND-I Received SMTP reply, code=553
0201113-16:44:03 TID:05508 sock:1124 SEND All the recipients are invalid.
0201113-16:44:03 TID:05508 sock:1124 SEND {*** 1637}, szRemHost=domain.com, pszBuf=tgarst

0201113-16:44:03 TID:05508 sock:1124 SEND Thread terminated, rc=54868, MTA notified, MTA returned 27

 

[sl1input]

Looks like you may have SMTP authentication and or SSL enabled.

Check from > Call Pilot Manager "Messaging" - "Message Delivery Configuration" - "SMTP/VPIM" - "Security Modes for SMTP" - Ensure the top 3 SSL tick boxes are unticked and that Unauthenticated is ticked below.

#This will only work if the mail server is set to allow unauthenicated and non SSL connections.

 

[Tman45]

Sl1input - thanks but we do have those unchecked and unauthenticated checked. The log might be from before we changed it <maybe>. We still can't get the message to go thru and I think it is something to to with the IMA error that says domain. com (yes there is a space but we can't find where that is set in any of our configuration. I have even looked at the config on the server. Do you have any other potential idea? We have rebooted recently too. It has to be something silly that is overlooked or maybe we have to walk thru config from scratch again? Maybe a space was accidentally entered and then fixed but it remains for some reason?

 

[AtAvaya]

Please review [URL unfurl="true"]https://support.avaya.com/kb/ext/SOLN186825[/url] which may help resolve this issue. This link includes to very helpful steps in validating the message forwarding is setup correctly.

 

[Tman45]

Thanks @Avaya - I am checking with our vendor since I don't have a valid Sold To or Legacy Site ID in order to establish a login.