It's definitely worth it to run your own eMail system (in my 
opinion).  I think people should be able to do this if they want to, 
although one of the challenges that sometimes arises is which IP 
netblocks their eMail servers are in.

        If your server is operated at home, you may be in a dial-up 
netblock, which many providers will block outright or count in 
weighting as being potentially problematic.  In such cases your 
internet provider may be able to provide you with a different IP 
address that's in a non-dial-up netblock, or, assuming this is the 
problem, you may need to consider other options (e.g., routing 
through a different IP via an encrypted tunnel/private-VPN, or using 
delegating to another host to act as a relay {we used to provide this 
for a few of our clients, until they decided to switch over to us}).

        One thing that might be helpful to you is getting yourself listed in 
the DNSWL:

                DNS whitelist (DNSWL)
                https://www.dnswl.org/

        If you haven't already, you may want to consider getting your IP 
address(es) registered through their self-managment interface.  (I 
don't know if this will solve your problem with Google's systems, but 
hopefully it will at least prevent future issues with other systems.)

        Google also has a document that might be helpful (I don't know 
whether you've seen this one yet):

                Google Support :: How to find out why email sender is deferred
                
https://support.google.com/mail/thread/15238559/how-to-find-out-why-email-sender-is-deferred?hl=en

        One of the last links on that page includes "bulk_send_new" which 
leads to the following form that promises to help by escalating the 
problem you described:

                Sender Contact Form :: Bulk Sender Escalation
                
https://support.google.com/mail/contact/gmail_bulk_sender_escalation

        The second part of that form provides one HTML textarea to submit a 
summary of the problem, and another for a detailed explanation.

        I hope this will be at least somewhat helpful to you in getting your 
eMail issue sorted.

> I know, I'm not alone in this... :(
> 
> I like to think that it's still feasible to run one's own email. I have for 
> many years, and currently manage about a dozen email domains for family and 
> friends. Most of the time all good. 
> 
> Then today my dad says to me "Why am I getting these bounce messages?" 
> 
> I check, and Gmail are deferring an email he sends every week to a group of 
> friends, 20 all up, 15 of them on Gmail, saying his SPF domain is a source of 
> unsolicited email (421-4.7.28). Outlook and Hotmail accept OK. 
> 
> This domain is old, not compromised, has SPF, DKIM (1024bit), DMARC, all 
> valid. We send using TLS. We have correct PTR. His emails go out fully signed 
> and pass checks. We don't send commercial emails, and that domain name is low 
> volume and all emails individually written and sent through a webmail client, 
> none of it is automated. 
> 
> Are we wasting time even trying any more? 
> 
> You can't even submit a request to them for help, because they ignore it 
> unless you attach valid and current mis-classified headers from within gmail. 
> Umm.. how can I do that when they're not accepting the email? 
> 
> Simon Wilson
> M: 0400 121 116


-- 
Postmaster - postmas...@inter-corporate.com
Randolf Richardson, CNA - rand...@inter-corporate.com
Inter-Corporate Computer & Network Services, Inc.
Vancouver, British Columbia, Canada
https://www.inter-corporate.com/


_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Reply via email to