Wow... that did the trick! Thanks! Strange how the sender email would make a difference. Maybe Rogers has more tighter email controls???
I wasn't paying attention earlier on - but - I notice you have the sender's email as info@dns323.com.
You could have a situation where the recipient mail server is checking the "sender' email address" and is unable to resolve it and discards the message as SPAM. This could well be the case for others who say it used to work & suddenly stopped (ISPs and email admins as a rule don't publicise their SPAM control procedures or when they change them)
ISPs and email server administrators are forced to do more & more to curb SPAM - some of the tricks used which can cause problems with the DNS-323 sending mail are ...
1) blocking outbound SMTP traffic that does not originate from the organisations's mail server.
2) requiring the originating ip address of the SMTP traffic to be within their network range.
3) using non standard ports on the SMTP server (I think the DNS-323 now allows you to specify the port)
4) requiring authentication to the SMTP server before mail can be sent (the DNS-323 can be set to do this)
5) domain verification (this is described avove)
6) requiring authentication to the POP3 or IMAP server before mail can be sent.