![](https://seccdn.libravatar.org/avatar/734fa1860295423792baab65701da26b.jpg?s=120&d=mm&r=g)
On Wed, 4 Feb 1998, Mike Hostetler wrote:
I'm not so sure that this is a sendmail problem. My theory is that patebonding.com doesn't have their mx records set right. If it was your sendmail configuration, you wouldn't be able to send mail to anywhere except with a fully-qualified name.
554 MX list for patebonding.com. points back to gatekeeper.patebonding.com 554
... Local configuration error
patebonding.com preference = 0, mail exchanger =gatekeeper.patebonding.com patebonding.com preference = 100, mail exchanger = pop.ing.com patebonding.com nameserver = nam.ing.com patebonding.com nameserver = scream.ing.com gatekeeper.patebonding.com internet address = 206.147.212.125 pop.ing.com internet address = 209.46.63.2 nam.ing.com internet address = 209.46.63.1 scream.ing.com internet address = 209.46.63.6 Looks like MX records are ok. These say "Any mail for patebonding.com should go to the host gatekeeper, and if gatekeeper is not up, then send mail to pop.ing.com" Try putting in a "stock" copy of sendmail.cf -- Lou A. Costabile Voice and Fax: [613] 781-7061 <A HREF="mailto:luis@lac.resonet.com">mailto:luis@lac.resonet.com</A> To get Receipt Notification include %rec% anywhere in the Subject field. You must restart your computer before the new message will take effect. Do you want to restart your computer now? Yes or Yes -- -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e