Koozali.org: home of the SME Server

Gmail directing all SME Server Emails to spam.

Offline mmccarn

  • *
  • 2,627
  • +10/-0
Re: Gmail directing all SME Server Emails to spam.
« Reply #15 on: May 20, 2023, 02:26:43 PM »
Make sure that google's reason is still the SPF record.

There are lots of other things that Google will use to classify email as SPAM.

Possibly relevant in your case:
* IP Addresses from ranges of IPs assigned by your ISP to residential internet connections
* Mismatch between your server's DNS, HELO and PTR records



Way too much detail

IP Address Space
- If your IP address belongs to a range that has been identified by your ISP, or by any of several spam filters (spamhaus etc) or by Google as belonging to an IP Address space used mostly by residential users some of whom have dynamic IP addresses, your email may go to SPAM.
- The recourse in this case is to pay your ISP for an IP with a different reputation, or to relay your email through an outgoing service
--> If you start relaying email through a service you will need to adjust your SPF record

HELO
- whatever your server uses as its HELO string needs to return your server IP address in a DNS lookup
- Some services also insist that the name used for HELO return an "A" record, and not a "CNAME" record
- SME 'HELO' is set using qpsmtpd->HeloHost, defaulting to DomainName if qpsmtpd->HeloHost is not set:
Quote from: /etc/e-smith/templates/var/qmail/control/helohost
{ $qpsmtpd{HeloHost} || $DomainName }
Quote from: bash command to check the DNS lookup of your HELO value
nslookup $(config getprop qpsmtpd HeloHost || config get DomainName) 4.2.2.2

PTR
- your IP address needs to have a PTR record
- The name returned for the PTR lookup for your IP needs to resolve to the same IP
- The PTR record for your IP is controlled by whoever owns the IP address -- almost certainly your ISP.  Changing or setting a PTR record for your IP would require asking the ISP, who may or may not do what you ask.

Quote from: Demonstrating using apache.com (edited for readability)
# nslookup -type=txt apache.com
apache.com   text = "v=spf1 +a +mx +ip4:67.227.199.17 ~all"

# nslookup -type=ptr 17.199.227.67.in-addr.arpa
17.199.227.67.in-addr.arpa   name = host2.accelrf.com.

# nslookup host2.accelrf.com
Name:   host2.accelrf.com
Address: 67.227.199.17

Quote from: Figure out who owns the IP (who can change the PTR record)
# curl ipinfo.io/67.227.199.17/org
AS32244 Liquid Web, L.L.C

# nslookup -type=soa 17.199.227.67.in-addr.arpa
# (nothing, so chop off the last octet
# nslookup -type=soa 199.227.67.in-addr.arpa
Non-authoritative answer:
199.227.67.in-addr.arpa
   origin = ns.sourcedns.com
   mail addr = admin.sourcedns.com
   serial = 2023050301
   refresh = 28800
   retry = 7200
   expire = 3600000
   minimum = 14400
« Last Edit: May 20, 2023, 02:37:45 PM by mmccarn »

Online Jean-Philippe Pialasse

  • *
  • 2,762
  • +11/-0
  • aka Unnilennium
    • http://smeserver.pialasse.com
Re: Gmail directing all SME Server Emails to spam.
« Reply #16 on: May 21, 2023, 02:16:57 AM »
there are a lot of variable. including people taging it as spam, organization inside goigle adding score for incoming emails.
wait few days and reevaluate

Offline JRBATM20192021

  • ***
  • 111
  • +0/-0
Re: Gmail directing all SME Server Emails to spam.
« Reply #17 on: May 21, 2023, 07:59:14 AM »
Sounds good I will take a look at that stuff and reevaluate in a few days... Thanks!

Offline ReetP

  • *
  • 3,732
  • +5/-0
Re: Gmail directing all SME Server Emails to spam.
« Reply #18 on: May 21, 2023, 03:36:39 PM »
give it some time and wine. 
aging is the same for reputation and good wines.

:lol:

I can testify to that.
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions of software
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation