How to remove message size restrictions

[djve]

Under the Global Settings the MTA tab has the subsection of Messages. The subsection has two fields.

Maximum message size (kb):*
Maximum size of an uploaded file(kb):*

We have some rather large files being transfered.
1. Will setting the values to zero work in disabling the checks? Or will an empty field be sufficient?
2. What do the red asterisks mean?

Haven't found this in the wiki or the forum so if I missed it please let me know and I'll look at the original post.

Thanks,

David

[mmorse]

1. Will setting the values to zero work in disabling the checks? Or will an empty field be sufficient?

Never tried-just set it really high; like to 1048576 KB (which =1GB) no one should ever hit that limit-if you're sending 1GB emails around it's time for a different file sharing solution...

2. What do the red asterisks mean?

You have a space, comma, or other invalid character in the line. Enter just numbers in KB with no spaces.

[antonmb]

I've used the Admin UI to change the values to 20480, but the asterisk are still there.

I used the console UI using zmprov, and after a refresh the asterisks are still there.

And I still can't send attachments over 10mb.

Help?

Also, it seems that the postfix settings for message_size_limit isn't updating even when changed through zmprov and the admin UI.

[phoenix]

Originally Posted by antonmb

And I still can't send attachments over 10mb.

I'm not surprised, you've changed the maximum size to 20kilobytes.

You need to do the following commands:

zmprov mcf zimbraMtaMaxMessageSize 10240000
zmprov mcf zimbraFileUploadMaxSize 10485760

That's the original settings and it's in Bytes. Make sure you increase the size to an amount that will include at least 60% more than the original file size as it's larger when it's converted for upload.

[djve]

Thanks but, like antonmb, the red asterisks remain. Even after setting the values from the command line. Minor issue but worth noting.

1Gb! I'm not sending DNA peptide sequences. Just experience has shown that any maximum value will have an exception that needs to be worked around. So the easiest answer for me would have been a no maximum size limit.