Email getting truncated in SOST

Question

Dear SRMer's,
System Information : SRM4.0
As part of the business requirement, our email address in SRM need to be a max length of 100 characters. When testing by creating a shopping cart and adding an approver with a 100 character length email,  in SOST, the email address is getting truncated to 40 characters and the following error message is displayed:
"Cannot process message, no route from Sender XYZ  to Receipient ABC"
Here is the long text of the error message:
Cannot process message, no route from Sender XYZ  to receipient ABC
Message no. XS826
Diagnosis
To continue processing, the system requires a valid route from sender XYZ  to recipient ABC (type INT).
System response
The action was terminated.
Error occurred in R/3 in SAPconnect
Procedure
If this error was generated within R/3 by SAPconnect, you have the following options:
Create a route (i.e. assign a suitable address area, which covers the above address, to a node).
1. Check whether the route exists, but the node to which it is assigned is not in operation. If this is the case, change the route or put the node into operation.
2. Change the recipient address if it has been entered incorrectly.
If the error was detected outside of R/3, please read the operator's manual for your communication software or contact the manufacturer.
Please let me know if any one encountered this problem before and has a solution for it, or do we need to open an OSS Note.
Points will be rewarded for answers.
Thanks in advance,
Bob

Answer 1

Hi
Seems to be a bug.
Note 888730 - Approval link in e-mail for offline approval is truncated
Note 615876 - 3.0-4.0: Extension of the field for the e-mail address
Note 595553 - Mail has the status 'Error', but was sent
Note 86106 - SAPconnect: Faxing from application, error XS826
Note 1031866 - RFx & Auction URL in bidder's email notification truncated
Note 851090 - General Note: Enabling E-mail for use in Job Bid Management
Note 176492 - Automatic email when an alert occurs (RZ20)
Incase this does not help, please raise a customer OSS message with SAP as well.
Regards
- Atul