Closed Bug 490469 Opened 16 years ago Closed 14 years ago

Mail Enable incompatibility for Thunderbird 2.0 and higher

Categories

(MailNews Core :: Networking: SMTP, defect)

1.8 Branch
x86
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: chinkle, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.9) Gecko/2009040821 Firefox/3.0.9 Build Identifier: All versions of Thunderbird after 1.5.0.12 No Thunderbird client from 2.0 onward can send mail through Mail Enable mail server. The error sent from the server is Bad Sequence of Commands. 1.5.0.12 and earlier connect just fine, so it is NOT a configuration problem on the server. Reproducible: Always Steps to Reproduce: 1. Install Thunderbird and configure 2. Attempt to send mail. (this only affects sending mail--receiving mail works just fine)
Graig is that also the case with the 3.0 beta series ? Can you provide smtp logs as described at https://wiki.mozilla.org/MailNews:Logging ?
Component: General → Networking: SMTP
Product: Thunderbird → MailNews Core
QA Contact: general → networking.smtp
Version: unspecified → 1.8 Branch
(In reply to comment #1) > Graig is that also the case with the 3.0 beta series ? > > Can you provide smtp logs as described at > https://wiki.mozilla.org/MailNews:Logging ? I have not attempted to install the beta client at work. My superiors do not allow the installation of beta software at work.
(In reply to comment #2) > (In reply to comment #1) > > Graig is that also the case with the 3.0 beta series ? > > > > Can you provide smtp logs as described at > > https://wiki.mozilla.org/MailNews:Logging ? > > I have not attempted to install the beta client at work. My superiors do not > allow the installation of beta software at work. If you are running 2.x series at work (one that does not work) - could you still provide us SMTP logs ?
No response to information requested. Closing as incomplete report.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.