Skip to content

SMTP Issue when Reporting Issues and sending zero sized attachments #551

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
danielloader opened this issue Mar 2, 2025 · 1 comment
Open
Labels

Comments

@danielloader
Copy link

Hey, we've recently swapped from AWS SES SMTP servers to Postmark SMTP and now running into an issue.

AWS SES seems to tolerate sending zero byte attachments (and just doesn't attach them) but postmark rejects them with an SMTP Error code 300 - Zero-sized attachments not allowed.

I am assuming this is because the stderr file is zero bytes (though I want to include the stderr and stdout files where possible on emails).

  • Can shinyproxy check if the file size is zero bytes before attaching the email and omit if it's zero?
  • Or can shinyproxy emit some sort of commented header into the start of each file so they're never zero bytes?

We've had to roll this change back for now but would be good to get SMTP compliant emails out.

@LEDfan LEDfan added the bug label Mar 7, 2025
@LEDfan
Copy link
Member

LEDfan commented Mar 7, 2025

Hi, this seems like a bug that we can easily fix. I created an internal ticket and we will fix it in the next release.
I

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants