Dotnetpanel Forums

I've upgraded all my servers to DNP 2.5.0 (which are all windows 2003 servers). And yes, I've also changed the provider from SM 3.x-4.x to SM 5.x by changing the record in the Services table.

I'm using SmarterMail 5.x (the latest version).

• By default I have POP retrieval enabled, that is set to disabled by DNP
• Limits are all over the place; mailbox size is incorrect, number of users is not set according to the DNP policy and same issues are with user aliases, pop retrieval accounts and recipients per message.
• Priority seems to be totally ignored; I've set some different priorities to my message but those settings seems to be ignored and set to factory default, not server's set-defaults.
• Throttling, same issue there as with priority
• Events, don't know. I haven't changed those from the factory defaults yet...

Please take a look at this, this level of inconsistency is a little embarrassing to my customers

Thank you,
Halldor Hrafn.

ping...

 Is anyone else having this issue?

Hi, sorry for delay.

Current provider was tested on SM 5.1 and some features were not accessible from SM API. Yesterday SmarterMail 5.x (5.5.3126)*  was released and after some tests some features don't work and they will be fixed.

1. POP retreival will be fixed and included on UI in domain settings.

2. Max bounces per hour will be added into throttling (it is available from SM 5.5). Bandwidth and messages per hour will be fixed.

3. Priority settings are not accessible through SM API.

4. We are working if it possible to set Events in domain settings.

5. "Limits are all over the place; mailbox size is incorrect, number of users is not set according to the DNP policy and same issues are with user aliases, pop retrieval accounts and recipients per message....."

Could you be more specific here, please? Mail box size you set when you create new Mailbox and it honnors Hosting plan limit. User aliases, number of users you set in Hosting plan and DNP uses this quotas over those quotas that you specified in domain settings. Hosting plan quotas are not affect the provider, it is general mechanism for all mail providers.

6. Max Pop retreival accounts option is available in SM 5.5 and it will be added in DNP.

7. Currently we are investigating how to handle Events in Domain Settings and results will be available later.

Thank you for your cooperation and reports. 

Hi,

Thank you for your reply

For items numbered:

3. "Priority settings are not accessible through SM API."

Do you mean that since priority settings are not available through the SM API, then any inconsistencies in config are a result of a possible bug in SM's API ?

5. "Could you be more specific here, please?"...

See the following list; example vales are in this order: SM domain default / DNP hosting plan / result on domain 

1. Disk space (for domain): 500 / n/a / 500 MB
2. Domain Aliases: 2 / n/a / 2
3. Users: 100 / 10 / 100
4. User Aliases: 1000 / 0 / 1000
5. Mailing lists: unlimited / 0 / unlimited
6. POP retrieval accounts: 10 / n/a / unlimited
7. Max Message Size: 10000 / n/a / 10000 KB
8. Recipients per Message: 200 / n/a / 200

Some of the settings seem to be available when an administrator is editing the mail domain with DNP, however those values are not in the plans and they are reported as 0 in DNP (even though SM says they are some set value, for example domain disk space).

What I would expect is that the hosting plans have all these values, or at least in the service settings. When DNP creates a mail domain/account it should either set the assigned values or at least use the SM server's default settings. When viewing the values, DNP should read the set values from SM. Some of these points are probably what you are trying to accomplish (or doing), but for some reason I'm experiencing this inconsistencies. So please examine this and either fix it or ask me to call a priest to exorcise the servers

Please let me know if you need any more info, and to the other users of DNP; Do you also notice these problems ?

Thank you,
Halldor Hrafn

Hi.

Let's have such case. You have hosting plan with 10 users and 2 SM domains. How to handle number of users for each domain? Hosting plan quota works with all mail domains created under the space. So you can set in your SM domain even 1000 users but if you have in hosting plan 100 you able to create only 100 users.

Against Priority I can't say it is SM bug. It is their right to make these options available through API. May be they will include it in next release, I've already asked them.

Hi,

I seem to have read some values incorrectly and I apologize for the confusion.  

Yet I feel there are a few this that need some further investiction. The following are all the relevent settings which are applied to the hosting plan, SM's domain defaults and the resulting settings applied to the mail domain and mail account in SM.

Hosting plan:
Mail Accounts: 10 - even though DNP uses this value to limit the accounts, shouldn't it also use it to set the domain?
Max Mailbox Size, MB: 40 - ok
Mail Forwardings: 40
Mail Groups (alias): 0 - in DNP zero is "disabled" but in SM zero is "unlimited", yet the account gets the SM's defaults.
Max Group Recipients: 50
Mail Lists: 0 - in DNP zero is "disabled" but in SM zero is "unlimited", how is it used when applying settings to a mail domain?
Max List Recipients: 0

Domain defalts: (0 = unlimited)
Disk Space: 500 MB
Domain Aliases: 2
Users: 100
User Aliases: 1000
Mailing Lists: 0
POP Retrieval Accounts: 10
Max Message Size: 10000 KB
Recipients per Message: 200

Domain settigs (shown from SM): (0 = unlimited)
Disk Space: 500 MB
Domain Aliases: 2
Users: 100 - incorrect*
User Aliases: 1000 - incorrect*
Mailing Lists: 0  - incorrect. should be disabled not unlimited (zero). .. or is this value set to zero when Mailing lists are disabled ?
POP Retrieval Accounts: 0 - incorrect. should be 10 not unlimited (zero).
Max Message Size: 10000 KB
Recipients per Message: 200

User settings: (shown from SM):
Mailbox Size Limit: 40 MB - correct

*Even though this value is actually ignored by DNP for creating mail accoutns, it should still be set. If a user has a privledge as a domain admin, then he/she can create more accounts beyond the limit in DNP.

 Also, from my point of view, I feel like that at least the Limits -settings, found under Mail Domain Properties in DNP, should be apart of the Hosting plan.

Thank you for listening ,
Halldor Hrafn.

Many of the limits set in DNP are only enforced while using the DNP admin, if the user changes there mail account to a domain administrator then they can bypass the limits because these limits are not also set properly in SM

For example there is no way to limit specifically the number of email domains a user can create in DNP, so if a plan has 200 email accounts and unlimited domains or sub-domains then they can create up to 200 separate email domains in SM which for hosts with a domain limited SM (Luckily not me) could potentially use up all their allowed domains very quickly.

In fact I'm not even sure if the hidden domain admin is counted in the max users count in DNP, if not you could create unlimited domains each with a hidden domain admin user (which is counted in SM's licence) so also using up the mail domains and users in a restricted SM licence. 

IMHO if you can't do the implementation properly then you should leave it to SmarterMail, simply have the current plan restrictions (With a limit on mail domains added) and allow the user to only create email domains and be able to login to SM as domain admin to manage there email accounts directly in SM instead.

One other thing the "change password" option would be much more understandable if it was underneath the password boxes and had a little more explanation.

wiredeyes:

For example there is no way to limit specifically the number of email domains a user can create in DNP, so if a plan has 200 email accounts and unlimited domains or sub-domains then they can create up to 200 separate email domains in SM which for hosts with a domain limited SM (Luckily not me) could potentially use up all their allowed domains very quickly.

Exactly. To further emphesize on this matter let's have another example :

Your plan allows for one domain but you allow a maximum of 50 mail accounts (and let's imagine DNP sets the account limit correctly). Now you think that most customer would want to have the option of having one more domain for their web-site so you allow for one, or even two more domains. However, doing that will possibly allow every user to have up to 100 or 150 mail accounts, which will eat up your SM license quite quickly ...

Perhaps a different approach is in order: Allowing for the same amount of mail domain aliases as the domain number, but adding a mail domain limit to the hosting plan ?

We like to allow unlimited domains and subdomains to be added as website aliases or email domain alias and thats fine.

It is a very simple fix, like you limit the number of phisical websites a user can create you should be able to limit the number of phisical email domains,

Hi.

I just want to ask how you can create 150 users if you have restriction of 50 users in Hosting Plan? For example you have created 40 users for one domain and then decided to add new domain - so only 10 users left for second domain. Note that new domain creation inhertis default domain settings.

Andrey Severtokov:

Hi.

I just want to ask how you can create 150 users if you have restriction of 50 users in Hosting Plan? For example you have created 40 users for one domain and then decided to add new domain - so only 10 users left for second domain. Note that new domain creation inhertis default domain settings.

Simple you just make your email user an domain administrator and since the limites imposed by DNP are only in DNP's system (And seem to be unlimited in SM) you can simply login to SM as domain admin and you can create unlimted users using as much space as you like.

I just tested this actualy. I set my plan up with the folowing restrictions

I then created a new user as domain admin on a new domain in DNP with a 200MB mailbox limit (DNP would not let me go over this).

I then logged into this user and as I was a domain admin I was able to change my max mailbox size create as many users as I liked as the domains max users is set to 0 (Unlimited) by DNP.

In this case I agree with you. But you do these changes in SM directly. Here can be many examples when you create item in DNP and then modify it on the server. After such changes I cannot guarantee stable work of your created items.

Andrey Severtokov:

In this case I agree with you. But you do these changes in SM directly. Here can be many examples when you create item in DNP and then modify it on the server. After such changes I cannot guarantee stable work of your created items.

Sorry no offience but your talking absolute rubbish, if DNP actualy set the max users correctly for a domain in SM rather than setting it to 0 (unlimited) then this wouldn't be an issue, the same goes if DNP actualy had a setting for limiting the number of email domains that could be created, this way we could actualy put limits on our customers that they couldent bypass by simply making a user an SM domain admin.

it would make things allot easier, if the serveradmin could select in settings if users can create mailbox admin accounts or not. as if the user can login to SM and make changes that DNP cant track, its pointless having this feature.

 either

a) work like helm4 does, and reads SM for new settings
b) develop a sync task that checks SM settings and imports accounts
c) to stop having issues like above, maybe set DNP to use "default limits" in smartermail for most features ie limiting (excluding diskspace, as i like setting that per hosting plan in  DNP).

I agree on the points above, though I doupt removing a domain admin support is the right solution. There are far more settings in SM which a customer might want to set and DNP does not provide (for example domain keys).