Neal H. Walfield | 25 Mar 15:11 2015

TLS: checking a self-signed certificate


I've just upgraded to Debian Jessie.  When I connect to my mail
server, gnutls now complains that it can't verify the server's
certificate ("The certificate is NOT trusted.  The certificate issuer
is unknown.").  I don't want to enable insecure mode as I've
apparently been using so far.  Instead, I want gnutls to check the
certificate, which I have saved locally.  I can't figure out how to do
that, however.  I suspect that it has something to do with
'ssl-program-arguments', but I can't figure out the magic incantation.
I thought I could just pass --x509certfile /home/us/mail.pem, but I
get the same error.  Anyone have any ideas?



John Morris | 17 Mar 19:58 2015

Default Address with multiple Addresses

Dear all,

I have the standard multiple-account setup via
`wl-user-mail-address-list', but although invoking ‘W’ from the folder
buffer will start a draft from the correct folder (via
wl-draft-parent-folder), if I start composing with C-x m I am by
default sending from $LOGNAME <at> $HOSTNAME, which does not exist.  I can
select a new template with C-c C-j, at which point it behaves as
expected, but if I forget to do that I lose the email on sending to
some undisclosed Valhalla for unsent messages.

Is there any way to have the default buffer set a valid email address?
I have user-mail-address set, but that makes no difference...

I can provide details of the config if required, but it’s straight of

Many thanks,


Michael Welle | 10 Mar 10:36 2015

Error opening multipart messages


I have lots of multipart messages, e.g. messages that contains a text
part and alternatively an html part. WL has trouble to open some of
them and bails out with end of file during parsing. I think the
problem is in the content type declaration of one of the parts:

Content-Type:  text/plain;  charset=utf-8 
Content-Transfer-Encoding: base64

This declaration has a blank after the string utf-8, which causes the
error. Can wl be more forgiving here or is it against the standard and
up to the sender to fix this?

Some of the affected messages are really old. So the problem could be
a regression somewhere on WL's path.



biff4emacsen - A biff-like tool for (X)Emacs
Flood - Your friendly network packet generator

Greg Bognar | 3 Mar 00:40 2015

Warning (elmo): Please set `wl-message-id-domain' to get valid Message-ID string.

I have two computers which use the same wl config.

On one of them, a laptop, I get "Warning (elmo): Please set
`wl-message-id-domain' to get valid Message-ID string" every time I start
wl.  On the other, a desktop in the office, I don't.

The warning does not seem to cause any problems in using wl.  It's just

I have vague recollections that this has come up before, but a Google search
did not turn up anything useful.

Can someone explain what this is, and how I can solve it?  To what (and how)
should I set wl-message-id-domain?


Taku.YAMAMOTO | 6 Feb 02:43 2015





山本 琢

Zip Random | 4 Feb 13:50 2015

ziprandom <at> is added to <wl <at>>

To: wl-ctl <at> 
Message-Id: <87d25pyh6f.fsf <at>>
X-ML-Name: Wanderlust
X-Mail-Count: 14626
X-MLServer: fml [fml 4.0 STABLE (20040215/4.0.4_BETA)]; post only (only members can post)
X-ML-Info: If you have a question,
	please contact wl-admin <at>;
	<mailto:wl-admin <at>>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113;
X-Received: by with SMTP id dr11mr4339373wid.40.1423054197274;
        Wed, 04 Feb 2015 04:49:57 -0800 (PST)
Mime-Version: 1.0
Content-Type: text/plain
Precedence: bulk
Lines: 3
List-Subscribe: <mailto:wl-ctl <at>>

     $B%a!<%k%"%I%l%9(B: <ziprandom <at>>

confirm 2015020421433743741670121702 Zip Random
(Continue reading)

Taku.YAMAMOTO | 1 Feb 03:59 2015





Michael Welle | 30 Jan 18:12 2015

Mail encryption, possible problem with SEMI


I discovered strange behaviour while trying to encrypt mails (Emacs
24.4.1, SEMI is the current version from the melpa archive). The key
ids that are fed to gpg are mostly totally unrelated to the mail's
recipient. The problem seems to be in mime-edit.el. In
mime-edit-encrypt-pgp-mime a recipient list is calculated. A to-header
like 'foo bar <foo <at> a.b>' is therefore parsed into three elements 'foo',
'bar' and 'foo <at> a.b', which results in three key ids (depending on the
contents of your key ring). Unfortunately, the key ids resulting from
'foo' and 'bar' are unrelated to this mail in my case (tons of
different keys can be found for foo). And even the key found for
foo <at> a.b might not be the one one want to use.

As a work around one can use plain mail addresses like 'foo <at> a.b'.


John Morris | 22 Jan 19:48 2015

Change ‘AT <date> <USER> wrote:’

...which is bad English.

Presumably there’s some variable to customise, to change the string
placed before the citation when doing reply-with-citation, but I can’t
find it....

Apologies if this is trivial.

many thanks,


James Harkins | 20 Jan 03:10 2015

Re: IMAP process hanging Emacs, or just failing

At Mon, 19 Jan 2015 19:12:51 -0500,
Thomas Narten wrote:
> You might also delete/empty your cache. I'm pretty sure you can delete
> all of .elmo/cache if not .elmo w/o losing mail.  You could easily
> just move the directory somewhere else temporarily, try things, and
> then restore if it doesn't help.

Indeed, "rm -rf ~/.elmo/cache" resolved the problem.

So, there's a bug in elmo?

> And there are some explicit cache expiration stuff you can do. Poke
> around with wl-summary-delete-cache and the like (all undocumented
> sadly).

I remember having problems with one of the automated cleanup functions in the past. I use rsync to back up my
user data, which sets each file's "last-accessed" time, and that makes the automated cleanup fairly
useless (since none of the mail files have been untouched long enough to expire).

In any case, thanks for the tip about the cache. WL is working again here!


James Harkins | 19 Jan 03:46 2015

IMAP process hanging Emacs, or just failing

I'm sending this from webmail, not wanderlust (as I would prefer), because at the moment, wanderlust's attempts to contact the IMAP server are doing nothing except causing Emacs to consume 100% CPU on one of the cores.

I've seen this happen many times before, usually when the connection has been idle and it's trying to open a new connection. Usually I can resolve the problem by doing M-t twice (forcibly kill the old connection, and open a new one).

Today, however, this didn't help. Neither did closing Emacs entirely, relaunching, and restarting wl.

First relaunch of Emacs: in the Folder buffer, updating folder statistics cause an infinite loop.

Second relaunch of Emacs: Folder buffer, the same operation stops abnormally with the message "Process IMAP is not running."

How do I even begin to troubleshoot this? I really don't want to have to go back to *shudder* Claws mail...

Linux hjh-e431 3.11.0-26-generic #45~precise1-Ubuntu SMP Tue Jul 15 04:02:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

This is GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2) of 2014-02-22 on king, modified by Debian

Wanderlust 2.15.9 from el-get.