Solved SMTP Access is Denied

[chrisjako]

I sporadically get issues with the on premise 3cx PBX where as the SMTP stops working, for no reason i can think of

Restarting the event notification manager service fixes the problem, however i really need to find the source of the problem

We are running V18

 

[cobaltit]

Would this be 3CX SMTP?

 

[chrisjako]

Would this be 3CX SMTP?

Yes the inbuilt one on the server, I an running the PBX on a dedicated server using the debian install

 

[cobaltit]

Well technically there is no SMTP server built-in, just the SMTP client

But the issue you describe is typically what happens when you either either on a dynamic IP or you have some sort of misconfiguration. For example, we had a PBX where the IT folks had traffic coming in on one IP address which was we had in 3CX, but outbound traffic went out on another IP. In that scenario, 3CX was expecting SMTP from the IP configured in 3CX, but saw SMTP traffic from a different IP and denied it.

Anyways, either way is it's a network issue more than likely, which if you can't solve (in this case we couldn't get their IT to fix) when we used a different SMTP with authentication.

 

[chrisjako]

Hmmm, the problem isn't constant though its intermittent - I could understand if it either did work or it didn't, setting up SMTP is my plan B however its not an ideal solution for set and forget

 

[NickD_3CX]

Hmmm, the problem isn't constant though its intermittent - I could understand if it either did work or it didn't, setting up SMTP is my plan B however its not an ideal solution for set and forget

Do they have more that one WAN links on their Firewall? If so, they could be load-balancing which could explain why this is intermittent.

If the network side of things for this customer is being handled by someone else and you don't want to get much involved with them, I think settings up your own SMTP might be the way to go, but I agree with cobaltit that what he said is the most likely scenario.

 

[chrisjako]

Thanks, i dnt have time to do a deep dive into this so just setup as office365 instead - all seems to be working fine so far

 

[NickD_3CX]

Glad to hear that!

I'll mark this one as 'Solved'.