search

deanproxy / eMail

Command line SMTP client
https://www.deanproxy.com/code
GNU General Public License v2.0
135 stars 46 forks source link

Signature specification #17

Open mined opened 9 years ago

mined commented 9 years ago

Configuration option SIGNATURE_FILE apparently provides no way to refer to my home directory; SIGNATURE_FILE = $HOME/.signature.email (or quoted) does not work.

Configuration option SIGNATURE_DIVIDE does not work; email says: email: FATAL: Variable: '▒▒▒d' is not valid

deanproxy commented 9 years ago

For home directory, use the identifier ~. So on your case ~/.signature.email

SIGNATURE_DIVIDE was removed a few versions ago as it made more sense to add whatever divider you wanted inside of the signature file itself. I might have not removed all traces of that option from the docs...

mined commented 9 years ago

Oh, so I was hit again by the issue that ~ is not expanded as $HOME by email (likewise it does not use $HOME/.email.conf). The only other application I encountered that does this is openssl. All others use $HOME to refer to configuration files. This has a potential of confusion. Note that $HOME being different from getpwuid (getuid ())->pw_dir may not be typical for Unix systems but it is more likely on cygwin where users may wish to share a home directory among cygwin and Windows environments.

deanproxy commented 9 years ago

Okay. I see what you mean. Unfortunately I don't have Cygwin to test on. I can make a patch for this but I will not be able to test it.

mined commented 9 years ago

You can simply test by changing HOME to some other directory (or unsetting HOME for a null test). (People may do that on Unix systems too occasionally for reasons similar to using chroot.)