Topic: 550 5.1.1 USER UNKNOWN

[mike_mattos]

in hosts I have two entries, mydomain.com and *.mydomain.com
in aliases I point www.mydomain.com to mydomain.com

mail for domain  mydomain.com is handled by server  mydomain.com  5   and smtp2.easydns.com 10

I update both with dynsite, it and probably other update programs share  a VPN problem.

Be VERY careful if you use VPN on the dynsite computer, I've seen dynsite update easydns with the IP the VPN connection made while I was doing a support call, and guess what?  No one could email my server!  Very hard to find, because dynsite of course repaired the address when I closed the VPN connection!  The remote VPN site has an email server, and my mail was being directed there!

[dilligaf]

How could they be? The problem you have described has nothing to do with SME server.

Is that not clear yet?

Charlie, I understand your lack of patience, and apologize,
but the vendors that are unable to e-mail us, are not willing to fo anything on their end, they can e-mail all their other clients.
I am trying to be a PITA, I just don't have the expertise to figure out the problem,that's why I am here.

[dilligaf]

in hosts I have two entries, mydomain.com and *.mydomain.com
in aliases I point www.mydomain.com to mydomain.com

mail for domain  mydomain.com is handled by server  mydomain.com  5   and smtp2.easydns.com 10

I update both with dynsite, probably other update programs have a VPN problem.

Be VERY careful if you use VPN on the dynsite computer, I've seen dynsite update easydns with the IP the VPN connection made while I was doing a support call, and guess what?  No one could email my server!  Very hard to find, because dynsite of course repaired the address when I closed the VPN connection!  The remote VPN site has an email server, and my mail was being directed there!

what is the dynsite computer?

[janet]

dilligaf

I just don't have the expertise to figure out the problem,that's why I am here.

So start absorbing what Charlie is saying, he is an extremely experienced person and is being very patient. The problem is your unwillingness to accept his answer.

Get the original sender to forward to you a "complete" returned message. It must be sent to you by Forwarding as an attachment, rather than just forwarding.
You need to get all the Header information to see the path the message has taken, and then you will see the server name & IP etc that is rejecting the message.
In your email client look at the Header or Source or Properties information for the original returned email.

[dilligaf]

will do, and I know about Charlie's capacity/ability,
thank you.

[mike_mattos]

If you have a dynamic name service, you have some way of notifying them when your IP address changes.

Dynsite is a program that does this automatically, on a windows computer.  Historically, SME server would update you PRIMARY domain address OK, but would not update your virtual domains.  Dynsite allows you to have a list of domains updated automatically.

[dilligaf]

gotcha, we're static.

[mike_mattos]

This just reminded me of a similar failure caused by  a clients ISP.  <bell.ca>
 
Client had his own server hosted offsite.  ISP <bell.ca> charged client for a hosting package he was not using, and set up a service under client's domain name.  Ignorant client told ignorant bell rep he wanted his email address to be his domain address, rep turned on hosting service for that domain name on a bell.ca server. 

Client could receive email from most of the world EXCEPT from bell.ca customers (people for whom bell.ca was the ISP) , because bell.ca customers were routed to the bell.ca hosting service, NOT to the customer's server.

took a while to figure it out

[dilligaf]

Mike,
A phone call to telus (ISP) looks like similar issue (they say they found something)
will report back full details when working again.
thanks