On 25.09.2007 (01:10), Jiang Qian wrote:
I'm sure we can write some kind of poor man's python script or
shell/sed/awk script to add or remove address from this. You can then
invoke this on the BCC field.
But the question was how to make them appear, one by one, in separate
mails, in the TO
On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
There was a thread a short while ago about non-ascii characters in the
From name during which I changed my name from Oestrem to Østrem, and
it works.
Today, I happened to find one of my own messages in a search of the
list at
On Tue, Sep 25, 2007 at 10:03:30AM +0200, Eyolf Østrem wrote:
Eyolf =?iso-8859-1?Q?=D8strem?= eyolf () oestrem ! com
RFC 2822 (is that the right number?) does not allow non-ascii characters
in headers, and there is another RFC that describes how to encode
non-ascii characters in headers.
On 25.09.2007 (04:13), Jiang Qian wrote:
Not so nice to look at... Is there still some setting I should
make/change, or is this down to marc.info's inability to handle
unicode characters?
Your name appears(including Ø) fine on my mutt display. My default
encoding is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 10:03 AM, quoth Eyolf Østrem:
Eyolf =?iso-8859-1?Q?=D8strem?= eyolf () oestrem ! com
Not so nice to look at... Is there still some setting I should
make/change, or is this down to marc.info's inability to handle
On 25.09.2007 (09:02), Kyle Wheeler wrote:
The answer is, unfortunately, no. There's no way to specify
alternatives in your From header. Plus, even if there was, it's
doubtful that marc.info would support them, given that it doesn't seem
interested or capable of decoding the existing RFC.
On Mon, Sep 24, 2007 at 10:59:05PM -0500, Kyle Wheeler wrote:
...
Thank you very much for your help... Now everything works
right. I have greatly appreciated your input.
Franz
On 25-09-2007, at 10h 03'30, Eyolf Østrem wrote about More on non-ascii chars
in headers
Not so nice to look at... Is there still some setting I should
make/change, or is this down to marc.info's inability to handle
unicode characters?
Eyolf Østrem/Oestrem/=?iso-8859-1?Q?=D8strem?=
That is
I've seen an interesting sidebar patch for mutt, though it was just that
a patch is not new and was never implemented.
I am just curious as to the reason why it was never implemented.
--
#Joseph
I know procmail is used to sort an incoming mail but what about outgoing
mail.
Can I use procmail for sorting outgoing mail or I need to use hooks?
--
#Joseph
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 11:16 PM, quoth Ionel Mugurel Ciobica:
Eyolf =?iso-8859-1?Q?=D8strem?=
That is not Unicode. Unicode would be this:
| Eyolf =?UTF-8?Q?=C3=98strem?=
This is the (safe) way to transfer non-ASCII information over the net.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 04:54 PM, quoth Joseph:
I've seen an interesting sidebar patch for mutt, though it was just that
a patch is not new and was never implemented.
I am just curious as to the reason why it was never implemented.
Eh? It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, September 25 at 08:29 PM, quoth Joseph:
I know procmail is used to sort an incoming mail but what about outgoing
mail.
Can I use procmail for sorting outgoing mail or I need to use hooks?
Procmail is a delivery agent; it only handles
13 matches
Mail list logo
