|Applies To||RSA Product Set: Archer|
RSA Version/Condition: All
Platform: Software as a Service (SaaS) environment
|Issue||RSA Archer Notifications are delayed or not received from a Software as a Service (SaaS) environment, but the Notifications Sent report shows email was sent successfully.|
|Cause||The preferred FROM address for Notifications is not set to firstname.lastname@example.org.|
The customer's email system is not monitoring the correct MX record or needs to whitelist SaaS mail relays.
|Resolution||The SaaS Operations Team recommends customers set the From address to email@example.com (the preferred address). |
If customers wish to send from addresses other than firstname.lastname@example.org, they can request their Email Team monitor the SPF DNS record for archer.rsa.com. It will always have the IPs that Archer may send mail from.
One way to get that is by using the nslookup command-line utility:
Currently, the nslookup returns the following. The mx means the MX host(s) for the archer.rsa.com zone and ip4 entries of 126.96.36.199, 188.8.131.52, 184.108.40.206 and 220.127.116.11.
"v=spf1 mx ip4:18.104.22.168 ip4:22.214.171.124 ip4:126.96.36.199 ip4:188.8.131.52 ~all"
Open a new command line window and run the following commands:
Currently, the nslookup returns the following. The important information from the results is that the MX record is 184.108.40.206.
mailrelay01.archer.rsa.com internet address = 220.127.116.11
Therefore, based on the information above, Archer may send e-mail from: