Solved Email Settings Locked

[niddnet]

Hello All,

I upgraded from v16 to v20 (well, I backed up my V16 and restored to a fresh V20) without problem.

I have been unable to get email to work in any configuration. I have Google Workplace and an SMTP Relay which is secured by IP address - this did not work saying that the server prematurely terminated.

I decided to try the 3CX mail server, and receive 5.7.0 Denied - apparently due to an issue around IP addresses.

My IP addresses are all set correctly, my .3cx.co.uk URL matches the IP of the PBX - however the PBX is behind a router/firewall.

The biggest problem now is I can no longer change the Email Server from "3CX SMTP Server". The dropdown is greyed out. I can still test - and the test still fails - but I can no longer move back to my custom SMTP to try to resolve.

Can anyone help?

Thanks

 

[SteveITS]

A Pro license is required for custom SMTP. As I recall it would keep working if set but couldn’t change then change back.

v16 is pretty old, was/is the license active? If you click on your license key does it show an error?

 

[OlegR_3CX]

Hi there.
So for issue 5.7.0 the issue will happen if the IP of FQDN is mismatched with the IP from where the request comes.
In your case, the FQDN IP is 7X.XX.XX.15 and the requests come from 1X.XX.XX.36

Now the other issue is how are you signing into the user account as a system owner in V16 there was no system owner, and in V20 you don't have a super admin user sign-in. See the guide here as well as the complete tutorial.
Right now you could perhaps use your backup and restore in V18 update 9 and then either upgrade to V20 from the PBX console.

 

[niddnet]

Hi All

Just to answer a couple of questions - yes, the license is live and current (but not pro - that answers that part!).

Re how I'm accessing - when I first did the restore from V16, I fell foul of not having a "system owner" assignment to any extensions - so I fired up the old V16 one more time, added the correct privileges / roles to the extension, took a NEW backup - and then started again from scratch with V20. The beauty of having all this virtualised made it pretty painless.

Finally - I did assume that was the case re. the FQDN IP being incorrect as that is an IP from a secondary routed subnet. I thought I had configured enough routes to make it work - the IP ending in 1x.x.36 is the default WAN interface IP.

I am happy with the V20 setup, aside of email not currently working. The functionality (loss of custom email) I'm seeing is by design, and not an error, so that's fine. And the IP Addressing situation is very much my own issue to solve, so I'll stick my head back into some manuals, and see what I've missed!

Thank you everyone - great support, friendly responses, and super quick. What's not to love!?


Ross

 

[OlegR_3CX]

Ross,
thank you for your feedback and kind words.
If you think of something else let us know.
Have a nice day

 

[niddnet]

I've updated a couple of settings and the PBX now has its own completely separate VLAN, which has the side-effect of having its own "native" IPv4 address. Everything solved, so happy to close this if the mods wish it so!

Thanks again!