On 2/20/19 9:57 AM, William Oliver wrote:
On Wed, 2019-02-20 at 10:16 -0700, S. Bob wrote:
Hi All;
This is probably Off Topic, apologies...
I recently kicked googlemail to the curb in favor of a service that does not read my emails (fastmail). We are very happy with fastmail. We are using our own domain which I was also doing with google.
All of our clients can now email me at the same email address as before and I get the emails via fastmail, however we have one client that I do not receive the emails for. They can email me at other addresses but not the 'migrated' address. I'm not sure how to even start debugging this...
Any thoughts, ideas, suggestions would be much appreciated
Thanks in advance
This happened to me when I set up a mailinglist for a church group I belonged to. I ran a mail server I had in my home office that was hooked up to a cable service. Of the 50 people on the list, 20 could not send mail to the list -- even though they could receive mails.
It turned out that all of them were using one cable vendor and were getting their internet connection through it. I tried calling them, but the technical support folk there said it was my problem and they were not interested in spending time trying to help me -- so I was on my own.
I did a search on the problem at the time, and I wasn't the only person who ran into it. From my reading, it seemed that it was an issue of this particular ISP's internal security protocol that involved some sort of checking of ownership or something like that. The gist I got was that my domain resolved correctly, and the ICANN ownership info of the domain was correct, but the ownership of the some other component, like the IP address, was different, since it was tied to my ISP and not to me -- even though I was doing my own nameservice. Thus, I broke their spoofing rules. There was no solution that I could find, and none that worked for other folk who ran into it -- all of whom were running their own name and mail service from home.
You didn't have a dns delegation-of-authority which allows you to claim control or the mail server's reverse dns address and showing you're not some fly-by-night spammer or some such.
If your were to dig for the PTR record for the mailserver's IP you would get back something like 75-25-207-10.lightspeed.sjcpca.sbcglobal.net that indicates who is currently in charge of that IP. If you had the delegation-of-authority it would return YOUR mailserver's name.
e.g. 1st record shows name of mailserver for your domain 2nd record shows address of mailserver 3rd record ties the mailserver's address to it's IP
forward dns: yourchurch.org IN MX mx.yourchurch.org forward dns: mx.yourchurch.org IN A 192.168.10.20 reverse dns: 20.10.168.192.in-addr.arpa IN PTR mx.yourchurch.org
The delegations are usually available from your ISP if you're persistent and may come with a monthly fee. AT&T used to charge me $5 US but raised it to $15 because they could. Good bye AT&T, hello Digital Ocean: $5 for a basic server includes a delegated authority record.
The workaround I ended up using was to change the Reply To: address for those users to a big-name server address (gmail as I remember) and then forwarded that to my server, which it would do.
Note:
- This was specific to one ISP (and the search turned it up only for
that ISP) 2) It was back in 2008 3) I may not have characterized it correctly, since I didn't actually solve it.
billo _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org