Does RTC email function support "Submission port (587)"?
RTC seems to have an issue to use port 587 (submission port) for some of email notification such as: 1) assigning a member to a project area, 2) invite to join Team.
One of our customer has an issue to send these email notificaiton with submission port (port 587) but other email notification such as workItems modification is fine.
This behavior is consistent and only the workaround we found was to change the SMTP port back to 25 from 587.
Dose anyone have the same issue?
Is this a defect of RTC server? or Do I miss some setting?
REF site for submission port:
Configuring Authenticated Access to Exchange
http://help.globalscape.com/help/me3/configuring_authenticated_access_to_exchange.htm
Thank you!
One of our customer has an issue to send these email notificaiton with submission port (port 587) but other email notification such as workItems modification is fine.
This behavior is consistent and only the workaround we found was to change the SMTP port back to 25 from 587.
Dose anyone have the same issue?
Is this a defect of RTC server? or Do I miss some setting?
REF site for submission port:
Configuring Authenticated Access to Exchange
http://help.globalscape.com/help/me3/configuring_authenticated_access_to_exchange.htm
Thank you!
One answer
The difference between the two types of sending is that the team invitations are sent as the currently logged in user while the work item notifications are sent as the user specified in the E-mail Settings tab of the Admin UI.
In this case, it sounds like the user specified in the Mail tab is allowed to send mail on port 587 while the currently logged in user is not.
We can test this theory by having the customer log in as the user specified in the Mail tab and attempt to send a team invitation. If it works, then we know that the issue is the way the port 587 module is set up; all users who will send team invitations need to be added as authenticated users on that port. Exchange should have documentation on how to do this; I believe it is step 8 of http://help.globalscape.com/help/me3/configuring_authenticated_access_to_exchange.htm. I am not familiar enough with Exchange to say for sure.
Martha (Ruby) Andrews
Jazz L3 Developer
This link may also be helpful: http://www.advancedintellect.com/post/2011/03/02/Exchange-2010-and-SMTP-settings.aspx
In this case, it sounds like the user specified in the Mail tab is allowed to send mail on port 587 while the currently logged in user is not.
We can test this theory by having the customer log in as the user specified in the Mail tab and attempt to send a team invitation. If it works, then we know that the issue is the way the port 587 module is set up; all users who will send team invitations need to be added as authenticated users on that port. Exchange should have documentation on how to do this; I believe it is step 8 of http://help.globalscape.com/help/me3/configuring_authenticated_access_to_exchange.htm. I am not familiar enough with Exchange to say for sure.
Martha (Ruby) Andrews
Jazz L3 Developer
This link may also be helpful: http://www.advancedintellect.com/post/2011/03/02/Exchange-2010-and-SMTP-settings.aspx