Please see bug#18084 (especially on 11/16/99 16:41 comments)for more information. Right now, the sspitzer.mcom.com server SMTP configuration is no problem for sending message to same domain e-mail address. But still have problems if send message to different domain e-mail address. For example, there is no problem if I sending message to the same domain (to:uwtest or firstname.lastname@example.org), but still have problems if send to different domain (ex: email@example.com or firstname.lastname@example.org) This bug is logged for just keep track of solving problem for sspitzer.mcom.com SMTP configuration problem, it's not 5.0 problem. Server Name is: sspitzer.mcom.com User/Password is: uwtest
Reassigned to Seth.
Change QA contact to me and Cc: Lisa
19 years ago
Status: NEW → ASSIGNED
Target Milestone: M13
mark m13, accepting.
Doesn't seem like a user-visible issue. Moving target milestone way out.
I still can only send messages to same domain email address by using 4.7 & 5.0: It seemed that the SMTP still had the configuration problem... I am just checking and updaing the comments for this bug.... If I send to different domain email address, I got the Alert message as following: "An error occurred while sending mail, The mail server responded: <email@example.com>...Relaying denied.Please check the message recipients and try again>...still can ONLY send to "firstname.lastname@example.org" itself domain email address.......
I don't think we'll get to doing this. Karen - perhaps benc can help us set up a mail server if needed. Seth - should I close this out?
lchiang, sspitzer, this is dead. close it.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
Reopening this bug since problem is still existing, even this might be a server setup problem, I would like to keep this bug open until we solve this problem. Ccing benc, can you check this server SMTP status for us? If Seth cannot check the status for us, we probabaly need to reassign this bug to Ben to see whether we can solve the server problem instead of close this bug.....
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
I'd need to know more about the specifics of the problem described in this bug. Lets get together FTF or in front of a system so I can see what is going on. I'm sure I can isolate this quickly.
benc / huang, don't worry about this bug. moving to future.
Target Milestone: --- → Future
After confirm with Ben, this is common. It depend on how SMTP configuration setup...But I log bug 69163 since when server is hitting SMTP limitation, our client should display better error dialog to users.... marking bug back to the way it is, and thanks Ben provides the info to me.
Status: REOPENED → RESOLVED
Last Resolved: 18 years ago → 18 years ago
Resolution: --- → INVALID
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.