Closed Bug 19026 Opened 25 years ago Closed 24 years ago

Need to setup "sspitzer.mcom.com" server SMTP configuration

Categories

(MailNews Core :: Networking, defect, P3)

Product:
MailNews Core
Component:
Networking
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED INVALID
Milestone:
Future

People

(Reporter: huang, Assigned: sspitzer)

Details

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 uwtest@sspitzer.mcom.com), but still have problems if send to
different domain (ex: huang@netscape.com or sspitzer@netscape.com)

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
Assignee: mscott → sspitzer
Reassigned to Seth.
QA Contact: lchiang → huang
Change QA contact to me and Cc: Lisa
Status: NEW → ASSIGNED
Target Milestone: M13
mark m13, accepting.
Target Milestone: M13 → M20
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: 
<qatest30@netscape.com>...Relaying denied.Please check the message recipients and 
try again>...still can ONLY send to "uwtest@sspitzer.mcom.com" 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.
marking invalid.
Status: ASSIGNED → RESOLVED
Closed: 24 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
Closed: 24 years ago → 24 years ago
Resolution: --- → INVALID
Verified.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.