Is it a bug that BOE XI 3.1 emailing doesnot supports FRC2822?

Question

Dear All,
SMTP RFCs.                                                                               
The main concern is around section 3.4 of that RFC. It says that                                                                   
addresses in address-lists must be separated by commas, however BO XI                                                              
forces the use of semicolons in some fields, and allows their use in others.                                                       
There is a mention of semicolons in the RFC, but that is only if you aresending to special "address groups", which I don't think is
used anymore.                                                                               
Semicolons on their own cannot be used to separate addresses.                                                                               
One problem we have faced due to this is that the Sendmail SMTP server                                                             
will truncated the recipient list of the message incorrectly separates                                                             
addresses with semicolons. I am sure that other SMTP servers will display                                                          
unpredictable behaviour due to this bug.  
1. Schedule a webi report to send an email.                                                                               
2. In the Destination section, you are allowed to enter semicolons to                                                              
separate addresses. When the report runs it will not convert these to                                                              
commas before sending them to the SMTP server.                                                                               
3. In the Notification section, if you separate addresses with commas,                                                             
they will revert back to semicolons after saving the schedule. Email                                                               
headers also contain semicolons instead of commas.

Answer 1

The problem is that if the variable is set as mandatory, it will prompt the following error?
A database error occured.  The database error text is MDX
SELECT {} ON COLUMNS,
[ZB1STORE].[LEVEL01].MEMBERS DIMENSION PROPERTIES
[ZB1STORE].[4ZB1STORE] ON ROWS FROM
[ZPZB1OA1/ZPZB1OA1_02_TEST] SAP VARIABLES [ZSTORES]
INCLUDING [ZB1STORE].[0000001011001]. (WIS10901)
But then if I set it back to optional, no error will occur.
Therefore I want to know if it looks like a bug since I understand both optional/mandatory variables should be supported.
Thanks.
Derek