This content has been marked as final. Show 8 replies
I am getting the exact same error - did you ever get a resolution to this ?
i don't see such a problem on my OCS.
What OCS version are you using? What mail client are you using?
I am using Build 10.1.2.3.0. This problem happens with both the Oracle Web Access client
and if I use the Oracle connector for Outlook.
It only happens with one email address - all other domains are fine ?
We have the same problem.
With some domains, emails come back with 501 #5.5.2 syntax error 'rcpt to:<firstname.lastname@example.org> ' with the trail space.
In the es_header table the address is written whitout the space, but maybe the space is added during the sending process.
Any help appreciated.
Thanks in advance.
Same problem here, only with one domain.
All other emails to other domains work without a problem.
I do compose the email without any spaces at the end, but when i send it i get an error message back, and suddenly there's a space at the end of the email address;
Original message (id 1570892) received at Fri, 11 Jan 2008 10:39:57 +0100
Message was not delivered to the following addresses:
Reporting-MTA: dns; portal.desyde.nl
Received-From-MTA: dns; a80-127-177-18.adsl.xs4all.nl
Arrival-Date: Fri, 11 Jan 2008 10:39:57 +0100
Final-Recipient: rfc822; email@example.com
Last-Attempt-Date: Fri, 11 Jan 2008 10:40:23 +0100
501 #5.5.2 syntax error 'rcpt to:<firstname.lastname@example.org> '
Remote-MTA: dns; smtp.routit.net
Is possible that is there not any possibility to workaround to this problem?
On metalink no mention about.
Anyone as a hint ?
Well, it seems like there isn't an official answer about this matter, from what i can gather the problem is being caused by the smtp outbound daemon.
Has someboy tried asking about it on metalink?
Did you import this address into Outlook's local address book? If it's only happening with one address, the entry in the local address book might be the problem. Try deleting the entry and re-creating it. As far as I am aware essmo process isn't the culprit, this is an issue at the MUA layer.