The 03.08.18 at 10:47, Jim Norton wrote:
Thanks for the information Carlos. Interesting thing is that for a few months now using ELM I've had no problems sending and receiving emails from the suse suse lists. Some have suggesed that my nameserver was broken, which is not the case either because if my nameserver was broken, I'd have a few more problems that just suse lists.
There can be a temporary failure on the name server. Remember that changes there need to propagate, and servers have memories. Sometimes, they can mismatch. Also, with the power outage, who knows what may have happened? Also, some servers may complain, and other might go ahead. I know of a number of servers that accept non existent "from" addreses without any complaint - I know because sometimes I forget and I go out with my "fake" or invented domain name, and it gets through to the final destination :-)
However, this *issue* has appeared to corrected *itself*. I made no changes to my system. I frankly thought that someone at someone at Suse didn't like a post of mine and made a change to have my address rejected. :-)
i don't hink so :-)
So I'm confused..but things seems to be working now....
I just did a litle test on your address - to late, but lets see -. Observe: cer@nimrodel:~> host oregonhanggliding.com oregonhanggliding.com has address 66.80.68.82 cer@nimrodel:~> host -t MX oregonhanggliding.com oregonhanggliding.com mail is handled by 10 mail.oregonhanggliding.com. This gives the IP of your domain, and that mail to it is handled by another server (mail...). So, we look that one as well: cer@nimrodel:~> host mail.oregonhanggliding.com mail.oregonhanggliding.com is an alias for falcon.oregonhanggliding.com. falcon.oregonhanggliding.com has address 66.80.68.82 cer@nimrodel:~> host -t MX mail.oregonhanggliding.com mail.oregonhanggliding.com is an alias for falcon.oregonhanggliding.com. So, the "other" server has the same IP, so in fact it is the same one. But, it says that the real name of "mail..." is" falcon..." (an alias), that could be another server. Let's look it up. cer@nimrodel:~> host falcon.oregonhanggliding.com falcon.oregonhanggliding.com has address 66.80.68.82 cer@nimrodel:~> host -t MX falcon.oregonhanggliding.com cer@nimrodel:~> Now, we see here a problem: the IP is the same one, but when we ask who handles mail there, we receive a blank. That could cause that the "receiving" mail server in suse thinks that your domain doesn't exist, when in fact the problem is that it doesn't have a proper MX record. That is what I think, at least - perhaps somebody else can confirm it :-? If I repeat for my server, I get: cer@nimrodel:~> host tiscali.es tiscali.es has address 212.166.72.69 cer@nimrodel:~> host -t MX tiscali.es tiscali.es mail is handled by 5 smtp.tiscali.es. cer@nimrodel:~> host smtp.tiscali.es smtp.tiscali.es has address 212.166.64.67 cer@nimrodel:~> host -t MX smtp.tiscali.es cer@nimrodel:~> So, I'm unsure. Also, if some other domain server (the secondary server for your domain, prhaps) has a different info, then we could have an intermitent failure. -- Cheers, Carlos Robinson