Content-Transfer-Encoding: 8bit
3 answers
I don't know how you determined that "Content-Transfer-Encoding: 8bit is the key that caused the trap and the email blocked ", when the RM emails are blocked, did you see any error code like 500 or 400?What version of RM are you using?
We see some reported issues in RM emails when they are blocked or it can say 400 or 500 error code received in the log file when email are sent, for example:
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=227893
Some other issues are related to specific email account which has problem itself and are not related to RRC email features.
Ideally if you can check with jts.log and rm.log and see if there is any errors when the emails are sent and post them here for reference and we may find more related info.
We see some reported issues in RM emails when they are blocked or it can say 400 or 500 error code received in the log file when email are sent, for example:
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=227893
Some other issues are related to specific email account which has problem itself and are not related to RRC email features.
Ideally if you can check with jts.log and rm.log and see if there is any errors when the emails are sent and post them here for reference and we may find more related info.
Is it possible that the spam-filter on your mail server is too aggressive? In other words, it only permits Base64 and Quoted Printable?
I tested in my CLM 4.0.6 environment with sendmail 8.14.4 and got the email notification without any problems. These emails do carry the Content-Transfer-Encoding: 8bit header.
I tested in my CLM 4.0.6 environment with sendmail 8.14.4 and got the email notification without any problems. These emails do carry the Content-Transfer-Encoding: 8bit header.
