What SM version you using ?

Inbound or outbound ?

Yes for domains

In build 8797 as the smarter mail administrator, you can define the domain defaults system wide, 

Hello Curtis,

Thank you for your message.

I was aware of the setting per domain or by default.

I just wanted to know whether it can also be set per user, as this would be very helpful for my scenario. However, this does not seem to be the case.

Best Regards

Oliver

Correct Oliver, this cannot be set on a per-user level. What is the scenario you're trying to account for?

I can imagine a scenario.  A user in an org that is not too savy and needs a sanity check just for them.

Someone that does not understand that sending a 25 Meg PDF file (because they dont understand how to look at a file size) out to an entire mailing list of like 5,000 people, instead of uploading a file and making a link to it.

One of the orgs we work with, the marketing person built a PDF packed of an event they were doing. all kinds of high res photos. The document was 75 Meg.  They tried sending that out to a mailing list of about 1,000 people, then complained that it would not go out.

+1 on this type of request from us.  I think it is needed.

Oliver, you might be able to try to "events" feature as a smartermail admin.

Not to block an email, but you can create an "event" trigger and when the criteria is met get an email or notification or something for it. In this below I have it set that if an email is sent that is larger than 10Meg then you can take various actions

Hello Kyle,

thank you for your question.

Here are two examples:

Unfortunately, it has now become the norm for users to send large amounts of data by email. The majority of a company's employees should be able to get by with a small size of up to 10MB for receiving/sending. However, there are always departments that require a larger size for receiving/sending. To make it possible for this small group of employees, however, the limits must be raised for the entire domain. This is then used by everyone and leads to an unnecessary performance load on the server and memory consumption.

In the second example, you can see the benefits as a cloud provider. It would be good if you could offer customers packages that also differ in terms of receiving/sending size. Since mailboxes with a higher receiving/sending size also require more performance or bandwidth, they should be priced higher.

Best Regards

Oliver

Hello Curtis,

thanks for your suggestion.

I will try it out with rules. I would just find it a much cleaner solution if I could set it up in the user settings.

Best Regards

Oliver