I’m not sure exactly where the problem lies here. My IMAP mail service is provided by Google Workspace. I tried to mail a 29 meg. attachment tonight and eM Client popped up a message that said that the “server was limited to transmit files up to 35 meg” (or words to that effect). I went directly to the Google Workspace gmail server and was able to mail the attachment via that. But what’s the story with eM Client telling me that the server is limited to 35 meg and not sending a 29 meg. file? I assume this is a bug.
I’m just posting this in the hope that eM Client will look into the matter. Thanks.
My IMAP mail service is provided by Google Workspace. I tried to mail a 29 meg. attachment tonight and eM Client popped up a message that said that the “server was limited to transmit files up to 35 meg” (or words to that effect.
That is to do with the mail server sending limit.
Gmail’s standard file attachment size limit for sending mail with a personal account is 25 MB “for total message content and attachments”.
Google Workspace enterprise are higher limits which I believe is up to around 50mb. If you were able to send more than 25mb before and have a enterprise account then contact Google support.
Alternatively if you are trying to send and email with an attachment/s and you are restricted in your sending server attachment file size, then you can alternatively send the attachments “via a cloud drive attachment instead” to reduce the size of the outgoing email using eg: Google Drive, One Drive, Dropbox etc as per the following blog below.
The attachments upload into an “eM Client folder in your cloud drive” so you then are only sending a cloud drive attachment link in your email and using your cloud drive space for the attachment.
Thanks for your reply. I have web server space that I use to send large files, so I always have that fallback.
What’s mysterious here though is that I don’t have an enterprise account, but was able to send the 29 meg. file via the web interface without any difficulty. It’s only eM Client that balked. That’s why I felt it was a bug. I wasn’t actually exceeding the server limit, which I do believe has been raised to 35 meg total (I’m not sure about this).