We send reports via subscription and the attachments are blocked by
Mailsweeper saying "Invalid base64". It seems that the server encodes the
attachment wrong so it's blocked by mailsweeper. In notepad the "extra"
character is visible. I encoded an attachment locally and no extra characters
displayed. Not sure how to start. Is Reporting Service causing the error
because mails sent via outlook express are going throught. I know Reporting
Service uses the built-in CDO capabilities to send mails but I have no idea
where to start.It's solved with Service Pack 2. It's not mentioned there as a bug fix but I
believe it was fixed regarding the problems they had with Lotus notes domino
Server.
cheer
"Joachim" wrote:
> We send reports via subscription and the attachments are blocked by
> Mailsweeper saying "Invalid base64". It seems that the server encodes the
> attachment wrong so it's blocked by mailsweeper. In notepad the "extra"
> character is visible. I encoded an attachment locally and no extra characters
> displayed. Not sure how to start. Is Reporting Service causing the error
> because mails sent via outlook express are going throught. I know Reporting
> Service uses the built-in CDO capabilities to send mails but I have no idea
> where to start.
Monday, March 12, 2012
MIME attachment blocked
Labels:
attachment,
attachments,
base64,
blocked,
database,
encodes,
invalid,
mailsweeper,
microsoft,
mime,
mysql,
oracle,
reports,
saying,
server,
sql,
subscription,
via
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment