Randy Bush | 16 Jul 16:43 2014

how to open local mbox

i have an mbox file fetched off the net.  my localhost, a laptop, is not
running an mta.  i can not open it as a + as it is an mbox.  clue bat


Juliusz Chroboczek | 13 Jul 15:39 2014



I've put some code to add RSS/Atom/OPML support to Wanderlust that is
somewhat simpler to use than the existing shimbun backend on:


Just dump this somewhere in your load-path, byte-compile it, and say
something like:

    m a rss:https://github.com/wanderlust/wanderlust/commits/master.atom

To avoid slowing down Wanderlust, you'll probably want to add "^rss:" to
your wl-auto-uncheck-folder-list.

We don't do any local caching, so if you want to keep a local version of
your notifications, you'll need to use a pipe folder:

    m a |rss:http://lwn.net/headlines/newrss|+lwn

Finally, you can also use a feed as an access group; this is only expected
to be useful with OPML catalogs and syndicated Atom feeds:

    m A rss:http://planet.gnome.org/atom.xml

I'm using this for real work (tracking activity on our local GitLab
instance), and I've been running it with no issues for two weeks now, so
you should expect this code to be reasonably stable.  This is supposed to
handle both RSS variants (1.0 and 2.0), all two of the three Atom variants
(XHTML, double-encoded HTML, but not binary).  There are some formatting
(Continue reading)

Herbert J. Skuhra | 6 Jun 00:41 2014

Invalid base64 data


via a mailing list I received a base64 encoded message with a
signature at the end added by the list software. No multipart!

--- message --- 
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64


You received this mail because you are subscribed to xxx <at> yyy
To unsubscribe, send a mail to: xxx+unsubscribe <at> yyy
--- end ---

Wl fails to display the message with the error:

This entity can't be decoded.  Invalid base64 data

The message displays fine in Gnus. Obviously the fix is in

((eq encoding 'base64)
(Continue reading)

Juliusz Chroboczek | 27 May 15:04 2014

Re: About Wanderlust threading

>>> I wrote the code that modifies msgdb's structure and makes msgdb to
>>> keep multiple parents's Message-IDs.  The code has been committed in
>>> my repository.

Thanks a lot for that, Kazuhiro.  It does exactly what I need, and
it's one of the two patches I'm using that make it painful to come
back to unpatched Wanderlust.  David, I strongly support merging this.

I think you should add a comment to elmo-message-entity-field, to
explain why you're treating the references field specially.  Ditto in

I don't quite agree with your elmo-msgdb-get-references-from-header.
I'd siply say

  (let ((irt (elmo-msgdb-get-message-ids-from-header "in-reply-to"))
        (ref (nreverse (elmo-msgdb-get-message-ids-from-header "references"))))
    (if (and irt (equal irt (car ref)))
      (cons irt ref)))

and kill the variable elmo-msgdb-prefer-in-reply-to-for-parent, which
is no longer useful now that we can handle both fields at the same time.

Thanks again, Kazuhiro, this has made my INBOX much cleaner.

-- Juliusz

Juliusz Chroboczek | 26 May 22:52 2014

Re: IMAP parse error

> elmo-imap4-read-response: Wrong type argument: listp, "IMAP server information: Mailbox is at 90% of quota"

Heh.  Funny.

Please try this (completely untested).

diff --git a/elmo/elmo-imap4.el b/elmo/elmo-imap4.el
index 964dc06..0b9346b 100644
--- a/elmo/elmo-imap4.el
+++ b/elmo/elmo-imap4.el
 <at>  <at>  -1582,8 +1582,9  <at>  <at>  Return nil if no complete line has arrived."
 				  (match-string 2)
 				  (match-string 3))))
 	    ((search-forward "ALERT] " nil t)
-	     (message "IMAP server information: %s"
-		      (buffer-substring (point) (point-max))))
+	     (let ((message (buffer-substring (point) (point-max))))
+	       (message "IMAP server information: %s" message)
+	       (list 'alert message)))
 	    (t (list 'unknown))))))

 (defun elmo-imap4-parse-data-list ()

Markus Huber | 26 May 07:57 2014

IMAP parse error

I got the following message after updating:

IMAP server information: Mailbox is at 90% of quota
elmo-imap4-read-response: Wrong type argument: listp, "IMAP server information: Mailbox is at 90% of quota"

This is the relevant part of elmo's debug messages.

[23:20:06] <-- elmo-imap45 select INBOX
[23:20:06] -> * FLAGS (\Answered \Flagged \Draft \Deleted \Seen $Forwarded)
[23:20:06] -> * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen $Forwarded \*)]  
[23:20:06] -> * 156 EXISTS
[23:20:06] -> * 0 RECENT
[23:20:06] -> * OK [UNSEEN 1]  
[23:20:06] -> * OK [UIDVALIDITY 1270105387]  
[23:20:06] -> * OK [UIDNEXT 1537]  
[23:20:06] -> * OK [NOMODSEQ] Sorry, modsequences have not been enabled on this mailbox
[23:20:06] -> * NO [ALERT] Mailbox is at 90% of quota
[23:20:06] -> * OK [URLMECH INTERNAL]
[23:20:06] -> elmo-imap45 OK [READ-WRITE] Completed
*elmo-imap45* OK arrived
[23:20:06] => ((ok (read-write t)) (unknown) "IMAP server information: Mailbox is at 90% of quota"
(unknown) (uidnext 1537) (uidvalidity "1270105387") (unseen 1) (recent 0) (exists 156)
(permanentflags ("\\Answered" "\\Flagged" "\\Draft" "\\Deleted" "\\Seen" "$Forwarded" "\\*"))
(flags ("\\Answered" "\\Flagged" "\\Draft" "\\Deleted" "\\Seen" "$Forwarded")))
[23:20:11] <-- elmo-imap46 unselect
[23:20:11] -> elmo-imap46 OK Unselect completed.

David Maus | 25 May 09:36 2014

Re: Numbering of draft buffers

At Tue, 20 May 2014 22:05:18 +0200,
Markus Huber wrote:
> > At Tue, 20 May 2014 15:30:05 +0200, Markus Huber wrote:
> > 
> > [...]
> > 
> > I could track the error down to the function `wl-draft-config-info-filename'
> > where the first parameter is `nil'. This parameter gets the value of the symbol
> > `wl-draft-buffer-message-number' when the function is called which is `nil'.
> > 
> > Is there something I can do to further investigate the error?
> > 
> > Thanks for debugging this far. I can reproduce the problem and started
> > to work on a fix. The problem is that you stumbled on the situation
> > where WL cannot obtain the UID of a draft message (via IMAP). That's
> > why the message number is nil.
> > Best,
> >   -- David
> Sorry for the inconvenience. I now know that the problem lies within my setup:
> My `wl-draft-folder' is set to a multi folder for different accounts. I have an
> advice around `wl-draft-save-and-exit' and `wl-draft-send-and-exit' which sets
> `wl-draft-folder' according to the sender address. This didn't work correctly
> but allowed for saving drafts to different accounts. The problem is that the new
> numbering code cannot obtain an UID from the multi folder.
(Continue reading)

David Maus | 25 May 09:30 2014

Re: [PATCH] Implement draft highlighting using jit-lock-mode.

At Tue, 20 May 2014 20:08:21 +0200,
Juliusz Chroboczek wrote:
> The latest version of this code is in the branch jit-lock of
>   https://github.com/jech/wanderlust
> It applies cleanly to current head.
> -- Juliusz

It's on my list of things to review.

  -- David

David Maus | 25 May 09:27 2014

Re: latest wl: multiple breakage for me

At Wed, 21 May 2014 23:59:53 -0600,
Ken Gunderson wrote:
> Hello:
> After updating wl via pacman I had to downgrade due to inability to
> compose message w/o following error:
> elmo-imap4-accept-ok: IMAP error: Missing required argument to Append command
> IMAP error: Missing required argument to Append command
> Also, search summary view for messages matching e.g. From header
> "foo" no longer works.  Error reported is as follows:
> elmo-imap4-process-bye: IMAP4 session was terminated: "Fatal error:
> word too long", "Try Again"
> So I just pulled from e6h "melpa" and get same.  I need to roll this
> back to Arch's wanderlust-20140210-1 pkg so cannot debug/troubleshoot
> further.  

Thanks for reporting. Do you know what IMAP server software is running
on the host you get the "word too long"-error from?

  -- David

> Best-- Ken
(Continue reading)

Kazuhiro Ito | 18 May 01:44 2014

Re: About Wanderlust threading


> I'm finding Wanderlust's threading somewhat deficient.  In particular,
> Wanderlust appears unable to stich incomplete threads -- threads in
> which one or more messages are missing.  For example, most
> conversations I have consist of odd-numbered mails in my %Sent folder,
> and even-numbered ones in my %INBOX; Wanderlust presents the latter as
> separate messages.  (Yes, I know about wl-summary-search-parent-by-subject)

I wrote the code that modifies msgdb's structure and makes msgdb to
keep multiple parents's Message-IDs.  The code has been committed in
my repository.  Old Wanderlust can load new msgdb without any error,
but will fail to build thread.  If you want to rebuild thread
structure with the new feature, rebuild msgdb.


Kazuhiro Ito

Nick Lanham | 16 May 18:48 2014

Cannot parse IMAP command after update

After updating to wl 20140515, I get errors saying "Cannot parse IMAP command" when I try to do things like
reply to a message (I think it's in trying to fetch the message to quote it).  Downgrading to 20140210 seems
to fixed the issue.

Any ideas on why this might be and/or how I can debug what's going on?