Messages

Hi friends, because Aliases still won't update the IP list of smtp.gmail.com, I used a stupid method.

I wrote a cron to extract each IP and then manually added aliases.
*/3 * * * * ping -c 1 smtp.gmail.com | grep data. >> IP.txt

Sorry for the confusion.

"Gmail" was created by me to express that Aliases can only get 1 IP.
The Aliases actually applied by the firewall is Gmail_SMTP.

The DNS part you mentioned, I use 8.8.8.8 for each interface to resolve, but because the IP of smtp.gmail.com changes at any time, it causes the IoT device to use the unresolved IP to send mail, so it fails.




Thank you very much for your help, I will look for related articles on the forum.

Hello, I created a new vlan and set it to all deny, but some IoT devices still have to send alert mail through smtp.gmail.com, so I want to add a record in Aliases, but the record only It will capture 1 v4 and 1 v6, and will not create an IP list, resulting in some exception IPs encountered when parsing smtp.gmail.com and unable to send mail.






Thanks for your help.

Hello guys, when I add smtp.gmail.com to Aliases, I can only get one IPv4 and IPv6, which makes it impossible for other systems to send mail when they encounter parsing errors.

How can I solve it?

My aliases settings are as follows:

Name: Gmail
Type: Host(s)
Content: smtp.gmail.com
Description: Gmail

Thanks for your help.