proxmox-mail-forward sends mails as .eml?

devilkin

Member
May 11, 2020
24
3
23
Hi,

I've got some cron-jobs on my proxmox system to do verifications of things, and these run as root and mail me output. I've had a .forward with my mail address in the /root dir for this.

Since changing the notification system on my proxmox machine to use an external SMTP server (which is hosted on another device), I'm receiving the cron output as .eml files, which is fairly annoying.

Is there some way to disable this feature of proxmox-mail-forward, or a way to get rid of this behaviour? I just want Proxmox to send mails using my SMTP, but not hijack the entire system mail setup.
 
Last edited:
Hi,

at the moment there is no way to configure this. We deliberately chose this approach to keep the original message intact and to avoid rewriting any headers (for instance: the SMTP server would likely reject the message if the "From" header does not match your email account, due to spam avoidance). Email clients like Thunderbird will display the enclosed message 'inline', making it fairly easy to read the enclosed mail.

However, I do see how this behavior could be annoying in Mail clients which lack this functionality. We will investigate alternatives to improve the user experience.

Thanks for the report!
 
  • Like
Reactions: devilkin
While on the topic of .eml attachments: the Proxmox user mailing list also often, but not always, wraps mails in .eml, which cannot be shown by ProtonMail. Proxmox is not wrong and Proton should fix this, but it's the only mailing list where I encounter this issue regularly.
 
While on the topic of .eml attachments: the Proxmox user mailing list also often, but not always, wraps mails in .eml, which cannot be shown by ProtonMail. Proxmox is not wrong and Proton should fix this, but it's the only mailing list where I encounter this issue regularly.
a lot of mailing lists nowadays behave like this - the issue is if the sender's mail server has a policy in place that doesn't allow the mailing list server to send as the original sender (without tripping up the receiving mail server's spam checks). in that case, the mail needs to be wrapped in some fashion so that the actual mail that gets sent is from the list and sent *as the list* (as opposed to, from the list but sent as original sender).
 
  • Like
Reactions: leesteken
a lot of mailing lists nowadays behave like this - the issue is if the sender's mail server has a policy in place that doesn't allow the mailing list server to send as the original sender (without tripping up the receiving mail server's spam checks). in that case, the mail needs to be wrapped in some fashion so that the actual mail that gets sent is from the list and sent *as the list* (as opposed to, from the list but sent as original sender).
Thank you for explaining. I guess I'm just unlucky due to the combination of the Proxmox mailing list and ProtonMail web-client (which I wish they fixed).
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!