You are here

Can't send mail with TH 38.2

6 posts / 0 new
Last post
JKEngineer
Offline
Last seen: 2 months 2 weeks ago
Joined: 2008-03-02 14:21
Can't send mail with TH 38.2

After updating from 31.7 to 38.2 Thunderbird Portable, installed locally on a HD with Win7 Pro, I could not send mail through an external server. I was able to receive mail through the same server. When I downgraded back to 31.7, I was again able to send and receive mail.

On trying to send mail, I got an Alert box that said:
An error occurred while sending mail. The mail server responded: Administrative Prohibition. Please check the message and try again.

This happened with several message attempts to 3 different recipients, including email to myself with no attachments.

The Error Console has messages like:

Could not read chrome manifest 'file:///D:/PortableApps/PortableApps/ThunderbirdPortable/App/thunderbird/chrome.manifest'.

Could not read chrome manifest 'file:///D:/PortableApps/PortableApps/ThunderbirdPortable/App/thunderbird/extensions/%7B972ce4c6-7e08-4474-a285-3208198ce6fd%7D/chrome.manifest'.

Timestamp: 8/21/2015 8:57:34 AM
Warning: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create
Source File: resource://gre/modules/Preferences.jsm
Line: 378

Timestamp: 8/21/2015 8:57:34 AM
Warning: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create
Source File: resource://gre/components/steelApplication.js
Line: 783

No chrome package registered for chrome://testpilot/locale/main.dtd

Timestamp: 8/21/2015 9:00:39 AM
Warning: mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create
Source File: resource://testpilot/modules/tasks.js
Line: 975

Any thoughts or insight?

JK

John T. Haller
John T. Haller's picture
Online
Last seen: 4 min 14 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Not Portable-Specific

This issue is likely not portable-specific. Googling a bit shows this can be related to poorly configured POP servers and several other issues. It could also be an incompatible extension (disable them all and try them one by one especially if one is unofficial or hacked to work with a later version of TB than it should support).

Sometimes, the impossible can become possible, if you're awesome!

JKEngineer
Offline
Last seen: 2 months 2 weeks ago
Joined: 2008-03-02 14:21
I did try safe mode

Thanks John.
I neglected to report that I tried "safe mode", that is with no extensions and had the same result. The only add-on I am using is Lightning. When I downgraded Lightning was disabled as version 2 (4.2?) was not compatible with the older version of Thunderbird. I had to find and download an earlier version. (3.3.3 - I know this number does not make sense relative to the version that was disabled - I probably have the wrong number for the disabled one - the 3.3.3 is currently installed).

I am using IMAP.

John T. Haller
John T. Haller's picture
Online
Last seen: 4 min 14 sec ago
AdminDeveloperModeratorTranslator
Joined: 2005-11-28 22:21
Other Issues

In that case, you'll need to explore those other issues on Google. The copy of Thunderbird within Thunderbird Portable is completely unmodified. It's launched with official command line parameters. So, this issue is not portable-specific. If it were, we'd have lots of users with an issue like this.

The error you are encountering can be caused by dozens of different issues within Thunderbird itself and also affects the locally installed version. You'll need to run through the possibilities.

You could start with a fresh copy of TBP and copy your mail in. Or make a backup, upgrade, then delete some of your profile settings files to try to determine where the issue is.

Sometimes, the impossible can become possible, if you're awesome!

JKEngineer
Offline
Last seen: 2 months 2 weeks ago
Joined: 2008-03-02 14:21
Chrome.manifest not in older TBP

I have not done much on this issue. I did look in the 31.7 TBP installation at the two paths cited in the errors regarding chrome.manifest. It does not exist. The paths are there, but the file is not.
Is it possible that the 38.2 version should not be looking for chrome.manifest? (and I understand this may be a TB not a TBP issue).

I may try a TBP installation of 38.2 in another directory and see if it will send mail.

JKEngineer
Offline
Last seen: 2 months 2 weeks ago
Joined: 2008-03-02 14:21
Found the problem

I continued to have the problem described above with any later release of TB that I tried. This included trying the non-portable in a sandbox.

Based on a logged error on the server, I found that the Display Name I had been using "name @ place" was being received as "name@place" with the spaces removed. Either because of the space removal, or because of my use of "@", which was what I had used throughout, the server was reporting a syntax error. Replacing the Display Name with "name at place" solved the problem.

Log in or register to post comments