Closed
Bug 330653
Opened 19 years ago
Closed 17 years ago
unable to send big attachments with yahoo.com.BR in Thunderbird
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: caborchardtjr, Assigned: mscott)
Details
(Whiteboard: CLOSEME 2008-05-22)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla Thunderbird 1.5 pt-BR (20051201)
I´m using an mail account from Yahoo.com.BR in Thunderbird 1.5 pt-BR. It receives e-mails without problems, and sends messages without attachments ou little attachmentes (<2mb) too. But when I try to send a message with an attachment with 2,5mb ou 3 mb for example, after a time Thunderbird returns this message: "Resposta do servidor: ´timeout(#4.4.4)´" and doesn´t send the e-mail. Some months ago this problem didn´t exist. Sending files up to 7 megabytes works using the yahoo.BR webmail. I turned off the antivirus (AVAST home edition) and the error continues.
Reproducible: Always
Steps to Reproduce:
1.Create an e-mail account at www.yahoo.com.br
2.Configure Thunderbird with this steps: http://br.mozdev.org/thunderbird/vocesabia/?yahoo (DON´T FORGET TO ACTIVATE THE POP3 IN THE WEBMAIL OPTIONS)
3.Send an message with a file bigger than 3 or 4 megabytes and smaller than 8 megabytes attached.
Actual Results:
It says ´timeout(#4.4.4)´ and don´t send the message
Expected Results:
send the message with the attachment
Lot´s os other users are reporting the same problem with Yahoo.com.BR.
I wrote to yahoo.com.br support and they said this is a problem of thunderbird, but I think that it can be a yahoo.BR problem
on the latest nightly build (version 3 alpha 1 (20060315)) the error persists
Version: unspecified → 1.5
Comment 3•19 years ago
|
||
A POP3 log could be helpful: http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#pop
But I actually doubt that the problem is TB, as the error comes from the _server_.
(In reply to comment #3)
0[274638]: SMTP Connecting to: smtp.mail.yahoo.com.br
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 220 smtp101.mail.mud.yahoo.com ESMTP
0[274638]: SMTP entering state: 15
0[274638]: SMTP Send: EHLO [201.34.xxx.xxx]
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 250-smtp101.mail.mud.yahoo.com
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 250-AUTH LOGIN PLAIN XYMCOOKIE
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 250-PIPELINING
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 250 8BITMIME
0[274638]: SMTP entering state: 4
0[274638]: SMTP entering state: 22
0[274638]: SMTP entering state: 17
0[274638]: Logging suppressed for this command (it probably contained authentication information)
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 235 ok, go ahead (#2.0.0)
0[274638]: SMTP entering state: 19
0[274638]: SMTP entering state: 3
0[274638]: SMTP Send: MAIL FROM:<user@yahoo.com.br>
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 250 ok
0[274638]: SMTP entering state: 6
0[274638]: SMTP Send: RCPT TO:<user2@yahoo.com.br>
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 250 ok
0[274638]: SMTP entering state: 7
0[274638]: SMTP Send: DATA
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 354 go ahead
0[274638]: SMTP entering state: 8
0[274638]: SMTP entering state: 9
0[274638]: SMTP entering state: 0
0[274638]: SMTP Response: 451 timeout (#4.4.4)
0[274638]: SMTP entering state: 10
0[274638]: SMTP entering state: 12
0[274638]: SMTP entering state: 13
Comment 5•17 years ago
|
||
Reporter, could you please test with the latest supported 2.0.0.x / trunk nightlies and see if the issue still occurs?
Whiteboard: CLOSEME 2008-05-22
Comment 6•17 years ago
|
||
No additional useful information since last comment -> resolving incomplete.
Please comment if the issue still occurs in the latest supported 2.0.0.14 / trunk nightlies.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•