Open
Bug 525787
Opened 15 years ago
Updated 13 years ago
Seamonkey 2.0 POP3 mail: signature file not attached on reply or forward except on first account
Categories
(SeaMonkey :: MailNews: Composition, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: ceo, Unassigned)
Details
(Whiteboard: [Halloween2011Bug])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0
Seamonkey 2.0 POP3 mail:
Signature file not is attached on reply or forward for mail accounts other than the first one.
Compose works correctly.
Settings are: Automatically quote, reply above the quote, signature below the reply.
No difference with compose in HTML or not.
Reproducible: Always
Steps to Reproduce:
1. Open a mail in an inbox in an account other than the first one
2. Click reply or forward
3.
Actual Results:
Message is quoted but no signature is inserted
Expected Results:
Message is quoted and signature file is inserted
Inserted the signature file.
Comment 1•15 years ago
|
||
And you configured a signature for each Account ?
Comment 3•15 years ago
|
||
I meant under Account/Composition&adressing/[]Include signature for replies / forwards
Can't confirm under Win XP (rv:1.9.1.6pre) Gecko/20091107
Version: unspecified → SeaMonkey 2.0 Branch
Please try again with a signature text set in the account settings and not with a signature file.
Does this error happen in a newly created profile too?
Anything in the Error Console?
Does not work with signature text or signature file with reply above or below, in an old or new account. It only works in the first account, not any others.
Where would I find the Error Console?
Menu - Tools - Web Development - Error Console. It shows Javascript errors on websites AND internal errors of Seamonkey.
Anything in the Error Console? Yep...
Warning: Unknown property 'mso-margin-top-alt'. Declaration dropped.
Source File: about:blank
Line: 39
Warning: Unknown property 'mso-margin-bottom-alt'. Declaration dropped.
Source File: about:blank
Line: 39
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 42
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 45
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 48
Warning: Unknown property 'font-color'. Declaration dropped.
Source File: about:blank
Line: 0
Warning: Unknown property 'mso-margin-top-alt'. Declaration dropped.
Source File: about:blank
Line: 39
Warning: Unknown property 'mso-margin-bottom-alt'. Declaration dropped.
Source File: about:blank
Line: 39
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 42
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 45
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 48
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Error: [Exception... "'JavaScript component does not have a method named: "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]" nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)" location: "<unknown>" data: no]
Warning: Error in parsing value for 'white-space'. Declaration dropped.
Source File: https://bugzilla.mozilla.org/skins/standard/global.css
Line: 278
Warning: Error in parsing value for 'white-space'. Declaration dropped.
Source File: https://bugzilla.mozilla.org/skins/standard/global.css
Line: 279
Warning: Error in parsing value for 'white-space'. Declaration dropped.
Source File: https://bugzilla.mozilla.org/skins/standard/global.css
Line: 280
Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/calendar.css
Line: 7
Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/calendar.css
Line: 7
Warning: Unknown property 'zoom'. Declaration dropped.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/calendar.css
Line: 7
Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/calendar.css
Line: 7
Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/calendar.css
Line: 7
Warning: Expected declaration but found '*'. Skipped to next declaration.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/calendar.css
Line: 7
Warning: Unknown property '-moz-opacity'. Declaration dropped.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/autocomplete.css
Line: 7
Warning: Error in parsing value for 'filter'. Declaration dropped.
Source File: https://bugzilla.mozilla.org/skins/standard/yui/autocomplete.css
Line: 7
Comment 10•15 years ago
|
||
Sorry, I should have said that the Console collects all errors, warnings and messages since the program start. To get information about a specific action the Console needs to be cleared before starting it. Take the Consoles content into the clipboard immediately after the action, especially before going to Bugzilla.
Perhaps you might want to check the Console again.
Reporter | ||
Comment 11•15 years ago
|
||
The log was cleared immediately before doing a reply or forward, and all those errors were as a result of that one action.
Reporter | ||
Comment 12•15 years ago
|
||
Pasting errors to Notepad first then to bugzilla.
For a reply
Warning: Unknown property 'mso-margin-top-alt'. Declaration dropped.
Source File: about:blank
Line: 0
Warning: Unknown property 'mso-margin-bottom-alt'. Declaration dropped.
Source File: about:blank
Line: 0
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 6
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 9
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 12
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 15
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 39
Warning: Expected end of value but found 'none'. Error in parsing value for 'text-decoration'. Declaration dropped.
Source File: about:blank
Line: 44
For a forward
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 6
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 9
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 12
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 15
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 39
Warning: Expected end of value but found 'none'. Error in parsing value for 'text-decoration'. Declaration dropped.
Source File: about:blank
Line: 44
Warning: Unknown property 'mso-margin-top-alt'. Declaration dropped.
Source File: about:blank
Line: 0
Warning: Unknown property 'mso-margin-bottom-alt'. Declaration dropped.
Source File: about:blank
Line: 0
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 6
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 9
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 12
Warning: Unknown descriptor 'panose-1' in @font-face rule. Skipped to next declaration.
Source File: about:blank
Line: 15
Warning: Unknown property 'mso-style-type'. Declaration dropped.
Source File: about:blank
Line: 39
Warning: Expected end of value but found 'none'. Error in parsing value for 'text-decoration'. Declaration dropped.
Source File: about:blank
Line: 44
Comment 13•15 years ago
|
||
I seems that you want to create HTML formatted mails. Please switch off the setting Compose messages in HTML format in the Compositions & Adressing settings for this account.
Is the signature a plain file or does it contain HTML? See bug 491706 and bug 531025.
Reporter | ||
Comment 14•15 years ago
|
||
You don't seem to get the point.
Some accounts I would like to reply in HTML. Others in plain text.
All the signature files are plain text.
The same errors are present, no matter which account I use, or
whether HTML is on or not.
When I reply or forward an email sitting in an inbox, no matter how
it got there, common sense is that it should pickup the formatting,
the signature and the from address from the settings in the account
that belongs to that inbox.
Try using the last version of Netscape, it worked perfectly.
Comment 15•15 years ago
|
||
> You don't seem to get the point.
I'm sorry about that and agree with the wanted behaviour you described. But it's easier to confirm bugs which can be reproduced.
To exclude that this error happens because some bad data is involved it is necessary that you create a new Profile under Menu - Tools - Switch Profile - Manage Profiles - Create Profile. Please report your findings.
Comment 16•15 years ago
|
||
With SM 2.0.2pre on Mac I also do not get the signature from the text file.
Build identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8pre) Gecko/20100101 SeaMonkey/2.0.2pre
Reporter | ||
Comment 17•15 years ago
|
||
See comment 7, New accounts already tried.
Comment 18•15 years ago
|
||
Please note the difference between a new account in an existing profile and a new profile. To prove that the bug isn't caused by personal settings it is necessary to create a new profile.
![]() |
||
Updated•15 years ago
|
Flags: wanted-seamonkey2.0?
Comment 19•15 years ago
|
||
Can you try and reproduce with SeaMonkey v2.0.3 ?
Is it diacritics in name file and folders?
Has been Account migrated from SeaMonkey 1.1? If yes, check the signature file in the location.
![]() |
||
Updated•15 years ago
|
Flags: wanted-seamonkey2.1?
Reporter | ||
Comment 20•14 years ago
|
||
Bug still there in Seamonkey 2.0.10 !!!
Comment 21•14 years ago
|
||
Tried to reproduce it with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.17pre) Gecko/20101129 SeaMonkey/2.0.12pre and three mail accounts (1 IMAP, 2 POP3)
I always get the signature included from a text file in all three accounts on reply (for plain and html mails).
For forward I never see a signature included and it doesn't matter if I want to include it from a text file or added it directly in the account settings.
Comment 22•14 years ago
|
||
(In reply to comment #21)
> For forward I never see a signature included and it doesn't matter if I want to
> include it from a text file or added it directly in the account settings.
Oops, forgot to set the pref correctly. With it enabled, I get the signature as well for forwarded messages.
Comment 23•13 years ago
|
||
Is this still reproducible?
Reporter | ||
Comment 24•13 years ago
|
||
Bug still there in Seamonkey 2.3.3 !!!
Comment 25•13 years ago
|
||
Please, try with 2.7a1 nightly from http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-central-trunk/ and include build in your report
Comment 26•13 years ago
|
||
I know this might be painful but could you try a new profile, see http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_SeaMonkey for information about how to transfer data. Always backup before attempting this.
Whiteboard: [Halloween2011Bug]
Version: SeaMonkey 2.0 Branch → SeaMonkey 2.3 Branch
Reporter | ||
Comment 27•13 years ago
|
||
OK, I have gone to the trouble of creating a new profile, and have managed to recover all the information except the form fill modify command in the extensions page freezes.
As regards the email bugs:
I have 4 accounts (plus the local one)
All: Quote the original, Start reply above text, sig below reply, incl sig for replies & forwards. Have tried with a signature file and signature text (same results).
1st Acct: compose in Text
2nd Acct: compose in HTML
I sent myself some emails created in the first two accounts with signatures- all good.
FYI When viewing these received emails, the signature appears dimmed.
When I reply in account 1, the signature part of the received message does not appear, whilst forwarding the message, the signature part does appear. ?
It is editing in text correctly and with the correct from address and signature.
When I reply in account 2, the signature part of the received message does not appear, whilst forwarding the message, the signature part does appear. ?
It is editing in text incorrectly, It should be in HTML.
The From address is also incorrect. It is showing account 1's address, not account 2's address.
The Signature is incorrect. It has used the one from account 1. !
These are the same bugs I have been reporting for over 4 years, and going to all the trouble of building a new profile has not made one bit of difference.
You need to get rid of, or put an option to disable, the reference to the X-Account-Key or whatever is stuffing up the formatting/from addresses/signature selection.
I will only try 2.7a1 if you can guarantee that the problems have been fixed.
R
David
Reporter | ||
Comment 28•13 years ago
|
||
Just discovered a new bug:
When replying to a message in the 2nd account and then changing the
from address to the 2nd accounts email address (by the pull down)
(rather than the incorrectly displayed 1st accounts address),
the correct signature is placed in the message,
BUT the whole forwarded message text is DELETED!!
Comment 29•13 years ago
|
||
(In reply to David from comment #27)
> I will only try 2.7a1 if you can guarantee that the problems have been fixed.
Nobody can guarantee that, we are trying to narrow what is the source of the problem to forward report to appropriate team so it can be fixed. Testing with latest nightly gives the information about issue fix already created, or not. Second step is try to reproduce the issue with latest Thunderbird nightly from http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/ to see, is problem Seamonkey specific or common source related.
Also, just to be sure that I'm not missed something, current Steps to Reproduce:
1) Set up two pop3 mail accounts
2) Set for both of them text signatures on all types of messages (new, reply, forward, etc)
3) Set for first account to compose messages as text, for second as html
4) When you replies from first account, signature appears all time correct
5) When you replies/forwards from second account, signature doesn't appear, but appears on new mail
6) When you replies from first account and changes in compose window account to second, correct signature appeared, but quoted text destroyed.
Am I correct?
Reporter | ||
Comment 30•13 years ago
|
||
1) Set up two pop3 mail accounts
- correct
2) Set for both of them text signatures on all types of messages (new, reply, forward, etc)
- correct
3) Set for first account to compose messages as text, for second as html
- correct
4) When you replies from first account, signature appears all time correct
- When replying to a message sitting in the first accounts inbox, the new signature is added, but the signature in the received message is removed.
When forwarding, it works correctly (keeps the complete original email and adds the signature).
5) When you replies/forwards from second account, signature doesn't appear, but appears on new mail
- When replying to a message sitting in the 2nd accounts inbox, the new signature is added, but the signature in the received message is removed. When forwarding, it works correctly (keeps the complete original email and adds the signature).
It is still not using the correct formatting.
6) When you replies from first account and changes in compose window account to second, correct signature appeared, but quoted text destroyed.- Now that I added multiple identities to the first account, this seems to have been solved.
It is still not using the correct formatting.
Comment 31•13 years ago
|
||
Okay, I'll try to reproduce this tomorrow, to at least the issue be marked as NEW, not unconfirmed.
Can you also provide two screenshots with incorrect and correct formatting?
Reporter | ||
Comment 32•13 years ago
|
||
Please correct me if I am wrong, but I believe the solution is blatantly obvious and very simple:
1 Ignore the X-Account-Key, or add an option to ignore the X-Account-Key
2 When replying to a message, or forwarding a message, use the same subroutine that creates a new message.
That correctly Opens a new edit window
Uses the correct formatting
Uses the correct signature, CC and Bcc addresses
Uses the correct From address
Then copy the ENTIRE contents of the original message, and paste it into the newly created message in the correct spot. (If replying, add the > ).
3 If Replying, set the new 'To Address' to the 'From Address' of the original message.
Done.
Reporter | ||
Comment 33•13 years ago
|
||
You can tell whether the formatting is HTML or not, by noticing whether the pull down boxes and other formatting symbols are present or not.
Comment 34•13 years ago
|
||
(In reply to David from comment #30)
> 4) When you replies from first account, signature appears all time correct
> - When replying to a message sitting in the first accounts inbox, the new
> signature is added, but the signature in the received message is removed.
> When forwarding, it works correctly (keeps the complete original email and
> adds the signature).
Confirming issue on latest nightly, signature of received mail removed on reply
> 5) When you replies/forwards from second account, signature doesn't appear,
> but appears on new mail
> - When replying to a message sitting in the 2nd accounts inbox, the new
> signature is added, but the signature in the received message is removed.
Confirming
> It is still not using the correct formatting.
All fine from my point of view
Build info:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0a1) Gecko/20111017 Firefox/10.0a1 SeaMonkey/2.7a1
Now you can also try to check, if this problem exists in Thunderbird, as I proposed in Comment 29
![]() |
||
Comment 35•13 years ago
|
||
>> - When replying to a message sitting in the first accounts inbox, the new
>> signature is added, but the signature in the received message is removed.
>> When forwarding, it works correctly (keeps the complete original email and
>> adds the signature).
> Confirming issue on latest nightly, signature of received mail removed on reply
This is working as designed. This is intended behaviour. This part of the bug is invalid.
(There is probably a RFC on this)
You need to log in
before you can comment on or make changes to this bug.
Description
•