Hello there,
We using gmail to send usage meter reports and we met following trouble:
Unable to send an email because of: 552-5.7.0 This message was blocked because its content presents a potential 552-5.7.0 security issue. Please visit 552-5.7.0 https://support.google.com/mail/?p=BlockedMessage to review our 552 5.7.0 message content and attachment content guidelines. z3-v6sm350428ljb.71 - gsmtp
Can you help us, how to resolve that problem?
Maybe the solution is that use another mail server, not gmail? It is problem because gmail keeps our corporate domain and corporate mailboxes.
vCloud Usage Meter 3.6.1 Build 7359407
After talking to the TSE that I believe handled this specific support request: the issue is not with the .zip format for the export of reports. The error comes from the automatic email in Usage Meter 3.6.1 being sent to um-reports@vmware.com. The zip file itself is encrypted, and Gmail has an issue with this encryption.
Is this the same situation, or was it having an issue sending the reports to your own e-mail address? If it is the above the error can be safely ignored unless you plan on using Usage Insight.
Hello Heaveaxy,
The easy solution would be to use another mail server that can still resolve the um-report@vmware.com address. This is the option I like the least.
I wouldn't mind bringing this to both Product Management and development's attention. Is there a support request? On support we could put in a feature request to allow users to configure the attachment type. Gmail would still allow a .tsv, .txt, or .csv file.
Yes, it is suppport request. I think it would be a good feature to select attachment type for usage reports. Since nothing can be done, we will look for gmail alternatives(
After talking to the TSE that I believe handled this specific support request: the issue is not with the .zip format for the export of reports. The error comes from the automatic email in Usage Meter 3.6.1 being sent to um-reports@vmware.com. The zip file itself is encrypted, and Gmail has an issue with this encryption.
Is this the same situation, or was it having an issue sending the reports to your own e-mail address? If it is the above the error can be safely ignored unless you plan on using Usage Insight.