PACKAGE token does not work

[keaman]

Hi,

I added this code to my dns_a.conf file in /usr/local/directadmin/data/templates/custom.

|*if PACKAGE="remotemail"|
mail=86.111.247.23
smtp=86.111.247.23
pop=86.111.247.23
|*else|
smtp=|IP|
mail=|IP|
pop=|IP|
|*endif|

In reseller account, I added a "remotemail" package.
However, when I create a new user based on "remotemail" package,
Only values ​​from "else" are taken

Regards,
Thomas

 

[keaman]

then your syntax is wrong.

http://help.directadmin.com/item.php?id=293

I turned on the debug mode, but I do not see any errors in it.

This is my full dns_a.conf,
what is wrong?:

localhost=127.0.0.1

|*if PACKAGE="remotemail"|
mail=86.111.247.23
smtp=86.111.247.23
pop=86.111.247.23
|*else|
smtp=|IP|
mail=|IP|
pop=|IP|
|*endif|

|*if IS_IPV6!="yes"|
|DOMAIN|.=91.229.68.56
*=91.229.68.56
www=91.229.68.56
ftp=|IP|
|*endif|

Edit.
In DirectAdmin debug mode, I found something like that, maybe this is the reason:

Named :: writeDB :: error reading ./data/users/mailtest10/user.conf to get package info.

 

[chatwizrd]

Well that doesnt really help much.

Here is the guide:

http://www.directadmin.com/features.php?id=1375

I guess just check the syntax and make sure the package name matches. Is the package you are assigning a user package and not a reseller package?

Not sure what else you could do to diagnose it besides email directadmin support.

 

[DirectAdmin Support]

Hello,

Checking the code, the package is taken from the user.conf, which makes sense.

However, when creating a new User, the domain is created before the user.conf is actually written, hence the creation of the zone (triggered by the creation of the domain) isn't able to find the user.conf, hence the PACKAGE token is empty.

I've just added extra code to pass the package down to the DNS creation, so if it's in the process of creating a User, it will have that information.

John

 

[redeye]

Hello,

Checking the code, the package is taken from the user.conf, which makes sense.

However, when creating a new User, the domain is created before the user.conf is actually written, hence the creation of the zone (triggered by the creation of the domain) isn't able to find the user.conf, hence the PACKAGE token is empty.

I've just added extra code to pass the package down to the DNS creation, so if it's in the process of creating a User, it will have that information.

John

Hi, this works now with 1.43 but only when you create a new user, not when you add a domain to an existing user . Maybe something for future releases.