Closed Bug 272333 Opened 20 years ago Closed 19 years ago

550 5.0.0 Sorry,no access allowed error when sending messages

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: capspb12, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I'm using Thunderbird 0.9 with 3 different profiles, all using IMAP to retrieve
messages and each using a separate unauthenticated SMTP server to send messages.
 I am using Thunderbird 0.9 on both a Windows XP SP2 system and a Fedora Core 2
system, and am having the same problem.  For nearly 4 weeks, I was sending and
receiving messages with no problems.  Yesterday, I wasn't able to send messages
from the Linux side, and now today I can't send them from the Windows side.  A
colleague at work has a similar problem with her install of Thunderbird 0.9 on
Windows XP SP2.  It's not just one SMTP server that doesn't work, all 3 of them
stop working at the same time.  I am also using the same version on my Fedora
Core 2 system at work, with a similar set up (3 accounts), but haven't had any
problems with it yet.

Reproducible: Always
Steps to Reproduce:
1. Open Thunderbird
2. Click Write
3. Put in To:, Subject, Body
4. Click Send

Actual Results:  
It tries to connect to the SMTP server, then pops up with a message box that says:
"An error occured while sending mail.  The mail server responded: 5.0.0
Sorry,no access allowed.  Please verify that your email address is correct
in your Mail preferences and try again."


Expected Results:  
It should have sent the message and copied it to the sent mail folder

I ran Thunderbird while making a log as suggested on the online help and this is
the output of the log:

0[284970]: SMTP Connecting to: geology.umd.edu
0[284970]: SMTP entering state: 0
0[284970]: SMTP Response: 220 geology.umd.edu ESMTP Sendmail 8.12.10/8.12.10;
Mon, 29 Nov 2004 20:13:25 -0500 (EST)
0[284970]: SMTP entering state: 15
0[284970]: SMTP Send: EHLO [192.168.0.100]

0[284970]: SMTP entering state: 0
0[284970]: SMTP Response: 250-geology.umd.edu Hello
pool-138-88-203-106.res.east.verizon.net [138.88.203.106], pleased to meet you
0[284970]: SMTP entering state: 0
0[284970]: SMTP Response: 250 ENHANCEDSTATUSCODES
0[284970]: SMTP entering state: 4
0[284970]: SMTP entering state: 22
0[284970]: SMTP entering state: 3
0[284970]: SMTP Send: MAIL FROM:<karwoski@geol.umd.edu>

0[284970]: SMTP entering state: 0
0[284970]: SMTP Response: 550 5.0.0 Sorry,no access allowed
0[284970]: SMTP entering state: 6
0[284970]: SMTP entering state: 12
0[284970]: SMTP entering state: 13
how do you know it's not a change on the server side?
(In reply to comment #1)
> how do you know it's not a change on the server side?

The first case of this problem arose about 6 weeks ago, which caused me to start
using Thunderbird to see if I could replicate it.  I've been in contact with a
sysadmin for one of the servers I connect to (my work email) plus I administer
one of the other servers as a RH9 box that hasn't changed since I set it up over
a year ago.  The sysadmin for my work email couldn't find any reason that I
couldn't connect to the SMTP server and hadn't made any changes that would have
caused such a problem.  I'm able to telnet to the server at port 25 and get a
response, so it is letting me into the SMTP port.  Plus the fact that all 3 SMTP
servers configured stop working at the same time.
the smtp log shows that you're able to connect to that port with thunderbird as
well. But, if you telnet to the smtp port, can you do this:?

 MAIL FROM:<karwoski@geol.umd.edu>

that's where the smtp server is complaining...
From the log Todd posted everything TB sends is correct so I don't think it's
our fault.
To this I was able connecting to geology.umd.edu by hand (telnet) and with TB
0.9 and got a 
250 2.1.0 <karwoski@geol.umd.edu>... Sender ok.
in response to my
MAIL FROM:<karwoski@geol.umd.edu>
both times.

Todd, I suggest you to use telnet and not only try to connect but do what TB in
the log did. From what you wrote (no problems at work), it sounds like the
problem is somewhere on the line between your computer and the server(s).
I'm at work right now, so I can't try anything out until later tonight.  

If it's a problem with the connection between my computer and the server, why
did another computer (one here at work) have the same problem?  I tried other
smtp servers but none of them would connect, each giving the same error?  Plus,
it's only TB that is having problems; no other email program on the same system
has a similar problem.

I'll try telneting to each of the 3 servers later tonight and see what output I
get and post it here.  Thanks for the help.
(In reply to comment #5)

> If it's a problem with the connection between my computer and the server, why
> did another computer (one here at work) have the same problem?

It has? I read "I am also using the same version on my Fedora
Core 2 system at work [...] but haven't had any problems with it yet." as you
don't, sorry.

> Plus, it's only TB that is having problems; no other email program on the same
> system has a similar problem.

Ok, that's an interesting information. But unfortunately none that gives me a
new idea for now. But there's another thing that's different between your and my
logs. 

220 geology.umd.edu ESMTP Sendmail 8.12.10/8.12.10; Tue, 30 Nov 2004 08:59:41
-0500 (EST)
EHLO [192.168.0.3]
250-geology.umd.edu Hello nrbg-d9bb7cf1.pool.mediaWays.net [217.187.124.241],
pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 6000000
250-DSN
250-ETRN
250-DELIVERBY
250 HELP
MAIL FROM:<karwoski@geol.umd.edu>
250 2.1.0 <karwoski@geol.umd.edu>... Sender ok

Your log only contains "250 ENHANCEDSTATUSCODES" but I get a long list. Since
this is before any authentication or similar the server seems to distinguish
connecting clients somehow. Maybe that has another cause, maybe the same.
OK, I ran TB at my work computer making a log file while I sent a message.  The
output from the log matches what you got when you connected to our SMTP server
here.  Here's the output:

1901632[8cb5040]: SMTP Connecting to: geology.umd.edu
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 220 geology.umd.edu ESMTP Sendmail
8.12.10/8.12.10; Tue, 30 Nov 2004 15:08:27 -0500 (EST)
1901632[8cb5040]: SMTP entering state: 15
1901632[8cb5040]: SMTP Send: EHLO [128.8.50.23]
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-geology.umd.edu Hello iceman.umd.edu
[128.8.50.23], pleased to meet you
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-ENHANCEDSTATUSCODES
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-PIPELINING
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-8BITMIME
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-SIZE 6000000
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-DSN
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-ETRN
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250-DELIVERBY
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250 HELP
1901632[8cb5040]: SMTP entering state: 4
1901632[8cb5040]: SMTP entering state: 22
1901632[8cb5040]: SMTP entering state: 3
1901632[8cb5040]: SMTP Send: MAIL FROM:<karwoski@geol.umd.edu> SIZE=592
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250 2.1.0 <karwoski@geol.umd.edu>... Sender ok
1901632[8cb5040]: SMTP entering state: 6
1901632[8cb5040]: SMTP Send: RCPT TO:<karwoski@wam.umd.edu>
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250 2.1.5 <karwoski@wam.umd.edu>... Recipient ok
1901632[8cb5040]: SMTP entering state: 7
1901632[8cb5040]: SMTP Send: DATA
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 354 Enter mail, end with "." on a line by itself
1901632[8cb5040]: SMTP entering state: 8
1901632[8cb5040]: SMTP entering state: 9
1901632[8cb5040]: SMTP Send: .
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 250 2.0.0 iAUK8RoI003152 Message accepted for
delivery
1901632[8cb5040]: SMTP entering state: 10
1901632[8cb5040]: SMTP Send: QUIT
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP entering state: 0
1901632[8cb5040]: SMTP Response: 221 2.0.0 geology.umd.edu closing connection
1901632[8cb5040]: SMTP entering state: 11
1901632[8cb5040]: SMTP entering state: 13


Later I'll try telnetting from home and I'll post the output then.
Alright, I've been trying things out on my home computer.  I first booted my
computer into WinXP and tried sending a message in TB with the same results.  I
did find something curious.  Our servers deny relaying to addresses off campus,
so in order to send an email from home, I have to use a VPN to connect to a
campus server.  When I did this and tried sending a message to a Hotmail
address, it went through without any problems.  When I disconnected, it stopped
working.  Now, I believe I tried this on my colleagues computer, and it did fail
even with the VPN connected, but it's a curiosity.

I tried telneting to the server (telnet geology.umd.edu 25) but got connection
refused errors.  I could ping the server itself and get a response, but it
wouldn't connect on port 25, even with the VPN connected.

I'm now logged into Fedora and I am again unable to send messages with TB.  I
don't have the VPN for Linux configured right, so I can't test that part right
now.  From Linux, I can telnet to port 25 on geology.umd.edu, but when I try
"MAIL FROM:<karwoski@geol.umd.edu>" I get "550 5.0.0 Sorry,no access allowed"
and nothing else.  Hopefully this is helpful.
so if you see the same error from telnet, "550 5.0.0 Sorry,no access allowed",
doesn't it seem like it's an issue with your connection to your server, and not
thunderbird?
If it's a problem with my connection, how do you explain the fact that I can
send mail using programs other than TB?
(In reply to comment #10)
> If it's a problem with my connection, how do you explain the fact that I can
> send mail using programs other than TB?

If you're sure they don't log in and therefore are allowed to send mails, a
external log should help to see what they do. On Linux Ethereal or tcpdump
should be contained in the distribution. For Windows you'll need to download and
install them seperately.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.