Use of 3CX SMTP server does not fumnction correctly despite FQDN resolving correctly

[paddock]

We have a number of 3CX servers out there and all (including existing Standard 15.5s) have custom SMTPs working just fine.

We have just built a new one and it will NOT let us configure a custom SMTP. We have to use the 3CX SMTP which will simply not function. Apparently this is new and we need a (more expensive) Enterprise licence. Being sold-up or what? My point is that our old ones on this software level work, it's just this new one that has been crippled.

We have a working 3cx.co.uk fqdn and certificate which resolves correctly from outside but we get the dumb authenticationinvalidecredentials 5.7.0 denied message which is a) meaningless, b) unnecessary and c) seemingly impossible to escape.

Have tried the obvious stop/reboot/wait 20 mins/reload licence etc etc.

I basically need a hack to strip this stupid restriction out so I can use a custom SMTP and get this system Live.

We have a firewall with multi-NAT and other things on some of the external IPs so I have assigned this to a different external IP to the primary firewall IP, the 3CX SMTP can't cope with this so the quick fix is a custom SMTP. Is there any way to crowbar the permissions as if I already had a custom SMTP then use the Grandfather rights to carry this forward?

I really only want to see responses that a) don't quote the party line and b) don't suggest licence reload/reboots etc

 

[leejor]

I would think that anything, that showed how to bypass 3CX restrictions/requirements on certain versions (if it were even possible), would be quickly removed. You are probably best trying to figure out why the 3CX SMTP server is not working for you.

 

[cobaltit]

OP already stated why it's not working. 3CX SMTP effectly works via IP authentication. So if your FQDN is resolving to one IP but your SMTP attempts are coming out of another one it won't work. You need to add an outbound NAT rule to correct.

As far as the versioning, you don't need enterprise, you need PRO or higher. This was changed in one of the v15.5 SP's and existing standard licenses that were already using custom SMTP were allowed to remain that way although if you change it you won't be able to change it back.