Re: paranoic gpg settings and /tmp
On Wed, Dec 08, 2010 at 06:50:26PM -0800, Brandon Sandrowicz wrote: On Wed, Dec 08, 2010 at 11:35:07PM +0100, Francesco de Virgilio wrote: - Ubuntu 10.10 - /home encrypted with ecryptfs - /tmp is a directory clearly readable by anyone having access to my hard disk Question: when I decrypt a message sent to me using GPG, is it immediately printed on the standard output (my shell) or is a _decrypted_ copy created in /tmp and deleted after closing the message? You could try setting $TMP or $TMPDIR (which mutt may or may not respect) to a directory like $HOME/tmp, which is already encrypted. There's also. for .muttrc: set tmpdir=~/tmp# where to store temp files At least I have that, it works, and mutt doesn't bitch at start time about unknown config. In general I think it's a good idea to set TMP and TMPDIR to ~/tmp anyway. If you have a GOOD reason to want to have such on actual /tmp (faster local disk instead of NFS disk?) then I'd recommend some shell startup scripting to attempt to make /tmp/user/, and set TMPDIR to that, bitching if it can't ensure it exists, is owned by you, and chmod 700. -- - Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/ Finger athan(at)fysh.org for PGP key And it's me who is my enemy. Me who beats me up. Me who makes the monsters. Me who strips my confidence. Paula Cole - ME signature.asc Description: Digital signature
Re: paranoic gpg settings and /tmp
On Thu, Dec 09, 2010 at 10:14:55AM +, Athanasius wrote:
In general I think it's a good idea to set TMP and TMPDIR to ~/tmp
anyway. If you have a GOOD reason to want to have such on actual /tmp
(faster local disk instead of NFS disk?) then I'd recommend some shell
startup scripting to attempt to make /tmp/user/, and set TMPDIR to
that, bitching if it can't ensure it exists, is owned by you, and chmod
700.
Aha, here's my example, I Was looking in the wrong host's ~/.bashrc.
Yes it's generating ${HOME}/tmp in this example, and is a bit overkill
for that, but I copied it from similar for /tmp/${USER}. Adjust to
taste.
## Try to guarantee a 'good' /tmp directory for me
MYTMP=${HOME}/tmp
if [ ! -d ${MYTMP} ];
then
if [ -e ${MYTMP} ];
then
rm -f ${MYTMP} 2 /dev/null
fi
mkdir ${MYTMP} 2 /dev/null
fi
if [ ! -O ${MYTMP} ];
then
echo Warning, someone else owns ${MYTMP} !
if [ ! -d ${MYTMP} ];
then
echo And it isn't a directory either.
fi
mail -s /tmp problem athan END
Problem with ${MYTMP}
END
export TMPDIR=/tmp
else
chmod 700 ${MYTMP}
export TMPDIR=${MYTMP}
export LYNX_TEMP_SPACE=${MYTMP}
fi
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence. Paula Cole - ME
signature.asc
Description: Digital signature
Re: New tool for sending HTML mail with Mutt
Nicolas Williams nicolas.willi...@oracle.com [2010-12-08 13:25 -0600]: On Wed, Dec 08, 2010 at 09:17:02PM +0200, Amit Ramon wrote: Chip Camden sterl...@camdensoftware.com [2010-12-08 11:01 -0800]: On a related topic, is there any way to get mutt to display RTL for certain characters? The Hebrew characters in your signature, for instance, are displayed LTR in my mutt, so they read backwards. Not directly. For that you have to use a bidi-aware terminal. I'm running Mutt in Mlterm terminal emulator, which can handle LTR and RTL quiet well (but not perfectly). I agree, this is a job for the rendered, which is also why you shouldn't need your plain2html program -- the web browsers displaying your email in webmail apps should handle bi-di correctly as long as they understand UTF-8. Might the webmail backend be doing something wrong? I don't agree... web browsers are not supposed to be able to know how to render bidi text. For this reason there are dir tags in HTML. Webmail backends are also not doing it. This is not the same as understand UTF-8. How would I know if the Hebrew text in your signature is displaying correctly? The glyphs appear to be correct. Would inserting spaces between the characters change the order in which they appear? If so, my terminal (Terminator) is not handlint bi-di correctly :( The first Hebrew letter in my first name is Ayn, which looks schematically like this: # # # # # # ## # # # # # # ## In a correct appearance you should see it at the rightmost place on the line that has my first name, Amit, in my signature... if it follows the word Amit immediately after the blank space, the terminal does not support bidi. -- :: Amitעמית Ramon רמון
Re: New tool for sending HTML mail with Mutt
On Thu, Dec 09, 2010 at 07:25:11PM +0200, Amit Ramon wrote:
Nicolas Williams nicolas.willi...@oracle.com [2010-12-08 13:25 -0600]:
On Wed, Dec 08, 2010 at 09:17:02PM +0200, Amit Ramon wrote:
Chip Camden sterl...@camdensoftware.com [2010-12-08 11:01 -0800]:
On a related topic, is there any way to get mutt to display RTL for
certain characters? The Hebrew characters in your signature, for
instance, are displayed LTR in my mutt, so they read backwards.
Not directly. For that you have to use a bidi-aware terminal. I'm
running Mutt in Mlterm terminal emulator, which can handle LTR and RTL
quiet well (but not perfectly).
I agree, this is a job for the rendered, which is also why you shouldn't
need your plain2html program -- the web browsers displaying your email
in webmail apps should handle bi-di correctly as long as they understand
UTF-8. Might the webmail backend be doing something wrong?
I don't agree... web browsers are not supposed to be able to know how
to render bidi text. For this reason there are dir tags in
HTML. Webmail backends are also not doing it. This is not the same as
understand UTF-8.
I'm not too familiar with bi-di, and I can see that a dir tag does exist
for HTML. We seem to agree that terminals (which have no HTML-like
tags) are supposed to figure out how to render bi-di correctly. Looking
around a bit I see that there are three standard ways to indicate
direction changes:
- Use Unicode control characters, most of which are discouraged, except
for the right-to-left and left-to-right marks (which are for
specifying direction for weak-directional characters relative to
surrounding strong-directional characters);
- Use HTML dir attribute or bdo element;
- Use CSS rules ('direction' and 'bidi-override' props).
The last two are for HTML docs only. The first one is the only one that
works in all contexts, while markup solutions based on anything other
than Unicode require tags/attributes to be defined.
But there is a Unicode bi-di algorithm... From what I can tell,
renderers that implement it should not require marks (except for
weak-directional characters, as mentioned above).
How would I know if the Hebrew text in your signature is displaying
correctly? [...]
The first Hebrew letter in my first name is Ayn, which looks
schematically like this:
[...]
In a correct appearance you should see it at the rightmost place on
the line that has my first name, Amit, in my signature... if it
follows the word Amit immediately after the blank space, the terminal
does not support bidi.
Indeed, my terminal is not displaying those in right-to-left. I see
that some applications do display properly (for example, the Bluefish
editor does, but vim/gvim does not).
Nico
--
Re: Avoiding duplicate messages
Solved it adding to .muttrc set copy=no Hope it can be usefull for someone. Regards, jm On Wed, Dec 8, 2010 at 6:18 PM, Jose M Vidal jmvidal...@gmail.com wrote: All my outgoing e-mails (new messages and replies) appear as two messages in mutt (Gmail IMAP) When I check the web client they all are dupicated as well. I've seen some messages in this list explaining how to remove duplicate messages (D + ~=), but my problem is: 1- It is inconvenient to do it every X messages, to keep the Sent messages folder clean 2- When doing it, I need to remove every time the folder-hook . 'unset trash' line from muy .muttrc, as I am used to archive my mail instead of deleting it. Is there anything I can do to avoid getting all my outgoing mail duplicated? Many thanks. -- jm -- jm
