Closed Bug 16708 Opened 26 years ago Closed 19 years ago

signature doesn't work from -compose

Categories

(SeaMonkey :: MailNews: Account Configuration, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: akkzilla, Unassigned)

Details

Needing to test an editor bug involving mail signatures, I highlighted the profile I normally use, selected Account Setup, and clicked the checkbox next to "Attach this signature". But it wasn't clear what should go in the text field -- the actual signature, or a path to a signature file? I created a file containing the text: <br> <i>...Akkana</i><br> and set my signature to be the path to that file (/u/akkana/.mozsig). When I then click New Msg to start up a compose window (looks like plaintext though my pref says use html, so I'm not sure which one it really is), I get the "-- " line but no "Akkana" text. This set the following two prefs: user_pref("mail.identity.id1.attach_signature", true); user_pref("mail.identity.id1.sig_file", "/u/akkana/.mozsig"); If I put the above html snippet directly into the text field in the account manager dialog, I don't even get the "-- " line and when I go back into the account manager, I see it's prepended the current directory, so that's obviously not what it expected either. I also tried editing my prefs (as listed above, set to point to the file) to use id0 instead of id1, in case id0 was always used for sending mail; but then the "-- " line was not appended either when clicking New Msg from the 3-pane window, or when running apprunner -compose from the command line.
Blocks: 16706
You have set up everything correctly (and yes, that is a filename you're supposed to enter there, you're right, it's pretty vague) - there are a few possible user errors here, but it also could be a bug. - When you open the compose window, it looks to see if you're selecting any folders in the folder pane. If you are, it tries to find the corresponding identity for that folder. If you are not, then it just selects the first identity. - The signature is actually inserted into the editor when the compose window starts up, based on the identity chosen (above), so once the window is up, you already have a signature.. and even if you switch identities with the combo box in the compose window, you'll keep the initial signature that was in the compose window when it opened. - the other trick is that HTML signatures need to have a .htm or .html extension to be treated as html.. otherwise they are treated as plaintext. I don't know how it behaves if you put HTML in a non-html signature though. (rich?) the "--" makes me think that it is in fact finding the signature. Does any of the above help at all? one wierdness I've noticed is that if you enter a non-existant file in the signature textbox there, it creates a DIRECTORY with the given name, which is kind of screwed up (it's actually nsFileSpec that's doing that I think) Let me know if this helps any, maybe we can narrow it down.
QA Contact: lchiang → nbaca
Alex writes: "- When you open the compose window, it looks to see if you're selecting any folders in the folder pane. If you are, it tries to find the corresponding identity for that folder. If you are not, then it just selects the first identity." There may be some issues when a folder / server is not selected prior to bringing up a compose window. See: http://bugzilla.mozilla.org/show_bug.cgi?id=15238
I "do the right thing" with signatures. If it has an HTM or HTML extension and you are in plain text mode, it will convert your HTML to plain text. - rhp
QA Contact: nbaca → lchiang
Yes, that helped -- needing the .html extension was at least part of it. Now I can get an html signature on outgoing mail for id1 (when I bring up the 3 pane window, highlight an identity and click New) but I still don't get anything for apprunner -compose, even when I set the same prefs for id0 that I had for id1. id0 is the smtp id, right? I saw the "erase the file and create a directory of that name" bug too (I had the file in the wrong place for part of the testing).
Status: NEW → ASSIGNED
Summary: can't set up signature via account setup → signature doesn't work from -compose
Target Milestone: M12
No longer blocks: 16706
ok, I'm going to keep this bug as it is now, but use the momoi bug (above) as a reference. I'm breaking the dependancy though, since akkana was able to make headway
Target Milestone: M12 → M13
Target Milestone: M13 → M16
moving non-critical bugs to M20
Target Milestone: M16 → M20
massive reassign of account manager bugs -> sspitzer please feel free to put me back on the CC if you have any questions/comments
Assignee: alecf → sspitzer
Status: ASSIGNED → NEW
compose related, adding jfd.
mass re-assign of account manager bugs to racham.
Assignee: sspitzer → racham
Status: NEW → ASSIGNED
Target Milestone: --- → Future
QA Contact: lchiang → nobody
mass re-assign.
Assignee: racham → sspitzer
Status: ASSIGNED → NEW
Product: Browser → Seamonkey
Assignee: sspitzer → mail
Akkana Peck, is this (very old) bug still a problem for you? Seamonkey 1.0 WFM under Win2K.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Akkana Peck, is this (very old) bug still a problem for you? Seamonkey 1.0 WFM under Win2K.
Sorry, marked Fixed accidentally.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Sorry, I don't have seamonkey mail installed and configured so I can no longer test this. Though I guess that answers the question -- whether it's fixed or not, it's no longer a problem for me.
OK, then => WFM
Status: REOPENED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.