Re: Thank you for Mutt
On Tue, Jul 24, 2012 at 04:12:22PM +, John Long wrote: > Mutt is a great app! It doesn't suck at all. Hmmm. I'm going to disagree a bit. I think Mutt is a fine MUA, and I use it for all of my personal and professional mail, but it definitely has some baggage that sucks. - IMAP support causes segfaults with 1.5.21. Regularly. - Local commands, such as 'c' to change mailboxes, can take ages, even though all the mailboxes are cached. - All around, it's slow. Even with caching. - Inconsistent keyboard shortcuts. First it's 'i' that exits, then 'y' then 'q', and so on. - No sidebar support (outside of an unofficial patch) for viewing your mailbox tree. - No vertical layout for viewing messages with widescreen monitors.. - No ability to change signatures when changing accounts automatically. - No RSS/Usenet support. There are other things that irk me, but those are probably the heavy hitters. Despite that, I find Mutt to be a good all-alround MUA, which I use daily (have for years), but you won't find me saying it doesn't suck. It certainly has its issues. :) -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o pgpqcPHlrrlXP.pgp Description: PGP signature
Re: Mutt eating the tab character in headers
On Fri, May 25, 2012 at 10:50:07AM -0500, Derek Martin wrote: > There's a lot to wade through, but the answer is here: > > http://dev.mutt.org/trac/ticket/2995 > > It turns out this is kind of hard to get exactly right. Paying closer attention to some other headers, it appears that some software uses the , some use a single , and some use 8 . Also, RFC 2822 only mentions what happens on the unfold, not how a fold itself should be created, although I can understand the argument on why a would be "a bad idea". At any event, it doesn't appear that there is any standard on the matter, so I'll adjust to Mutt's default behavior, now that I understand it a bit better. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: Mutt eating the tab character in headers
On Fri, May 25, 2012 at 03:24:38PM +0100, Chris Burdess wrote: > I would think that it doesn't actually matter whether mutt does this or > not, since any intervening MTAs are free to do this as they want. As > long as the result is valid RFC822, header whitespace may be changed or > whatever. Only the values are significant. I certainly agree. I guess I'm more or less curious why is being replaced by - what the logical argument is. Is the character not a valid character in mail header fields as defined by the RFCs? -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Mutt eating the tab character in headers
I have an "easter egg", if you will, in the header of my mail. I have two headers that I am adding: "Crypto-Challenge" and "Crypto-Hint". It's all for fun and games. However, in my muttrc(5), I am wrapping each line (It's rather lengthy otherwise) and preceding the newline with a character. It shows up fine when I compose my mail, but when saving, Mutt converts the to a (as you can see in the headers of this mail). For those who don't want to examine the mail headers, here are two pastebins of what I'm talking about. This: http://ae7.st/p/42a turns into this: http://ae7.st/p/5f8. I guess it doesn't really matter, except when viewing headers, other line wrapping is preceded by a , and Mutt displays it accordingly. So, why is Mutt converting my ta a ? Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o pgp6QAitE8UPN.pgp Description: PGP signature
Re: mutt and gmail's two step authentication
On Fri, Apr 06, 2012 at 09:32:50PM +0200, Ђорђе Тодоровић wrote: > Is anyone here using Gmail's two factor authentication with mutt (and/or > offlineimap), and how? Is it possible to use "Application specific password" > [1] in mutt to authenticate mutt with one's Gmail account? Yes, I am using Google's two factor authentication without problem. I store the application-specific password in a GPG-encrypted file, which I have Mutt decrypt when accessing the account. I am using GnuPG v2 with gpg-agent(1). Everything works as it should. > On a related note, does anyone know if offlineimap supports the same feature. I don't use offlineimap, so I can't comment here. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o pgp7fdlmH1LDl.pgp Description: PGP signature
Re: Subscribed folders and IMAP IDLE help
On Fri, Jan 13, 2012 at 07:05:25AM -0700, Aaron Toponce wrote: > Second, with "imap_check_subscribed" set, and in the Mailboxes view, if any > folders are created on the server, they are not visible in the Mailboxes > view. Pressing 'T' to "toggle-subscribe" folders to view unsubscribed > folders does not seem to work. So, in order to even view this folder in > Mutt, I must pull up Thunderbird, right click the folder, and subscribe to > it in the context menu. Only then, will the folder become visible in the > Mailboxes view. So, how do you subscribe to folders that you can't even see > in the Mailboxes view, when the toggle is clearly not working? I would > press 's' to subscribe, but it's not listed to operate against. It appears that 'c?' will list all directories on the server, subscribed or not, and from there, I can press 's' to subscribe to the folder that is not currently subscribed to. Pressing 'y' from the index indeed shows the newly subscribed folder. It would be nice to learn why 'T' is not toggling subscribed/unsubscribed in the Mailboxes view, however. Is this a bug? Still curious about the other questions I had starting this thread. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o pgpryogMxRrND.pgp Description: PGP signature
Subscribed folders and IMAP IDLE help
I have Mutt configured to talk via IMAPS/SMTPS to a Zimbra server. Everything is working fine, exept for managing subscribed folders and the Mailboxes view. I'm running 1.5.21 on an updated Debian Sid box. First, unless I have "imap_check_subscribed" set, I cannot view the Mailboxs by pressing 'y' from the index or 'c?'. It hangs making the attempt, it seems. I can change folders manually, however. Second, with "imap_check_subscribed" set, and in the Mailboxes view, if any folders are created on the server, they are not visible in the Mailboxes view. Pressing 'T' to "toggle-subscribe" folders to view unsubscribed folders does not seem to work. So, in order to even view this folder in Mutt, I must pull up Thunderbird, right click the folder, and subscribe to it in the context menu. Only then, will the folder become visible in the Mailboxes view. So, how do you subscribe to folders that you can't even see in the Mailboxes view, when the toggle is clearly not working? I would press 's' to subscribe, but it's not listed to operate against. Third, unrelated to subscriptions, but if the server supports IMAP IDLE, which this Zimbra instance does, then are the "mail_check" and "timeout" variables even needed? If so, why? Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o pgpBWCSEh7e9K.pgp Description: PGP signature
Pager wrapping bug
I have some colors setup for the pager, such as header, nested replies, etc. As a result, the following gives some interesting results: :set wrap=10 :set wrap=0 Some of the lines in the pager have the wrong color applied to them. Is this a known issue? -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: Unmarking new unread messages as N
On Thu, Dec 15, 2011 at 06:03:32PM +0100, Jostein Berntsen wrote:
> > I frequently check the mutt index for new messages (marked "N"). I
> > mark some to be deleted ("D"), but put off reading other new messages
> > until I can break from work at some point in the course of the day in
> > order to process them all at one time. So I would like to change the
> > new ("N") status of those messages to (" ") without having to view
> > their content. Can this be done?
>
> You should be able to do this by doing "N" on the new message.
You can also do ^r (ctrl+r) to mark an entire thread as read.
--
. o . o . o . . o o . . . o .
. . o . o o o . o . o o . . o
o o o . o . . o o o o . o o o
signature.asc
Description: Digital signature
[SOLVED] Re: Alias tab completion not working
On Sun, Oct 30, 2011 at 10:11:03PM +0100, Rado Q wrote: > Your mutt-version supports mutt-var-expansion? Yes. > Define at run-time a temporary alias, then TAB-expand it to get a > list of _all_ defined aliases. > If none exists beyond the temporary, you file is not slurped. I got everything working. Here's what I did: ~/.muttrc: folder-hook "gmail.com" "source ~/.mutt/gmail.rc" folder-hook "example.com" "source ~/.mutt/work.rc" source ~/.mutt/gmail.rc # open gmail on startup ~/.mutt/gmail.rc: bind editor complete-query bind editor ^T complete set query_command = "goobook query '%s'" ~/.mutt/work.rc: bind editor complete # default Mutt setting bind editor ^T complete-query # default Mutt setting unset query_command # default Mutt setting source ~/.mutt/work_aliases Notice the differences between the key bindings for "complete" and "complete-query" in the different RC files. Also note that I'm unsetting "query_command" in my ~/.mutt/work.rc. This was necessary to tab complete the aliases out of the ~/.mutt/work_aliases file. Hope this is helpful to someone else. I'm sure this is only helpful to a very small subset of users, but I wouldn't be doing my due diligence if I didn't post it. https://xkcd.com/979/ seems relevant. Sorry if you read my blog, or follow me on Google+, but it seemed most appropriate to post here as well. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Alias tab completion not working
I am using Mutt with two IMAP accounts: Google, and work. I have separate RC files for each account. With Google, I am using 'query_command' to query my Google Contacts with goobook(1). For work, I have setup an alias file, with the necessary aliases. Here are the relevant parts of that RC: # file: ~/.mutt/work.rc unset query_command # unset query_command from ~/.mutt/google.rc set alias_file="~/.mutt/work_aliases" set reverse_alias=yes set sort_alias=alias source $alias_file source ~/.mutt/work_lists I've unset 'query_command' to make sure I'm not using goobook(1) to query my Google Contants, and just to query the "work_aliases" file. Yet, whet composing a message, I cannot tab complete the aliases in that file. You'll also notice that I have mailing list definitions setup. Those work fine when pressing 'L' to respond to a mailing list. What am I missing to get my work aliases working? Is there something else I should unset from my ~/.mutt/google.rc config (or my ~/.muttrc for that matter)? Any help is greatly appreciated. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: IMAP fetch header failed
On Mon, Oct 24, 2011 at 05:31:45PM +0800, du yang wrote: > I search a lot about the "tls_socket_read" problem. It's caused by SSL > connection time out or broken. In my case, I tuned mutt with many > timeout parameters but without success. If mutt's no problem, the > connection may be disconnected on server end or the ISP's > firewall. The "tls_socket_read" connection issues are related to GnuTLS. If you recompile Mutt with OpenSSL instead, those errors go away. Might be worth looking into if it's a big issue for you. > Your case said gmail has no problem, so the problem should reside in my > ISP's firewall. Possible. Again, running tcpdump(1) should be the first thing you do when troubleshooting a network-related issue, rather than trying to find some error in your config. Just a thought. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: IMAP fetch header failed
On Mon, Oct 24, 2011 at 02:17:23AM -0700, Michael Graham wrote: > Then perhaps Du Yang’s problem was caused by a bad/dropped connection? Possibly. A tcpdump(1) could tell for sure. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: IMAP fetch header failed
On Sun, Oct 23, 2011 at 11:54:06AM +0100, Michael Graham wrote: > I’m with Stardiviner on this one: I don’t think this *is* really a fault > in mutt. I don’t think mutt was designed to handle that many emails in a > single folder I disagree. Mutt seems to be to be designed around those who have tens or hundreds of thousands of mail that they need to work through. The key bindings make working through folders, accounts, the pagere, etc. a snap. Searching and limiting mail is painless (although better tools exist). For someone who has over 70,000 email messages in their account, Mutt is the only way to go. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: IMAP fetch header failed
On Sun, Oct 23, 2011 at 02:02:01PM +0800, stardiviner wrote: > => On [2011-10-23 10:56:38 +0800]: du yang Said: > > I have a gmail INBOX with more than 20,000 messages. I configured mutt > > IMAP to this mailbox. For this is the first time to this mailbox, mutt > > try to fetch all the headers at the beginning and always got the > > problem "tls_socket_read (A TLS packet with unexpected length > > was received.)" when just fetched about 5000 headers. > > > If your Gmail INBOX really has 20, messages, I think mutt IMAP can not > fetch so much > headers. Maybe you need to delete or catalyzes your gmail. Garbage. I have over 70,000 emails in my account, over 40,000 of which are in the debian-users mailing list folder. I just recently reinstalled my computer, and had to re-fetch all 40K headers, and while it took a while to do so over IMAP, it did so successfully, without hiccup. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: Hashcash
On Fri, Apr 15, 2011 at 03:47:35PM +0200, Simon Ruderich wrote: > I'm not entirely sure what you're trying to do. But > $display_filter should just read the message from stdin and pass > it to stdout. From what I can see that's what your program does > so it should be fine. https://github.com/atoponce/Penny-Red -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Automatically downloading the header cache
I'm curious if it's possible to automatically download the IMAP header cache on a new install, after configuring the .muttrc of course. It's rather frustrating to go into each folder (I have 100+ of them on the IMAP server) to instigate the process of downloading all the headers into the cache. Of course, I have $header_cache set (as well as $message_cachedir and $message_clean_cache) to the appropriate path, and the headers are getting downloaded- just only when I visit that folder, and not before. Any ideas? Is $imap_chack_subscribed what I'm after? I've asked in IRC and Google'd around a bit, but haven't found anything, so I figured I'd ask here. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: Hashcash
On Sun, Mar 27, 2011 at 02:59:12PM -0600, Aaron Toponce wrote:
> original = sys.stdin.readlines()
> email = StringIO.StringIO(''.join(original))
> message = rfc822.Message(email)
>
> # ... snip several lines of code ...
>
> for line in original:
> if len(line) == 1 and len(token_status) > 0:
> print
> for status in token_status:
> print status
> token_status = []
> else:
> print line,
Somehow, the code lost its formatting, and I forgot to attach the Python
script. Let's try this again:
# converting a list to a file-type object for parsing rfc822 headers
original = sys.stdin.readlines()
email = StringIO.StringIO(''.join(original))
message = rfc822.Message(email)
# ... snip ...
# reprint the original mail, as well as the status of the hashcash check
for line in original:
if len(line) == 1 and len(token_status) > 0:
print
for status in token_status:
print status
token_status = []
else:
print line,
Thanks again.
--
. o . o . o . . o o . . . o .
. . o . o o o . o . o o . . o
o o o . o . . o o o o . o o o
#!/usr/bin/env python
import rfc822
import StringIO
import subprocess
import sys
tokens = []
token_status = []
# converting a list to a file-type object for parsing rfc822 headers
original = sys.stdin.readlines()
email = StringIO.StringIO(''.join(original))
message = rfc822.Message(email)
# check for the presence of "X-Hashcash" and "Hashcash" headers
if message.has_key("X-Hashcash"):
for list in message.getheaders("X-Hashcash"):
tokens.append(list)
if message.has_key("Hashcash"):
for list in message.getheaders("Hashcash"):
tokens.append(list)
# check each token
if len(tokens) > 0:
for token in tokens:
bits = token.split(":")[1]
resource = token.split(":")[3]
token_status.append(subprocess.call("hashcash -cdb %s -r %s -f /home/aaron/.mutt/hashcash.db %s" % (bits,resource,token), shell=True, stdout=subprocess.PIPE))
# reprint the original mail, as well as the status of the hashcash check
for line in original:
if len(line) == 1 and len(token_status) > 0:
print
for status in token_status:
print status
token_status = []
else:
print line,
#subprocess.Popen("less", shell=True)
signature.asc
Description: Digital signature
Re: Hashcash
On Fri, Mar 25, 2011 at 07:10:19AM -0600, Aaron Toponce wrote:
> Now to start working on the verification process. I figure I can use
> $display_filter for that, and just not filter anything, but execute another
> Python script.
So, now I'm working on the verification script, and I'm struggling getting
it to work with $display_filter. It's a Python script. When the script
doesn't have anything in it, the message isn't displayed. This isn't what I
would expect. I would expect the message to still display, unless the
script has logic that performs otherwise.
I haven't tested this with a shell script just running sed against the
file, so maybe I should try that. However, it seems that I have to reprint
the entire message with Python (which is fine, because I want to add lines
to the output, based on some logic in the Python script). Here's the
relevent logic:
original = sys.stdin.readlines()
email = StringIO.StringIO(''.join(original))
message = rfc822.Message(email)
# ... snip several lines of code ...
for line in original:
if len(line) == 1 and len(token_status) > 0:
print
for status in token_status:
print status
token_status = []
else:
print line,
The "original" variable is the original message, read from STDIN, as
$display_filter does. The "email" variable is the message, converted to a
file-type object, so I can use the rcf822 module, getting access to the
headers easily. The "for" loop at the end is reprinting the mail, putting
the status of "hashcash" in the "status" variable in the message, right
after the headers, and before the body of the mail. I'm looking for a blank
line, as per RFC822 (and subsequent follow-up RFCs), there bust exist a
blank line before the body after the headers. I'm looking for this line to
print my message to the user.
The problem I'm experiencing, I think, is with the $PAGER. Everything
displays fine, except when I wish to PGUP/PGDN the message doesn't display
correctly, and gets all jumbled up. I'm assuming it has something to do
with writing the message line-by-line, but I'm not sure.
Can someone help me with this? I've attached what I've come up with so
far, and I believe all logic is sound, minus writing the masseg to screen
(which I would think you write the message, THEN the $PAGER displays it,
keeping everything in tact- guess not).
Any hlep would be appreciated. Thanks in advance!
--
. o . o . o . . o o . . . o .
. . o . o o o . o . o o . . o
o o o . o . . o o o o . o o o
signature.asc
Description: Digital signature
$folder_format with IMAP
It seems that may printf() sequences that are available for $folder_format aren't working when using IMAP. I'm guessing that many of these are for local folders only? Flags like %d for example. In fact, the only working string that seems to display anything for me is the following: set folder_format="%3C %3N %f" Has anyone else notices this? Is there something else that I need to set? I'm coming up short with anything that would say one way or the other. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: Hashcash
On Thu, Mar 03, 2011 at 05:23:43PM -0700, Aaron Toponce wrote:
> So, has anyone successfully implemented Hashcash into Mutt, and if so, how?
Here is what I came up with. It's a Python script that runs as my default
editor. The script calls Vim, after which, it parses the headers and adds
the necessary tokens. I haven't found any bugs yet, but I'm sure I will
soon enough. I also blogged about it here:
http://pthree.org/2011/03/24/hashcash-and-mutt/
Now to start working on the verification process. I figure I can use
$display_filter for that, and just not filter anything, but execute another
Python script.
Anyway, thought I'd post an update.
--
. o . o . o . . o o . . . o .
. . o . o o o . o . o o . . o
o o o . o . . o o o o . o o o
#!/usr/bin/env python
import csv
import fileinput
import rfc822
import subprocess
import sys
subprocess.call("vim %s" % sys.argv[1], shell=True)
file = open(sys.argv[1], 'r')
headers = rfc822.Message(file)
to_emails = headers.getaddrlist("To")
cc_emails = headers.getaddrlist("Cc")
email_addrs = []
tokens = []
# Harvest all email addresses from the header
for email in to_emails:
email_addrs.append(email[1])
for email in cc_emails:
email_addrs.append(email[1])
# Remove duplicate emails from the list, requires Python 2.5 and later
email_addrs = list(set(email_addrs))
# Check if an appropriate token is already generated for the mail
if headers.has_key("X-Hashcash"):
for list in headers.getheaders("X-Hashcash"):
email_addrs.remove(list.split(":")[3])
if headers.has_key("Hashcash"):
for list in headers.getheaders("Hashcash"):
email_addrs.remove(list.split(":")[3])
# Call the hashcash function from the operating system to mint tokens
for email in email_addrs:
t = subprocess.Popen("hashcash -m %s -X -Z 2" % email, shell=True, stdout=subprocess.PIPE)
tokens.append(t.stdout.read())
# Write the newly minted tokens to the header
f = fileinput.FileInput(sys.argv[1], inplace=1)
for line in f:
line = line.strip()
if f.lineno() == 1:
for token in tokens:
print token,
print line
continue
else:
print line
file.close()
signature.asc
Description: Digital signature
Re: Hashcash
On Tue, Mar 22, 2011 at 09:48:26AM +0100, Clément Bœsch wrote: > On Tue, Mar 22, 2011 at 08:39:16AM +, Jamie Paul Griffin wrote: > > > > Oh, and I love your .signature! > > > > > > Heh. Total geek. I dig it. > > > > > > -- > > > . o . o . o . . o o . . . o . > > > . . o . o o o . o . o o . . o > > > o o o . o . . o o o o . o o o > > > > sorry to change the topic but can i ask, what does that signature mean? is > > it like braille or something? > > > > Looks like a glider in the game of life It is the glider. See: http://www.catb.org/hacker-emblem/ and http://en.wikipedia.org/wiki/Glider_(Conway's_Life). Braille on the other hand is 3 rows by 2 columns. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: Hashcash
On Tue, Mar 22, 2011 at 10:37:35AM +0900, Dan Drake wrote: > One idea: write a script (shell, Python, etc) that parses the temp file, > adds the hashcash stuff, and then spawns vim. Then in Mutt, you set your > editor to be that script: > >set editor = my_hashcash_script > > The nice thing about that is you can write it using whatever you like, > instead of Vim's scripting language, and perhaps use email parsing > libraries and so on. Actually, that's not a bad idea. I'm struggling working my way through vimscript, and it's a shame that I have to reinvent everything myself. Calling already existing libraries and modules is definitely the way to go. Let's see if that makes my job easier. The only hiccup I see, is I might not have all the addresses added to the mail before composition. If I add addresses later, this means I would need to re-edit the temp file, so the script can reparse the addresses and add each token to the header. Then again, this was an issue anyway. Come to think of it, I should have Vim call an external script that works on the temp file when closing. This would give me the opportunity to add the necessary addresses to the header before the script executes. > Oh, and I love your .signature! Heh. Total geek. I dig it. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: Hashcash
On Thu, Mar 03, 2011 at 05:23:43PM -0700, Aaron Toponce wrote: > I'm curious if anyone has gotten hashcash working with Mutt. > http://hashcash.org/mail/mua/mutt/ seems to explain a background process > and a foreground process. > > The hashcash-sendmail script page (the background process) is down, and > I can't seem to find a copy of it anywhere online, and it's not in > Debian packages. The Perl script (the foreground process) written by Tim > Ruddick doesn't have any documentation on how to implement it into your > ~/.muttrc. > > I've got the Penny Post extension in Icedove 3.0, but apparently it > doesn't support 3.1, which I'm sure will come down the update pipes in > Sid soon enough. I'd rather stick with Mutt as my main MUA anyhow. > > So, has anyone successfully implemented Hashcash into Mutt, and if so, how? I have made some progress, although I must do everything manually. I'm looking to automate the process with Vim, so if someone could help me with this, that would be awesome. I've set "edit_headers=yes" in my ~/.muttrc so I can edit the headers with Vim, my preferred editor. I can select a new line, then from command mode, run "! hashcash -m resource -X -Z 2" to add the line to the header, as I've done with this message. Then, I can continue to compose my message, save, quit and send. Rather than calling the external command manually, I would like to automate the process with a macro. So, the macro should be able to parse the "To:", "Cc:" and "Bcc:" lines, which would contain a comma-separated list of addresses, and run the hashcash command for each address, putting each result on its own line. I'm not sure how to handle Bcc: addresses, so we can ignore that for the time being. Any idea how I can create this macro? I guess asking a Vim mailing list would be more appropriate, but I figured because I'm looking to implement this into Mutt, it is still considered "on-topic" here. Of course, this is only minting the appropriate tokens, and not verifying and storing them, which is a separate issue entirely, and also needs to be addressed (even though I doubt anyone besides me is really interested in Hashcash for mail). If anyone could help me with this, that would be great. Thanks, -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: [OT] GPG signature fails
On Mon, Mar 14, 2011 at 05:31:42PM -0500, Derek Martin wrote: > If this verifies, I just figured it out. Still a bad signature here. I wonder if it has anything to do with the fact that your signature is 159 bits, and not 160? -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: [OT] GPG signature fails
On Mon, Mar 14, 2011 at 05:31:42PM -0500, Derek Martin wrote: > If this verifies, I just figured it out. It's still failing in Mutt for me, but verifies in Thunderbird. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: [OT] GPG signature fails
On Sun, Mar 13, 2011 at 06:32:54AM -0600, Aaron Toponce wrote: > On 03/13/2011 06:11 AM, Remco Rijnders wrote: > > Derek, > > > > I do appreciate you signing all your mails to this list, but each and > > every one of them shows up as a bad signature and I'm not sure whether > > you are aware of this or not. > > > > I've tried to contact you about this outside this list, but you don't > > make it very easy for people to contact you directly. > > Something must be broken with your MUA or OpenPGP implementation. All of > his signatures come in clean for me. I haven't seen a bad signature from > him on this list. > > OpenPGP Security Info > > UNTRUSTED Good signature from Derek D. Martin > Key ID: 0xDFBEAD02 / Signed on: 03/10/2011 11:36 AM > Key fingerprint: B5F7 DC7F F7B9 A9E2 5AE2 9002 1C49 C048 DFBE AD02 Actually, that was using Icedove. Using Mutt yeilds: [-- PGP output follows (current time: Sun 13 Mar 2011 06:59:00 AM MDT) --] gpg: Signature made Thu 10 Mar 2011 11:36:36 AM MST using DSA key ID DFBEAD02 gpg: BAD signature from "Derek D. Martin " [-- End of PGP output --] After running 'gpg --list-packets' on his signature, here's what I get: :signature packet: algo 17, keyid 1C49C048DFBEAD02 version 3, created 1299603262, md5len 5, sigclass 0x01 digest algo 2, begin of digest e3 50 data: [159 bits] data: [159 bits] He's using DSA with SHA1. Interesting that the output is 159 bits, and not 160 bits. Seahorse also complains about the signature, calling it bad. Interesting too that Enigmail with Icedove validates the signature, but Mutt fails. At any event, it does in fact appear that something is broken with his OpenPGP signatures, likely due to a misconfiguration in his ~/.gnupg/gpg.conf or muttrc. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: [OT] GPG signature fails
On 03/13/2011 06:11 AM, Remco Rijnders wrote: > Derek, > > I do appreciate you signing all your mails to this list, but each and > every one of them shows up as a bad signature and I'm not sure whether > you are aware of this or not. > > I've tried to contact you about this outside this list, but you don't > make it very easy for people to contact you directly. Something must be broken with your MUA or OpenPGP implementation. All of his signatures come in clean for me. I haven't seen a bad signature from him on this list. OpenPGP Security Info UNTRUSTED Good signature from Derek D. Martin Key ID: 0xDFBEAD02 / Signed on: 03/10/2011 11:36 AM Key fingerprint: B5F7 DC7F F7B9 A9E2 5AE2 9002 1C49 C048 DFBE AD02 -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: OpenPGP digital signature
Re: tls_socket_read - definitely a Mutt bug.
On 3/10/2011 6:50 AM, Mason Loring Bliss wrote: > On Wed, Mar 09, 2011 at 03:01:19PM -0700, Aaron Toponce wrote: > >> It's not a Mutt bug. It's a GnuTLS bug. See the following: > > Thank you for playing, but no, it's not specific to GnuTLS. I can get almost > identical behaviour with OpenSSL. You're welcome for playing. I read bug reports, and know what they say. > Are you saying that both packages, OpenSSL and GnuTLS, have identical bugs > that interfere with Mutt's handling of status requests for invalid mailboxes > in an almost identical manner? > > Or are you saying that this configuration somehow leaked GnuTLS code in? I'll paste the relevant parts from the bug reports, seeing as though you missed it: "When a server terminates a connection abnormally (TCP termination), TLS (and thus gnutls) cannot distinguish that from a prematurely terminated connection due to attack. This is the reason the error "A TLS packet with unexpected length was received.". If we decided to silence this error, as other implementations or applications might do, we would be vulnerable to premature termination attacks (i.e. someone terminates your connection after the first 10kb of your message were downloaded to prevent you downloading an attachment). That is worse, thus we stay on the safe side of warning of servers that do that." So, shoot your mail provider for cutting your connection, black mail your ISP for dropping you, or keep your cat from chewing your network cables. It's not a Mutt bug. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Re: tls_socket_read - definitely a Mutt bug.
On 3/9/2011 2:23 PM, Mason Loring Bliss wrote: > On Wed, Mar 09, 2011 at 04:18:15PM -0500, Mason Loring Bliss wrote: > >> Does anyone know if this is a known bug, offhand? Or shall I create a login >> to the bug tracking system and file it? > > And foolishly, I forgot to mention what I got this with. To wit: > > 1.5.21 (2010-09-15) from Fedora 14's Mutt package, evidently built against > TLS, and the same version/date built from source against OpenSSL. It's not a Mutt bug. It's a GnuTLS bug. See the following: https://bugs.launchpad.net/ubuntu/+source/gnutls13/+bug/105736 https://bugzilla.redhat.com/show_bug.cgi?id=533647 http://lists.gnupg.org/pipermail/gnutls-dev/2003-March/000427.html -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Hashcash
I'm curious if anyone has gotten hashcash working with Mutt. http://hashcash.org/mail/mua/mutt/ seems to explain a background process and a foreground process. The hashcash-sendmail script page (the background process) is down, and I can't seem to find a copy of it anywhere online, and it's not in Debian packages. The Perl script (the foreground process) written by Tim Ruddick doesn't have any documentation on how to implement it into your ~/.muttrc. I've got the Penny Post extension in Icedove 3.0, but apparently it doesn't support 3.1, which I'm sure will come down the update pipes in Sid soon enough. I'd rather stick with Mutt as my main MUA anyhow. So, has anyone successfully implemented Hashcash into Mutt, and if so, how? -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o *** This email has been stamped using Penny Post. Stamping email helps combat spam. Find out more about stamping your email at: http://pennypost.sourceforge.net signature.asc Description: OpenPGP digital signature
Google 2-step authentication
Will mutt be supporting Google's newly announced 2-step authentication? I don't use any other mail client other than mutt, but I would like to take advantage of the extra security when it's available for my account. http://goo.gl/nP3ML Thoughts? -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: moving to Mutt from Gmail
On Sun, Dec 26, 2010 at 02:37:18PM +0100, Gregor Zattler wrote: > Hi Dale, mutt users, > * Dale A. Raby [25. Dec. 2010]: > > Why not use Gmail's own spam filter to eliminate the spam? It > > works pretty well and doesn't require you to use or maintain > > SpamAssassin. Use Mutt with IMAP and the messages will stay on > > the practically limitless storage space of Gmail's server. > > He'll then loos control over *his* emails... On his computer he > has physical controll over them. No, he won't. Google firmly believes it's your mail, not theirs. See http://www.dataliberation.org/google/gmail. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: PGP signed status flag not showing
On Wed, Dec 22, 2010 at 04:54:19PM -0600, Derek Martin wrote: > This absolutely makes sense -- every bit of what you describe. > > Mutt does not save the state of a mailbox once it leaves that > mailbox... so if it has to parse the message to determine that it is > signed when you first see a message, it will need to do so *every time > you visit that mailbox*. Except when visiting the other mailboxes, all the flags are in place, as expected - before viewing the message. > As for using in-line signatures, it's still very common to do so, > because (at least as of the last time I looked into this) many of the > most popular mail clients (including Pine and some derivatives, and > the MS-Outlook family) could not handle PGP-MIME messages *at all*. > Thus many people who are familiar with PGP and communicate with such > people persist in using the old form, because it's more portable. This is understood. Regardless, Mutt can flag both inline and MIME/SMIME signatures in the index without issue on every mailbox except two. Further, thes _is_ the gnupg-users mailing list that we are talking about. Not only will people be signing mail much more frequently on this list than others, but I would expect the probability that people on the list are using MIME/SMIME to be much higher than a standard list. > It's easy enough to confirm... just look at the raw content of the > message. If you don't see MIME parts headers, but you DO see stuff > like > > > - BEGIN PGP MESSAGE - > > - END PGP MESSAGE - > > ...then you have yourself a traditional PGP message. Yes. I'me very familiar with PGP signatures. I've been signing my email since 2004, and I've been on Uneset, mailing lists and BBS where signing posts was common-place. > For example, this post to gnupg-users absolutely IS a traditional > in-line PGP message: > > > http://www.gossamer-threads.com/lists/gnupg/users/52282?do=post_view_threaded#52282 > > A casual glance suggests there are many such messages. Again, I don't have a problem with this. It's just that the only flag showing, in fact, is just 'L' for the list. Nothing else, until after I view the message of the list. It's entirely inconsistent with the 100+ mailboxes that I change to every day. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
Re: PGP signed status flag not showing
On Wed, Dec 22, 2010 at 04:27:38PM -0500, Ed Blackman wrote: > There are two kinds of PGP encrypted or signed messages: PGP/MIME > and traditional inline. But only PGP/MIME can be detected in the > headers of the message. My guess is that mutt shows the flags for > the more common PGP/MIME messages all the time, because mutt has to > parse the header for the fields that show up in the index. For > traditional inline PGP, mutt only shows the flags after it's had to > parse the body to display it in the pager. This would make sense, except for the gnupg-users mailing list. I've been on the list for a while, and refuse to believe that everyone signs inline, and no one uses PGP/MIME. Also, after leaving the mailbox, and coming back to it, any signed flags that did show after reading a signed message are no longer present. -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
PGP signed status flag not showing
I'm struggling with this status flag in the message index. Most mailboxes show the 's', 'S' and 'P' flags appropriately. However, there are two mailboxes that don't. One is a local LUG mailing list, the other is the GnuPG Users mailing list, ironically enough. However, after viewing a message that is signed, when going back to the index, the 's' flag will show, even though it didn't show before reading the mail. PGP/GPG is working fine, as far as I can tell. I can send encrypted mail, decrypt mail, sign and verify signatures. Any ideas what I can't see the signed message flags in only a couple of the mailboxes? -- . o . o . o . . o o . . . o . . . o . o o o . o . o o . . o o o o . o . . o o o o . o o o signature.asc Description: Digital signature
