Network Management and Administration


CivicReady
®

CivicReady Whitelisting

Email Servers

This is a list of CivicReady Email servers to be whitelisted on your firewall and email system (if applicable).

'''It is very important that you have your Email Administrator or other IT Professional in your organization whitelist the following list of email IP addresses:'''

USA Servers:

  • 162.209.9.103
  • 162.209.88.57
  • 166.78.237.237
  • 104.130.222.158
  • 104.130.207.166
  • 104.130.206.175

Canadian Clients ONLY

  • orange.ca.regroup.com 69.28.224.24
  • orchid.ca.regroup.com 69.28.224.21
  • pink.ca.regroup.com 69.28.224.241
  • snow.ca.regroup.com 69.28.224.217
  • silver.ca.regroup.com 69.28.224.242
  • white.ca.regroup.com 66.155.96.7

 Note:

  • Without these IP address whitelisted your postings could be delayed.
  • In some cases it is also required to open Port #25
  • Also we would request that you modify your SPF record as follows, as that is also causing issues. This will help us in passing through strict SPF checks. 

xxxxxdomain-name.com text = "v=spf1 ip4:###.###.###.### ip4:###.###.###.### include:_spf.regroup.com -all"

IPs

If you are sending email messages to public domains i.e. yahoo, gmail, outlook, etc they are designed to allow all inbound traffic to be allowed into their email domain; however, government institutions use their own email sever, normally ending in .gov, etc. When multiple accounts in the same domain receive emails, their email security is being attached or spammed and it will normally blocked incoming emails, by adding the IP's for Regroup into their server firewall, they are allowing multiple messages from Regroup to be received. 

IP Address whitelisting for clients with in-house email servers (MS Exchange servers, Postfix etc)

regroup.com <http://regroup.com/>: 209.61.151.224, 104.130.96.10 (PRODUCTION SERVER)

SPF Record

When sending messages, you have the option of using our original email domain server information in the header (From email) (@regroup.com) or use one of your own email addresses (@institution.gov) when using your own email to send from Regroup, their email server firewall flags the email as phishing, since there is no record they send that email, adding our SPF record, you are allowing all emails coming from @regroup.com masked as your @institution.gov to be allowed into the firewall. 

SPF Records for clients who use their own email address as sender
DNS TXT record
rails/dev1.regroup.com <
http://dev1.regroup.com/>: DNS Record Type: TXT, Hostname: example.edu <http://example.edu/>, Text: v=spf1 include:_spf.rails.regroup.com <http://spf.rails.regroup.com/> -all
ri.regroup.com <
http://ri.regroup.com/>: DNS Record Type: TXT, Hostname: example.edu <http://example.edu/>, Text: v=spf1 include:_spf.ri.regroup.com <http://spf.ri.regroup.com/> -all
regroup.com <
http://regroup.com/>: DNS Record Type: TXT, Hostname: example.edu <http://example.edu/>, Text: v=spf1 include:_spf.regroup.com <http://spf.regroup.com/> -all

?



I'd Like to Request an Enhancement

0 out of 0 found this helpful

Updated:
Follow