Forums & Blog

Well done SM admins! Keep on posting here and make this noticed. If enough of us keep replying then eventually someone at SmarterTools will notice....er...that's unless THEY use SmarterMail themselves - perhaps their mailbox size has exceeded 10mb and they don't even realize that the automated 'topic-post-notification' email has bounced! Oh dear...a sad situation for all of us :(

Perhaps we can have some more horror stories of how we've lost good clients due to this draconian oversight? Post em here!

Huh?  

IMO it's ok with 10 Mb as default. Most of our client are satisfied with that. We only extend it for those with special needs. But of course a global configuration for all new users would be better.

While on the subject of global configuration, we would even more like to see a configurable default for "Delete Action" and " Initial Page on Login" plus the "Default User Settings" which now only is accessible as Domain Administrator not as System Administrator.

Lars 

ISEU:

Well done SM admins! Keep on posting here and make this noticed. If enough of us keep replying then eventually someone at SmarterTools will notice....er...that's unless THEY use SmarterMail themselves - perhaps their mailbox size has exceeded 10mb and they don't even realize that the automated 'topic-post-notification' email has bounced! Oh dear...a sad situation for all of us :(

Perhaps we can have some more horror stories of how we've lost good clients due to this draconian oversight? Post em here!

Is there really a point to attempting to start a revolt over this?  Yes, it would be nice to have this fixed, but this is also an issue that if handled properly by the admin, will never be a problem.

 
Also, don't assume that ST just doesn't care and that you have to start a revolt to get their attention.  They have made it known a lot that they do read the forums but do not intend to post a reply to every thread.  Instead, they take the input form the forums and use it to help make decisions about their products.

Oops! I didn't mean to offend anyone by starting a "revolt" - but what other means do we have? We've tried contacting ST: "Sorry, i can't be done" is their 'stock' reply.

I'm glad that you, as admin, have the time to sit there editing each domain. For the rest of us that use automated tools like Helm to add domains we wouldn't even know if a new domain had been added. Even if we did we wouldn't have the time to sit there tweking things. Life's short enough...

But...let's be fair about this: I challenge ST to come up with a simple statement committing to change this oversight. If anyone can get a reply out of ST on this please post it here so the rest of us can rejoice and be happy!

I thought some of the posts were getting a bit too serious here so I've added this light hearted transcript: (no similarity in names intended)

Transcript of the weekly business meeting:

Tom (Programming team, avid StarTrek fan): "So guys, any new features that we could add for the next realease of SM?"
Dave (Shareholder, also has shares in Google): "Hey! How about a URL added to each email sent via SM that offers the user a download of Google Toolbar?"
[Everyone] "Hmmm..."
Stuart (Human resources): "Well Dave that's something we can all give somethought to. Tom, can we add that to your 'possibilities' list?"
Tom: "Yeah, I'll certainly add it to Dave's existing set of 'suggestions' here in this special folder (opens folder)"
Dave: "Cool - you have all my suggestions in a special folder. What does that label "ID 10 T" stand for on the front Tom?"
[Everyone] "(muffled laughter)"
Brian (chairman): "Look guys let's back on track here: what features can we add?"
Jane (Customer services): "well, there seems to be three popular issues right now on the forum."
 "1) There's a lot of talk about changing the default mailbox size limit."
 "2) A few people mentioned something about making SM work on Windows 3.1 and..."
 "3) Someone wanted a skin that made SM look like the control panel in StarTrek Voyager."
Tom: "Wow, that 3rd one sounds tricky but I love a challenge! When can I start working on it?"
Stuart: "Hold on now Tom, let's see what everyone else thinks shall we?"
 "Brian, do you have any thoughts?"
Brian: "I've always said that our products should go cross-platform at some point; Windows 3.1 is well documented and would make an interesting project. Sounds like some our our customers are asking for it already."
Paula (A temp,working here between study courses): "Excuse me, may I make a comment?"
Jane: "Go ahead Paula. By the way can you get me another frothy mocha choco coffee when you're done? That last one was yummy!"
Paula: "Any other drinks orders?"
Brian: "Hang on Paula! What exactly did you want to add to our discussion?"
Paula: "It's nothing really, but I too noticed that the forum had a lot of requests for changes to the default mailbox size limit. Perhaps that's an indictor as to what your customers really need right now? It's just a thought..."
[Everyone] "(pause)"
Tom: "I'll have a latte grande with chocolate bits sprinkled on top."
Dave: "Make that two."
Stuart: "Just an espresso for me thanks Paula."
Brian: "Have you got any of those cookies with nuts in 'em?"
[Meeting adjourned pending coffee break]

I have to say I agree. It would seem that a change in an upcoming release would be very useful. We're currently on Imail and using a third party spam filtering system called Pinjo. It works well, but because the spam filtering has no concept of what Imail is managing, it puts resources spam checking email for accounts that don't exist. Hence why we're evaluating smartermail.

So there's an incentive for the dev team, there's money riding on this for you.
 

hey all, i work at an isp, and currently we have about 130 domains on 1 server, and are migrating about another 150 more to another SM server. we just use web services to invoke the svcDomainAdmin.asmx?op=AddDomain to create the domain, then svcDomainAdmin.asmx?op=UpdateDomain to set the default mailbox size. then we add users by invoking svcUserAdmin.asmx?op=AddUser2. this also has the option of <maxMailboxSize>.

so i guess maybe i've missed the real question here. is it that you want a "clicky-clicky" way to set at a global level the default mailbox size limit for all domains instead of invoking the web services?

 

James is correct, there isn't an option to default that in 4.x but you can do it from webservices.

In SmarterMail 5.x, the default is actually 100mb, and there is a new Default User propagation tool similar to the Default Domain propagation tool available in 4.x...  Our ultimate goal is to provide a Profiles System both users / domains.  Doing this, would allow you to potentially create Profiles in association to your hosting plans (if you are a hosting company).

ISEU:

The good news: There is already an XML entry (undocumented) for default mailbox size.

C:\Program Files\SmarterTools\SmarterMail\Service\mailConfig.xml
Under  <DomainDefaults> you'll see an entry measured in KB for the default maximum mailbox size:

<defaultMaxMailboxSize>30720</defaultMaxMailboxSize> (in this case I changed it from 10mb to 30mb, 30720kb)

Great! So Smartertools already know what we want and added the feature in, albeit requiring manual editing of the XML file, right? Wrong 

 

The bad news: It makes no difference what-so-ever.

I tried adding a new domain and it still had a 10mb mailbox limit.

 

Revolt with me. The offical SmarterTools reply (above) of 'sorry this can't be done' is lame. Every server administrator out there: please join the revolt by adding to this thread! What to tell them: we simply want to set the default domain mailbox size WITHOUT having to manually log into each new domain and configure it, because we use automated tools (like Helm/Plesk/Windows WF) which add the domains automatically whilst we're too busy doing other things - our lives are too hectic as it is, so come on Smartertools get a minor update sorted out before we abandon you and revert back to other mail systems instead. (Please)

How to do it
It's so simple. Surely the programmer knows how to do this? If not, here's how to do it. Each domain has an XML file (such as C:\Mail\testdomain.com\domainConfig.xml) called domainConfig.xml which is created by SmarterMail as part of the new domain creation process. So, first open up your programming tool (VS2005?) and go to the script that gets called when a new domain is added. Search for "domainConfig" because you can bet that this script also names this new file. Just prior to creating that file (probalbly using a FileSystem object) the contents of the XML file will be declared. Look for a key named "MailboxSize" (In the actual XML file it exists as "<MailboxSize>10</MailboxSize>") and at that point insert a new function called "getDefaultMaxMailboxSize" and simply tell it to read the settings from the file mailConfig.xml as explained above. Use the value returned by THIS function rather than the completely outdated and impractical limit of 10mb. Save the script and rebuild the code. Let us have a copy, please!

(If you can't be bothered to do this then please can I have the source code so that I can program it myself?)

 

Haven't heard too many people refer to IMAIL as stable.  We stay very busy helping small and large installations convert from IMAIL for stability and performance issues.

csgo:

slalomdrew:

I believe changing the default settings per domain will only make the default change for new accounts.

 

Yes, we're finding this out the hard way.  Have someone working on it full time making the changes.  If I'm really lucky it will only take a full day to fix this screwup.

Silly things like this are making my old stable Imail look better all the time. 

-Joe

ST-TUzzanti:

Haven't heard too many people refer to IMAIL as stable.  We stay very busy helping small and large installations convert from IMAIL for stability and performance issues.

I used to consult for a mid-sized national ISP, under 500k users, and their hardware footprint for iMail was ridiculous. Even with robust, load-balanced architecture they had stalled queues and marginal throughput. They eventually switched to a plain-brown-wrapper open source solution, ditching the glitz just to get the mail flowing again. I really don't know where or when Ipswitch went to the zoo, but they certainly did.