Author Topic: rejecting connection  (Read 2188 times)

Offline RLyon

  • Full Member
  • ***
  • Posts: 145
  • Country: us
  • Karma: +0/-0
    • View Profile
rejecting connection
« on: October 02, 2020, 02:34:38 PM »
Still cant get VM to email to work. Oct  2 09:03:32 DreamMajor exim[27782]: SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[192.168.1.251] input=" \r\n \r\n"
Oct  2 09:03:32 DreamMajor exim[27782]: SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[192.168.1.251] input=" \r\n \r\n"
Oct  2 11:03:33 DreamMajor exim[3683]: SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[192.168.1.251] input=" \r\n \r\n"
Oct  2 11:03:33 DreamMajor exim[3683]: SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[192.168.1.251] input=" \r\n \r\n"
Oct  2 13:03:35 DreamMajor exim[17724]: SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[192.168.1.251] input=" \r\n \r\n"
Oct  2 13:03:35 DreamMajor exim[17724]: SMTP protocol synchronization error (input sent without waiting for greeting): rejected connection from H=[192.168.1.251] input=" \r\n \r\n"

My Email gateway was port 25 but tried switching to 587 and same thing


Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4064
  • Country: us
  • Karma: +129/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: rejecting connection
« Reply #1 on: October 03, 2020, 09:48:59 AM »
Open a terminal and test it on port 25 with Telnet. https://www.thomas-krenn.com/en/wiki/Test_TCP_Port_25_(smtp)_access_with_telnet

Offline RLyon

  • Full Member
  • ***
  • Posts: 145
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: rejecting connection
« Reply #2 on: October 28, 2020, 03:57:44 PM »
I did as you said and we found that the IT dept changed SMTP servers and are using an exchange server now, but we are still getting this issue below, that it is failing to connect to an IMAP server


[98233 10-28-2020 14:45:01 ]*UM* IMAP ERROR: Connection failed to xxxx.exchange.xxx.com,143: Connection timed out[98234 10-28-2020 14:45:01 ]*UM* IMAP ERROR: Connect failed; TCP Connection Failed[98235 10-28-2020 14:45:01 ]*UM* 1325: FAILED to connect to IMAP Server[98236 10-28-2020 14:45:01 ]*UM* IMAP ERROR: [CLOSED] IMAP connection broken (command)[98237 10-28-2020 14:45:01 ]*UM* 1325: Restarting Main Thread[98238 10-28-2020 14:45:01 ]*UM* 1325: Entering Main Account Thread Loop[98239 10-28-2020 14:45:01 ]*UM* 1325: The previous connection attempt failed, waiting for 30 minutes.[98240 10-28-2020 14:45:02 ]*UM* IMAP INFO: Trying IP address [00.00.00.00][98241 10-28-2020 14:48:11 ]*UM* IMAP WARNING: SSL Connection failed, attempting TCP[98242 10-28-2020 14:48:11 ]*UM* IMAP INFO: Trying IP address [00.00.00.00][98243 10-28-2020 14:49:49 ]*UM* 1320: ACCOUNT INFO: rkoepke AT xxxx.exchange.xxx.com IN INBOX WITH LEVEL 5: SSL, EVENT, LINKED, TIMEOUT (20), MWI

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4064
  • Country: us
  • Karma: +129/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: rejecting connection
« Reply #3 on: October 29, 2020, 11:42:04 AM »
This looks like a general connectivity error... The logs are pretty clear that is can't connect to the server. That said, the initial error appears to be related to the system level SMTP E-Mail Gateway, and the logs you should now are for an individual users IMAP/Enhanced Integration account. Two completely different issues. Remember that each user needs to set their own login credentials for Advanced UM.

Make sure your DNS is set to the appropriate internal LAN DNS servers, otherwise it may not resolve "xxxx.exchange.xxx.com" correctly, or change the SMTP Email server gateway to the IP address of the server.

Offline RLyon

  • Full Member
  • ***
  • Posts: 145
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: rejecting connection
« Reply #4 on: January 20, 2021, 05:32:52 PM »
Their IT dept. said......If your phone server is internal and it’s resolving the external IP of the mail server, then your issue is that the phone server is trying to go outside and hairpin back in. This is typically not allowed.  Your phone server should be resolving webmail.xxxxxxxx.com to 192.168.1.249. My question is how do I do this? Do I use the webmail's external or Internal IP and does it go in the Email Gateway for Email SMTP server? I don't know anything about resolving.

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4064
  • Country: us
  • Karma: +129/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: rejecting connection
« Reply #5 on: January 20, 2021, 11:42:45 PM »
Their IT dept. said......If your phone server is internal and it’s resolving the external IP of the mail server, then your issue is that the phone server is trying to go outside and hairpin back in. This is typically not allowed.  Your phone server should be resolving webmail.xxxxxxxx.com to 192.168.1.249. My question is how do I do this? Do I use the webmail's external or Internal IP and does it go in the Email Gateway for Email SMTP server? I don't know anything about resolving.
The phone system will resolve the name via it's configured DNS servers, it doesn't resolve anything itself, like I said back in October...

Make sure your DNS is set to the appropriate internal LAN DNS servers, otherwise it may not resolve "xxxx.exchange.xxx.com" correctly, or change the SMTP Email server gateway to the IP address of the server.

To see what it is resolving to, you can connect to the SSH terminal and go to the command prompt and enter "ping (name of server)" and see what IP address it resolves to like as shown in the photo (press CTRL-C to stop the ping, and type 'exit' to return to the SSH menu).

If you have the Mitel's DNS servers set to Google or some other public DNS, it is probably resolving to the external IP address, if you have them set to the companies internal DNS servers, it should resolve correctly. Of course, you would always just put 192.168.1.249 in the Email Gateway settings.

« Last Edit: January 20, 2021, 11:58:44 PM by acejavelin »

Offline RLyon

  • Full Member
  • ***
  • Posts: 145
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: rejecting connection
« Reply #6 on: February 04, 2021, 05:38:16 PM »
I'm really sorry if I have beat this topic to the ground. Is System > E-Mail Gateway > E-mail SMTP Server looking for the the internal domain name of the mail server or the public name for all email systems to connect to same question for the Mailbox > XXXX > E-mail Synchronization > E-mail Server. I have Public Name in Both locations and wonder if that is my problem

Offline Tech Electronics

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2972
  • Country: us
  • Karma: +85/-1
    • View Profile
Re: rejecting connection
« Reply #7 on: February 05, 2021, 09:56:41 AM »
RLyon,

It seems you answered you own question here, but I will try to clear this up for you; if I can.

1. If the server you are trying to access is not on premise and therefore is in the Cloud (Internet) then use the Public FQDN.
2. If the server is on premise then use the local FQDN or IP Address.

The answer their IT Department provided earlier in this thread is that they don't or can't allow the Firewall/Router to hairpin back into the system. In reality they should have the same FQDN internally as they do externally, but I do realize that some IT people think it is more secure if they don't and in that case you use the internal FQDN or IP Address to access that server.

Thanks,

TE

Offline RLyon

  • Full Member
  • ***
  • Posts: 145
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: rejecting connection
« Reply #8 on: February 10, 2021, 03:06:54 PM »
Thank you guys for your help. I managed to get help from Mitel Tech Support and they said the issue is that IMAP now uses SSL version 1.2 which wasn't implemented until version 6.3 of Mitel Call Processing. My client has Mitel Call Processing version 6.2. So a simple upgrade should fix it


 

Sitemap 1 2 3 4 5 6 7 8 9 10