fix : test email : more detail

This commit is contained in:
morteza-mortezai
2025-12-07 23:08:08 +03:30
parent 9aadf42ceb
commit 05b8daede6
3 changed files with 104 additions and 6 deletions
+46 -5
View File
@@ -84,11 +84,52 @@ This endpoint requires **Admin authentication**. Make sure you're authenticated
If the domain is not blocked but emails still aren't arriving:
1. Check the sender's email server logs
2. Check WildDuck server logs
3. Verify DNS/MX records for both domains
4. Check if there are any forwarding rules
5. Verify the recipient's email quota isn't exceeded
### Step 1: Check WildDuck Server Logs
Look for SMTP rejection messages, connection attempts, or errors related to the sender domain:
```bash
# Check WildDuck logs for SMTP rejections
grep -i "metixco.ae" /var/log/wildduck/*.log
grep -i "r.sadat@humapek.co" /var/log/wildduck/*.log
```
### Step 2: Verify DNS/MX Records
Check that the recipient domain has correct MX records:
```bash
dig MX humapek.co
nslookup -type=MX humapek.co
```
### Step 3: Check Sender's Email Server
Ask the sender to:
- Check their email server logs for delivery attempts
- Look for bounce messages or error codes
- Verify the email address is correct: `r.sadat@humapek.co`
### Step 4: Verify SPF/DKIM/DMARC Records
Check email authentication records:
```bash
# Check SPF record for sender domain
dig TXT metixco.ae | grep -i spf
# Check DMARC record
dig TXT _dmarc.metixco.ae
```
### Step 5: Test with Allowlist
Try adding the domain to allowlist as a test:
```bash
POST /email-blocking/allowlist
{
"recipientEmail": "r.sadat@humapek.co",
"senderDomain": "metixco.ae",
"description": "Test allowlist for troubleshooting"
}
```
### Step 6: Check Firewall/Network
- Verify sender's IP is not blocked by firewall
- Check if there are any network-level restrictions
- Ensure SMTP port (usually 25, 587, or 465) is open
## Example: Fix the Current Issue