Is it possible to do so? The goal is to use an internal email address/server so that HipChat isn't reaching out to google servers on port 25 and worrying our network admins. I know there's a field to change the email address but I don't know how that would work without setting server information.
You should be able to make changes to your HipChat Server email configuration with reference to the Limiting filtering and relay rejection. By default, HipChat Server is built with Postfix email server which allows you to send email notifications through TCP port 25 according to the following documentation:
Are you currently running into any specific issues as of now? Perhaps you can share more information so that we can have a better understanding on it.
Hello, thank you for your reply.
So our emails are sending properly but our networking team is getting alerts that the Hip Chat server is getting blocked by the firewall on port 25 while trying to access google. I wanted to prevent Hip Chat from going to google on port 25 but couldn't find a way to change it to a local email server.
Our smart relay is disabled.
A couple of follow up questions from my end:
We are using the latest version of HipChat Server. I am reaching out for examples of the alerts but this is the information I have from them for now (note GHSCDISCHATLX1v is our HipChat Server Appliance): "I am observing outbound traffic from GHSCDISCHATLX1v on port 25 which is being blocked by the firewall. All the traffic is going to IP addresses owned by Google. I am unsure of the function of this server. Is this traffic normal?"
Since the emails are working with this traffic being blocked I was hoping to stop this traffic.
I'll reply again once I have examples of the alerts.
I had to update this reply as it would not let me reply to myself.
Below is one sample from the firewall log. Hope this helps
|Device Name||Event Date||Orig Event Date||Source IP||Source Port||Destination IP||Destination Port||Protocol||Vendor Alert||MSS Action||Logging Device IP||MSS Signature||Dest. Country||vendor_device_id||Source Interface Name||Src. Is Internal||Log Type||Translate Destination Port||Intrusion Outcome ID||Logging Device Hostname||Src. Country||ICMP Code||Event Cnt||mechanisms||Destination Interface Name||Vendor Severity||MSS Log Source UUID||Intrusion Action ID||effects||Interface Direction||Device Number||System Messages||network_protocol_id||Creation Time||Event Number||ICMP Type||Rule||Sensor Name||Dest. Is Internal||Collector Version||Collector ID||Class||Symantec Event Code||Log Type Name||Translate Source Port||resources||Message||Severity ID||Category|
...have mention name FirstnameLastname. Fe.: @MaartenCautreels This certainly helps to know who is being mentioned in a conversation. Imagine your colleague sends the following message...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot