Closed
Bug 309129
Opened 19 years ago
Closed 19 years ago
Cannot send mail using port 25
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dave.kimberley, Unassigned)
Details
Attachments
(1 file)
|
4.42 KB,
application/x-zip-compressed
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050910 SeaMonkey/1.0a Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050910 SeaMonkey/1.0a Compose message, click send, get the following message: "Send Message Error Sending of message failed. The message could not be sent because connecting to SMTP server mailhost failed. The server may be unavailable or is refusing SMTP connections. Please verify your SMTP server setting is correct and try again, or else contact your network administrator." I have many mail accounts and all the ones that use port 25 fail to send messages, my gmail account (port 587 and TLS) works. This works on Mozilla Application Suite 1.7.11. I have tried using the same profile and creating a new one but I cannot send messages with the Seamonkey Alpha apart from using my gmail account. Reproducible: Always Steps to Reproduce: 1. Compose message, selecting account to send from 2. Click send Actual Results: Get "Send Message Error" Expected Results: Sent message
Comment 1•19 years ago
|
||
Which provider do you use? I remember some providers block outgoing connections to port 25 (except for their own mailserver).
| Reporter | ||
Comment 2•19 years ago
|
||
Pipex. Mozilla 1.7.11 works on the same PC with the same mail accounts so it won't be the provider.
Comment 3•19 years ago
|
||
Can you create a SMTP log as described under http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#smtp ? Also try creating a HTTP log as described under http://www.mozilla.org/projects/netlib/http/http-debugging.html (you can skip the nsHttp:5 part, i'm more interested in the nsSocketTransport:5,nsHostResolver:5 part). Then zip those log files and attach it here to the bug. Also try upgrading to a recent trunk nightly and see if the problem still exists there.
| Reporter | ||
Comment 4•19 years ago
|
||
| Reporter | ||
Comment 5•19 years ago
|
||
Tried latest_trunk: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050918 SeaMonkey/1.1a Still get same problem.
Comment 6•19 years ago
|
||
it looks like from the transport service log that we're connecting to the server, but the server isn't ever sending us a greeting. This looks for all the world like a virus checker or firewall or something intercepting the connection on the port and not allowing data through. On your client machine, if you telnet to port 25 on that host, do you get greeting back?
| Reporter | ||
Comment 7•19 years ago
|
||
Problem solved.
Already disabled windows firewall, Microsoft Antispyware.
Problem was a McAfee VirusScan Enterprise 8 setting:
Virus Scan Console
Access Protection Properties
Port Blocking
Prevent mass mailing worms from sending mail
To solve select "Prevent mass mailing worms from sending mail" then click edit
button and add seamonkey.exe to list of excluded processes (mozilla was there by
default).Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Comment 8•19 years ago
|
||
Maybe we should contact them to include SeaMonkey by default, let me see if i can do something here (also i think this can be dangerous IMHO, does it allow viruses/worms with the name mozilla.exe to send mail then? not sure if they do the right thing here anyway ;)).
You need to log in
before you can comment on or make changes to this bug.
Description
•