pratapalakshmiandGitHub
ea35af3250
* feat: add Dockerfile for FIPS compliance * refactor: reorganize FIPS build configuration in GitHub Actions workflow - Moved the FIPS build input to a more logical position in the workflow. - Updated environment variable handling for FIPS builds. - Removed the deprecated docker-compose-fips.yml file and adjusted related upload steps. - Improved readability by consolidating Dockerfile path conditions. * chore: update GitHub Actions workflow to use [email protected] and streamline Dockerfile path handling - Upgraded the build-push action version to v1.3.0 for all build steps. - Simplified Dockerfile path conditions for various services. - Consolidated FIPS build logic for better clarity and maintainability. * refactor: simplify FIPS build logic in GitHub Actions workflow - Removed conditional FIPS build suffix from branch name generation. - Updated airgapped artifacts packaging condition to focus solely on airgapped builds. * fix: remove quotes from Dockerfile paths in GitHub Actions workflow - Updated Dockerfile paths in the build-branch-ee.yml workflow to remove unnecessary quotes for consistency and clarity.
Required DNS Records for Receiving Mail Server
1. A Record
HOST-DOMAINpoints to the server running the email service (e.gplane.example.com).
This can also be replaced with CNAME record of cloud load balancer.
Type: A
Host: <host-domain>
Value: <public-ip-address>
TTL: Auto | 3600
2. MX Record
MAIL-DOMAINrefers to incoming email domain e.g.intake.example.com
Type: MX
Host: <mail-domain>
Value: <host-domain>
Priority: 10
TTL: Auto | 3600
3. SPF Record
Type: TXT
Host: <mail-domain>
Value: "v=spf1 ip4:<A-record-ip-host-domain> -all"
TTL: Auto | 3600
4. DMARC Record
Type: TXT
Host: _dmarc.<mail-domain>
Value: "v=DMARC1; p=reject; rua=mailto:<valid-email-addr>"
TTL: Auto | 3600
Verification Commands
# Verify A record
dig A <mail-domain>
# Verify MX record
dig MX <mail-domain>
# Verify SPF record
dig TXT <mail-domain>
# Verify DMARC record
dig TXT _dmarc.<mail-domain>
You can also visit https://mxtoolbox.com/ to know the issues with your DNS records configuration.
Common Issues and Solutions
-
MX Record Issues:
- Ensure proper dot at end of domain
- Check priority number (lower = higher priority)
- Allow 24-48 hours for propagation
-
A Record Issues:
- Verify IP address is correct
- Ensure mail subdomain matches MX record
Testing Mail Server Setup:
# Test SMTP connection
telnet <host-domain> 25
telnet <host-domain> 465
telnet <host-domain> 587