Bug 84964 - evolution does not include my .signature file in my mails.
evolution does not include my .signature file in my mails.
Product: Red Hat Public Beta
Classification: Retired
Component: evolution (Show other bugs)
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Depends On:
  Show dependency treegraph
Reported: 2003-02-24 08:50 EST by Dams
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-25 15:05:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dams 2003-02-24 08:50:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
When i compose a mail in evolution my .signature does not appears in the  mail
body. There is just a "--" line with nothing under.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. evolution &
2. ctrl-n (for a new mail to send).
3. Select ".signature" for the "Signature:" entry

Actual Results:  the file is not included.

Expected Results:  I should see the ~/.signature file content

Additional info:

My ~/.signature file is not empty.
Comment 1 Jeremy Katz 2003-02-24 12:20:44 EST
What did you set up in your signature preferences under
Comment 2 Dams 2003-02-25 05:12:16 EST
In Settings->Composer->Signature the .signature was an empty signature. So
evolution is surely consistent with itself.
But I think i understand : in evolution 1.0 (like in psyche), there was the
possibility to include a file as a signature. In evolution 1.2 there is no such
ability, instead you can execute a script and make its output as signature. Now,
I think it would be cool to have a default ".signature" signature that would
execute something like a simple `cat ~/.signature`. 
Comment 3 Jeremy Katz 2003-02-25 15:05:33 EST
In 1.0, all that setting to a file did was actually read the file in.  The
default signature behavior in 1.2.x is a simple autogenerated signature.  Any
changes to this would have to be made on an upstream level.

Note You need to log in before you can comment on or make changes to this bug.