Re: Problem printing doc-attachments
On Sep 18, Gary Johnson [EMAIL PROTECTED] wrote: I upgraded to Red Hat Enterprise Linux WS release 4 some months ago and had a similar problem. I fixed it by changing that line to this: application/msword; mutt_rem_bgrun openoffice.org-2.1 -view %s I need the mutt_rem_bgrun command because I run mutt on a Solaris machine and run viewers for MS attachments remotely on the Linux box. In your case, this might work: application/msword; ooffice -view %s I don't know if that will help, but it's something to try. Thanks for the response. I tried that openoffice startup paramater but it had no effect on this problem. Any suggestions still welcome. I put the same question to the Ubuntu and Openoffice forums, if a solution comes up I'll report here. Holger
Re: Subject üî
* Kyle Wheeler on Tuesday, September 18, 2007 at 17:21:44 -0500 On Tuesday, September 18 at 11:55 PM, quoth Alain Bench: On Thursday, September 6, 2007 at 16:30:42 -0600, Kyle Wheeler wrote: I had already de-selected Wide Glyphs count as two columns I wonder what does this option? From what I can tell, it allows some characters to take up two columns. For example, an em-dash (—) is hard to tell from an en-dash (–) or even a hyphen (-) without an actual change in width. This makes more sense when using a non-monospaced font (as em-dashes are naturally the same width as an m, which are the same width as everything else in such fonts). It becomes an issue when mutt does something that calls up a symbol from outside the monospaced font, such as the horizontal line character used to draw the threading arrows. This has a natural width that is slightly wider than all the other characters, and so when that option is enabled, the horizontal line glyph occupies two columns (it’s centered in the two-column area). At least, I *think* that’s how this works, based on how it seems to behave. You also need to set this option if you want Asian characters readable in Terminal.app, otherwise they melt into each other horizontally. OTOH setting it messes up Mutt's thread display (can be worked around by setting narrow_tree in Mutt, but not in Slrn). I switched to iTerm for the moment which doesn't have these problems, and offers 256 colors, transparency and even GNU-Screen like multiplexing, but, on the downside, is slower. http://iterm.sourceforge.net/ Thanks as always, Alain. Seconded. c -- Python Mutt utilities http://www.blacktrash.org/hg/muttils/
Debugging an IMAP connection - how?
Our MS Exchange server now allows IMAP connections and I want to use mutt to access it. I have used mutt before with IMAP so know the basics. However I'm having trouble getting it to connect to the Exchange server, so :- Are there any special gotchas when using mutt with Exchange? Is there any way to log the connection process so I can see where it's failing? Any other ideas? I'm pretty sure I am now set up as an IMAP user on the Exchange server as last week I was getting an error (using Thunderbird) that was saying that I didn't exist as a user. Now I just get a failed login which implies that I have my password wrong but my password works on the Exchange webmail login and (as far as I know) that is the same password. -- Chris Green
Re: Debugging an IMAP connection - how?
El día Wednesday, September 19, 2007 a las 09:02:55AM +0100, Chris G escribió: Our MS Exchange server now allows IMAP connections and I want to use mutt to access it. I have used mutt before with IMAP so know the basics. However I'm having trouble getting it to connect to the Exchange server, so :- Are there any special gotchas when using mutt with Exchange? Is there any way to log the connection process so I can see where it's failing? Any other ideas? I'm pretty sure I am now set up as an IMAP user on the Exchange server as last week I was getting an error (using Thunderbird) that was saying that I didn't exist as a user. Now I just get a failed login which implies that I have my password wrong but my password works on the Exchange webmail login and (as far as I know) that is the same password. Hi Chris, You could use 'fetchmail' to connect to the IMAP port and watch the IMAP dialog in the log of fetchmail. Create a file ~/.fetchmailrc with these lines: set logfile/tmp/fetchmail.log defaults timeout 30 keep fetchall poll your-imap-Exchange-server-name-here protocol IMAP username your-login-name password yout-password Then run $ fetchmail -vv and check the dialog in the log file. HIH matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclcpica.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ OCLC PICA GmbH, Geschaeftsfuehrer: Christine Magin-Weeger, Norbert Weinberger Sitz der Gesellschaft: Oberhaching, HRB Muenchen: 113261
Re: Debugging an IMAP connection - how?
On Wed, Sep 19, 2007 at 10:12:37AM +0200, Matthias Apitz wrote: El día Wednesday, September 19, 2007 a las 09:02:55AM +0100, Chris G escribió: Our MS Exchange server now allows IMAP connections and I want to use mutt to access it. I have used mutt before with IMAP so know the basics. However I'm having trouble getting it to connect to the Exchange server, so :- Are there any special gotchas when using mutt with Exchange? Is there any way to log the connection process so I can see where it's failing? Any other ideas? I'm pretty sure I am now set up as an IMAP user on the Exchange server as last week I was getting an error (using Thunderbird) that was saying that I didn't exist as a user. Now I just get a failed login which implies that I have my password wrong but my password works on the Exchange webmail login and (as far as I know) that is the same password. Hi Chris, You could use 'fetchmail' to connect to the IMAP port and watch the IMAP dialog in the log of fetchmail. Create a file ~/.fetchmailrc with these lines: set logfile/tmp/fetchmail.log defaults timeout 30 keep fetchall poll your-imap-Exchange-server-name-here protocol IMAP username your-login-name password yout-password Then run $ fetchmail -vv and check the dialog in the log file. The output actually comes out on STDOUT but that's not a problem. Yes, it's shown up what seems to be the error, it says account currently disabled, they obviously haven't turned me on yet. Thank you! -- Chris Green
utf8
Hello, What would be the best way to make visible mails arriving in my mail-folder as: --=_NextPart_001_2090AD_01C7FA92.54AF4C00 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: base64 V2hlbiByZXBseWluZywgdHlwZSB5b3VyIHRleHQgYWJvdmUgdGhpcyBsaW5lLg0KLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KTm90aWZpY2F0aW9uIG9mIElz c3VlIENoYW5nZQ0KVGhlIGZvbGxvd2luZyBjaGFuZ2VzIGhhdmUgYmVlbiBtYWRlIHRvIHRoaXMg SXNzdWU6IENoYW5nZWQgU3RhdHVzIHRvIEN1c3RvbWVyIFJlc3BvbmRlZCBmcm9tIFBlbmRpbmcs IEFwcGVuZGVkIGEgbmV3IERlc2NyaXB0aW9uLCBJbmNvbWluZyBtYWlsOiBGcm9tOiBtLmFwaXR6 ... In the past I have saved the attachment into a file and unpacked it with $ /usr/local/bin/decode-base64 attachment attachment.ascii but I can get 'decode-base64' compiled on FreeBSD 6.2R Any idea? Thx matthias -- Matthias Apitz Manager Technical Support - OCLC PICA GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e [EMAIL PROTECTED] - w http://www.oclcpica.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ OCLC PICA GmbH, Geschaeftsfuehrer: Christine Magin-Weeger, Norbert Weinberger Sitz der Gesellschaft: Oberhaching, HRB Muenchen: 113261
Re: Debugging an IMAP connection - how?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, September 19 at 09:02 AM, quoth Chris G: Are there any special gotchas when using mutt with Exchange? You probably have to be very careful with your imap_authenticators setting. If the one that the server requires isn't in the list, or if the server advertises something that it won't actually accept, that can prevent mutt from using that server. Is there any way to log the connection process so I can see where it's failing? Yup. Compile mutt with debugging turned on, then run mutt like so: mutt -d 2 A trace of what mutt did (including its imap conversation) will be in ~/.muttdebug0 Any other ideas? Try authenticating by hand. Here's a webpage that explains how to do it: http://www.memoryhole.net/index.php?section=referenceinc=imap Essentially, what you're looking for is in the CAPABILITY string, what auth mechanisms does it require? My dovecot server sends this: CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS STARTTLS AUTH=PLAIN AUTH=LOGIN The important part is those last two entries: it'll accept either PLAIN or LOGIN-style authentication attempts. Find out what your Exchange server will accept, and make sure it's listed in imap_authenticators in your muttrc. I'm pretty sure I am now set up as an IMAP user on the Exchange server as last week I was getting an error (using Thunderbird) that was saying that I didn't exist as a user. Now I just get a failed login which implies that I have my password wrong but my password works on the Exchange webmail login and (as far as I know) that is the same The other thing I've heard is that Exchange sometimes requires your email address as the user name when doing IMAP even though it does not when doing webmail logins. ~Kyle - -- It is not bigotry to be certain we are right; but it is bigotry to be unable to imagine how we might possibly be wrong. -- Gilbert Chesterton -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG8S/lBkIOoMqOI14RAoStAKD/jSfO8ZV9abZu50Ga3KnJcFX6HQCg04/o aq8MJEf6AfP4unFlW30dYE4= =llD1 -END PGP SIGNATURE-
Re: utf8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, September 19 at 03:57 PM, quoth Matthias Apitz: What would be the best way to make visible mails arriving in my mail-folder as: --=_NextPart_001_2090AD_01C7FA92.54AF4C00 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: base64 Hmm, the best way would be to get mutt to decode those. :) I don't know how, though - probably something you need to pester the devel list for. $ /usr/local/bin/decode-base64 attachment attachment.ascii but I can get 'decode-base64' compiled on FreeBSD 6.2R OpenSSL can also decode base64 stuff: openssl base64 -d attachment attachment.ascii ~Kyle - -- If you are going through hell, keep going. -- Winston Churchill -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFG8TChBkIOoMqOI14RAgI+AJ4gDUao/Aga3cXDJa9ZXFUUf46WTwCgvFb7 7GKVmF55l2xPJEub360Gg7E= =JWgg -END PGP SIGNATURE-
one macro to save many messages in different folders?
Hello, For several reasons not really relevant here, I have the messages of several mailing lists delivered to one common inbox folder. When I have read them, I want to tell mutt, with one keystroke, to look at all the messages I have tagged and save each of them to the folder corresponding to its mailing list. What if I do something like: message-hook '~h ?List-id Centos' 'save-hook +centos' message-hook '~h ?List-id OpenOffice' 'save-hook +openoffice' message-hook '~h ?List-id someotherlist''save-hook +someotherlist' what happens when I type ;s ? will mutt do the right thing, that is using all those hooks save each message to the folder it belongs to according to the rules above? If not, what is the right method to do it? I'm asking before starting to experiment myself because I'd like to know if I'm at least looking in the right direction or must go with a totally different approach, and because the idea came to me a few minutes ago but probably won't have the possibility to play with it before a few days. TIA, Marco -- The one book on software and digital technologies that no parent or teacher can ignore http://digifreedom.net/node/84
