Re: winmail.dat

> > Wouldn't it be more appropriate to ask why Thunderbird can process said > email from that > users' settings (outlook) and mutt cannot, rather than asking the sender > to change something in his settings? The sender's settings are pre-MIME. MIME is a set of Internet mail standards that has

Re: winmail.dat

Christoph P.U. Kukulies writes: > Hi. > I'm running Mutt 1.5.20 (2009-06-14) under Ubuntu and was wondering why > mutt couldn't cope with > some mail I got, containing an attachment, named winmail.dat (MS Outlook). Ask the sender to configure their mail tool for plain text or html rather than

Re: Revisiting: application/pgp-signature is unsupported

> I am facing the same problem now, but may have a bit more information. Original message has a multipart/signed structure with a qp text and a signature part, all of which is wrapped into a multipart/mixed structure, presumably done by the list server for the purpose of adding a (text, 7-

Revisiting: application/pgp-signature is unsupported

There was a thread on this mailing list back in March, http://marc.info/?l=mutt-users&m=130016436305546&w=2 List: mutt-users Subject:application/pgp-signature is unsupported From: Joseph < xxx () gmail ! com> Date: 2011-03-15 4:44:57 which doesn't seem to have had a

Re: [Announce] mutt-1.4 is out.

Thomas Roessler writes: > Mutt-1.4 has been released. You can download it from the following > location: . > - Mutt now uses the iconv interface for character set conversions. > This means that you need either a very modern libc, or Bruno > Haible's libiconv, w

Re: Mutt sucks less than the rest

> - clearsigned and/or ascii-armored messages > > Whether you guys like it or not, most of the rest of the world uses > clearsigning and ascii-armored plaintext messages. Mutt falls down > here. You apparently refuse to support this, which makes no sense > since the majority of the PGP-using

Re: signed emails, why ?

Alexander Skwar writes: > So sprach »Steve Kennedy« am 2002-01-07 um 12:52:25 + : > > Why does everyone send signed emails to the list, is it always > > necessary ? > > No, it's not. Personal mails and "important" mails should be signed > and/or encrypted. However mailinglist mails should n

Re: --without-iconv doesn't work?

Claus Assmann writes: > System: OpenBSD 2.8 > ./configure --without-iconv > doesn't work: The documentation in INSTALL is wrong. There is no --without-iconv configure option, and configure does the right thing by bombing out. I think this can be fixed, though :)

Re: --without-iconv doesn't work?

> without iconv. Also note that for some reason the iconv macro is > defined twice in config.h: perhaps one of them is hardwired. So make The reason is that the definition in acconfig.h is superfluous. At a glance, it seems that about 20 definitions in acconfig.h are superfluous. (See "Mak

Re: How to place a request of receipt for an outgoing mail?

> Frankly it is a diabolical practise, causes uneccessary and pointless > mail. If a mail is so important that you *must* be certain it has been > read then phone the person up. Since the mechanism is inherently > unreliable anyway, what is the point of using it ? Exactly. Every now and then,

Re: Problems installing MUTT

Ivan Castillo Escobar writes: > Hi, I'm trying to install and configure MUTT 1.3.24 in Tru64UNIX 4.0F. > I have the tar file, I did extract all files, but when I try to run (# > configure ) command the system returns the following message: > # ./configure > configure: error: can not find sources i

Re: Another command line question

Barney Wells writes: > I am using mutt .93.1 on SCO UNIX 5.0.5. > A few weeks ago I asked about attaching files; > > mutt -x -s testing -a test.file username > This works great. Now I want to send text that is > not in a file. It is fields out of my database. > I would like this to appear in t

Re: SMTP in Mutt

> OK, thats not what I mean. If you want me to set the variable like above. Its done >before I write the first email. I want to use my ISP provider SMTP server, so I need >the variable for it. I have done the search at Mutt manual, but they never say >anything about SMTP server, they do have E

Re: LWN

Jesper Holmberg writes: > Hi all! > > Check out the first "Letters to the Editor" in today's "Linux Weekly News" > (www.lwn.net), it contains some critique of mutt by Erik Kidd. To me, all > of it doesn't seem accurate, e.g. "Mutt can't search message bodies.", but > I guess someone more knowledg

Re: 1.3.24 fails to compile on SunOS

Steve Kennedy writes: > SunOS 4.1.4 gcc 2.95.2 > > make[2]: Entering directory `/home2/ns/steve/mutt/mutt-1.3.24/imap' > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl -I/usr/local/include -I../intl > -Wall -pedantic -O2 -c auth.c > In file included from ../protos.h:20, > from

Re: Script to rebuild quotes

Signing list email is a complete useless exercise and wastes my time if your key is not on any key servers (and yes, I tried several, just in case). [-- PGP output follows (current time: Fri 30 Nov 2001 12:14:19 PM GMT) --] gpg: Signature made Fri Nov 30 08:04:08 2001 GMT using DSA key ID 212

Re: mutt configure --with-sasl

Volker Jahns writes: > I would like to configure mutt compile to include imap support w/ sasl > authentication: > > > configure --enable-pop --enable-imap --with-sasl > terminates w/ error message: > > checking for sasl_client_init in -lsasl... no > configure: error: could not find libsasl Wh

Re: Mailing list and starting a new message

Sean LeBlanc writes: > I see the "lists" and "subscribe" commands, and I added them to my .muttrc. > They *seem* to work, I haven't figured out how to get the "list info" that shows > up via "lists", but anyway... > > I was wondering how one might set up mutt so that you hit some particular key >

Re: Cancelling an action?

> Ctrl-G. Cancels any action in mutt. It's a beautiful thing. :) Yeah, and Emacs raises its HUGE head ;-)

Re: List processing in Mutt

Bruno Postle writes: > On Sat 03-Nov-2001 at 11:06:16AM -0500, Rich Lafferty wrote: > > > > (In case you haven't already gone "D'oh!":) > > Am I the only person who got a huge windows virus tagged onto the end of > that email? I never saw it because it was rejected on my mail gateway. Yes, R

Re: [THKS] Different "From: " addresses

> Thanks for the great tip. The second method works wonderful. > Now I can post to lists with my arms at rest. > Could you tell me what the '~l' and '~C' are good for? For exactly the purposes mentioned in the manual. You should take some time to read it. http://www.mutt.org/doc/manual/man

Re: How to "un-attach?"

Justin R. Miller writes: > Thus spake John P. Verel ([EMAIL PROTECTED]): > > > I sometimes accidentally attach the wrong file to a message. I can't > > figure out how to to "un-attach it". Can anyone help on this? > > Try highlighting the attachment in the compose menu and hitting 'D' > (howev

Re: Maildir config?

Johansson Jan writes: > >Why don't you let mutt create it? Yet you need some place to store your > >Maildir-Folders in. > > I have over 2gigs of mail in ~/Maildir ;) Thank god that you're not a user in my network ;-)

Re: Postfix question

> both of these boxes are on the same cable network. > I will attach a copy of my main.cf file and maybe someone can give me Don't! > a pointer (I have tried reading the manual..) There is a postfix-users mailing list. There is a FAQ at www.postfix.org. If you need to send configuration da

Re: deleting messages with same message id's?

> :0 Whc: msgid.lock > | formail -D 16384 msgid.cache > :0 a: > duplicates > > You can change 'duplicates' to '/dev/null' if you trust the > recipe works. No, you shouldn't. Unfortunately, the procmailex man page doesn't mention that procmail may fail for reasons other than "... their own scr

Re: the 'You have got new mail' message

> or if this does not work : is there a bash command to look if i have got > new mail. so that i can put this command in the .bashrc file What's so hard about doing a "man bash"?

Re: mutt & exchange

> Another good reason to include SMTP capabilities into mutt. They don't belong there. Check the archives, this has been discussed to death already.

Re: mutt-1.3.2i corrupt?

Rino Mardo writes: > hi. i'm using debian 2.2r0 and have downloaded mutt-1.3.2i from ftp.mutt.org. > i have gnupg-1.0.5 installed which is currently being used by mutt-1.2.5i > without any problems. > > mutt-1.3.2i produces errors when doing "make install" and it's searching for > the file "READ

Re: mutt-1.3.2i corrupt?

Rino Mardo writes: > hi. i'm using debian 2.2r0 and have downloaded mutt-1.3.2i from ftp.mutt.org. 1.3.2i is an OLD development version from way way back. The current development version is 1.3.22.1i.

Re: iconv etc

> configure:6558: checking for iconv > configure:6576: gcc -o conftest -Wall -pedantic -g -O2 -I/home/will//include >-I/home/will/include -L/home/will//lib -L/home/will/lib conftest.c 1>&5 > /tmp/cca149331.o: In function `main': > /home/will/mutt-1.3.22.1/configure:6570: undefined reference

Re: [MAILER-DAEMON@hq.newdream.net: Undelivered Mail Returned to Sender]

> checking whether this iconv is good enough... no > configure: error: Try using libiconv instead Strange - everything else looks correct. We'll need the relevant parts of your config.log, too.

Re: fcc

> so my problem with 1.2.5 is the save-hook thing (which may have a very > simple answer for all i know), but i would like to be able to compile > 1.3.x just for cheap thrills. Well, if you don't show us how exactly 1.3.22.1i fails to compile, we're unable to help ...

Re: fcc

Will Yardley writes: > i just compiled mutt 1.2.5 in my home directory on a shell account on a > machine for which i don't have root access (later versions aren't happy > compiling for some reason, but 1.2.5 worked ok). > > a couple questions; i installed libiconv 1.7 in my home dir and pointed >

Re: [applica/mac-binhex, 7bit, 911K]

> the only way i can view it is if i read this email in > Netscape. I've looked into the linux mac utils, but > they don't seem to work for me. can anyone tell me > how in mutt i can save this attatchment in a format > that i can view with the gimp or any linux/unix image > viewer. Just save

Re: procmail

> Then the usual reason why .forward is ignored is unsafe permissions on your > homedir or your .forward / .procmailrc (should not be group-writeable). Unless you have one group per user, and procmail was configured accordingly. As appears to be the case with at least one major Linux distro.

Re: recompile for updated ncurses?

Ken Weingold writes: > I built mutt with ncurses 5.0, and just updated ncurses to 5.2. Any > reason to recompile mutt? I'm following the ncurses snapshots and don't usually recompile mutt, but in your case, I'd recommend it if you are using shared libs for ncurses. If you check out the top of

Re: SMTP AUTH-capable MTA

> My issue is not with sendmail, per se, but with a new set of policies > that have been implemented locally. Redirecting all mail from the Unix > host to a Windows NT machine to be virus and "content" screened is a > decision I disagree with. And seeing as that screening server has > already

Re: Procmail

> > :0 Whc: .msgid.lock > > | formail -D 16384 .msgid.cache > > :0 a: > > /dev/null > > Overkill. > > :0 Wh: $HOME/.msgid.lock > | formail -D 16384 $HOME/.msgid.cache > > is sufficient (why make a copy if you drop it to /dev/null anyway?) Overkill, yes, but still wrong. Please rea

Re: Prpblems Installing Mutt-1.3.20 from tar.gz ~

tabanna writes: > > After doing ./configure I am getting the message that > > > ~ have already Installed > > If is, indeed, the correct version, then, > What, please, do I need to do ? Try "./configure --help" and check whether there's anything relevant.

Re: Installing Mutt 1.3.19

> Thanks a lot, as you can see it worked: > > [nelsong:~]$ mutt -v > Mutt 1.3.19i (2001-06-07) > System: Linux 2.4.5 [using ncurses 5.2] > > Is that problem with autoconf 2.50 in general or just the one that`s > shipping with slackware? autoconf 2.5x is not fully backwards compatible. I have

Re: Installing Mutt 1.3.19

> I did`nt find anything in my config.log, but then again, I`m fairly > ignorant on these kind of things. I was wondering if someone could check > it out. Attached is the config.log, sorry if it bothers anybody, this is > the first and last time I attached an unrequested file. > It was created

Re: feature request

Erwin Kaiser writes: > Mutt is great! > Two features I'd like to propose: > 1. The screen should be cleared at termination. This is a feature of the terminal emulator you are running. This is the reason why I replaced the xterm terminfo entry on my Solaris box with the X11R6 xterm definition

Re: Evaluation of shell commands in .muttrc

> The header stays the same for the entire mutt session. I thought to > myself that perhaps the my_hdr was only being evaluated once, so I tried > the following instead: Insert send-hook . 'unmy_hdr X-BOFH-Excuse:' before the one below. See section 4.4 Using Hooks in TFM. > send-hook . "

Re: compiling Mutt with ncurses

> The script should recognize this (I haven't looked recently, but thought > that mutt's configure script used chunks of script that I'd written to > encompass this). CF_CURSES_LIBS is not used in 1.2.5, and the parts we "borrowed" don't cover header file location. Hhm, just by looking at it

Re: compiling Mutt with ncurses

Eugene Lee writes: > When I built ncurses-5.2, I set the installation prefix to /usr/local. > The libraries are in /usr/local/lib, which I expect. But the header > files are grouped into a /usr/local/include/ncurses directory. The > configure script for mutt-1.2.5i can't figure this out --- or m

Another pop3 question

I've been playing around with cucipop, but I can't seem to make it work with mutt. Running cucipop in debug mode, all seems to fine: after specifying USER and PASS, I can LIST and STAT, the mailbox, RETR messages etc. But mutt (1.3.19) only ever tells me that APOP authentication failed, "

Re: index format

Doug Kearns writes: > Hello all, > > Is there some way to to set the index format so that it strips certain > characters from the subject( %s ) ? > > eg. I'd like to strip the leading [...] from the subject > "[ruby-talk:15734] java based interpreter and regexes" There is no way to do it in mu

Re: ..and the mouse?

> > > Is there any chance with Mutt to use the mouse? > > > > What for? One of the reasons I like mutt for is that I can keep > > my hands on the keyboard at all times. > > Copy and Paste, especially if you use an xterm. I don't think this qualifies as using the mouse with mutt ;-)

Re: ..and the mouse?

> Is there any chance with Mutt to use the mouse? What for? One of the reasons I like mutt for is that I can keep my hands on the keyboard at all times.

Re: X-Face header

Ralf Hildebrandt writes: > Ok, I found out how to generate an X-Face "suitable" image using > compface, but how can I insert the header from within mutt? > > my_hdr X-Face: > > but > > a) The string spans multiple (4) lines > b) makes mutt crash (segfault) Well, Ralf, I'm sure you know the

Re: request for SMTP integration (was Re: Mail using non-local SMTP server.)

> > Mutt doesnt ask for it - and postfix / exim / qmail dont implement DSN at all > > Postfix now supports DNS: > > Major changes with snapshot-2924 > > > DSN formatted bounced/delayed mail notifications, finally. The > human-

Re: Multiple [*.log] file attachements from script

[Note: moved to mutt-users only!] > I am using mutt to send e-mail messages to the development group > following a product build/compile. Now I am writing some scripts for a > new product which is made out of multiple modules each of which will be > built individually. I may find myself in a situ

Re: alias list expansion

JT Williams writes: > Hi, > > How can I request that mutt does *not* expand an alias list? > Suppose I have > > alias foo-workers worker1, worker2, ... > > and I send a message to `foo-workers'; I do *not* want the To: > field to be expanded into the names of everyone on that list.

Re: Saving messages w/o the headers

> is there a slick way to save 'read' messages to a folder w/o all those > space-wasting headers? Or am I forced to run the folder file through a > 'filter' script? TIA... In many cases, I find the headers more useful than the contents ...

Re: Help...I forgot...

Scott Davis writes: > Please forgive my short memory. > > I know when you compose a message in mutt, and you are at the final screen > preparing to send, you can change the "From:" line with CTRL > or ALT . I just forgot. Thanks in advance, Close, but no cigar ;-) Pressing "?" in the send

Re: How handle HTML emails?

Dr. Christian Seberino writes: > How do people read HTML emails? If I'm in a good mood, I ask the poster to switch it off. Otherwise >/dev/null.

Re: lag

Igor Pruchanskiy writes: > I am having some serious lag sending mail to this list. > Is that normal ? Takes about 20 min to show up on the list This certainly cannot be called "serious"!

Re: debian-user save hook

> I do it like this in my muttrc, is there a better way, maybe one > that works for all subscribed lists with a single command? > > subscribe mutt-users@ > fcc-save-hook '~C mutt-users' =mutt-users > > subscribe sawfish@ > fcc-save-hook '~C sawfish'=sawfish In addition to the

Re: printf format

> For example: the index format uses %-15.15L > And I found out that these 15.15 is working like the C printf. > So I tried to find some info which explains what C printf is. > The only thing I found was some complicated mathematics about this > being a format of telling how a printer is going t

Re: Orphaned tmp files?

Jim Lambert writes: > I've noticed that mutt occasionally forgets to clean up tmp files. > It seems to be an intermittent problem and I was wondering if other > users had seen it. > > -Jim > > > mutt -v > Mutt 1.2.5i (2000-07-28) > Copyright (C) 1996-2000 Michael R. Elkins and others. > Mutt co

Re: Pb with this mailing list

Andre Berger writes: > Whenever I post to this list, I get an undeliverable mail-receipt, > saying > > [EMAIL PROTECTED] > Too many "Received" headers - suspected mail loop > > This has begun about a week (or two) ago. How to deal with the > situation? More than likely a mail loop

Re: How to display a mail in raw format

> I was wondering how one can display any mail in it's pure, raw format within Mutt. >So as to get the same result than if I would load the mbox file into an editor and >look at a particular message. e edit edit the raw message if you can exit your editor without

Re: [OT - Procmail] Filter UU/XXencode and HTML?

> This time, I'm wondering how to convert XX/UU-encoded stuff (which, > after what I've noted, can be difficult in MUTT when some broken > mailer was there before) into proper MIME attachments. > > Also, I wonder how in the world shall I make procmail take a > (optionally MIME-encoded) message w

Re: vim procmail recipe

> How about: > > :0 Whc: msgid.lock > | formail -D 8192 msgid.cache > > :0 a: dupes.lock > $HOME/Mail/duplicates > > This is the super safe version; if you're confident w/ this, you can > drop the second recipe and the c flag from the first. It's not a matter of confidence. This _is_ the sa

Re: [Fwd: mutt+gpg=screen_corruption] -> output redirection

> > Is that something mutt should take care of automatically > > (unexpected output of some commands, that is)? > > How does a program catch "unexpected things"? > Besides, if it expected anything they would > not be unexpected, now, would they? ;-) I kind of expected a reply like this ;-)

Re: [Fwd: mutt+gpg=screen_corruption]

Argh, I hate following up myself ... Lars Hecking writes: > > I'm fwd'ing this for someone who is not reading the list. Any ideas? > > The problem is that every time he hits a signed message (during the > same mutt session), the status line at the bottom gets c

[Fwd: mutt+gpg=screen_corruption]

I'm fwd'ing this for someone who is not reading the list. Any ideas? The problem is that every time he hits a signed message (during the same mutt session), the status line at the bottom gets corrupted more and more. It happens under xterms, gnome-terms, and the linux console. All relevan

Re: procmail mailing list strategy (was Re: vim procmail recipe)

> Here is how I deal with mailing lists in my .procmailrc: > # eliminate duplicate messages > :0Wh: msgid.lock > | formail -D 16384 archive/msgid.cache This is *bad*. If procmail fails somewhere after dupes checking and the message is requeued, the next delivery attempt wi

Re: [MAILER-DAEMON@localhost.localdomain: Returned mail: see transcript for details]

Suresh Ramasubramanian writes: > Lars Hecking proclaimed on mutt-users that: > > > And most of their dialups/dsl boxes etc. are so open you could drive > > an aircraft carrier through ... > > Lars - you got mail.com confused with someone else. They don't d

Re: [MAILER-DAEMON@localhost.localdomain: Returned mail: see transcript for details]

> > >>> MAIL From:<[EMAIL PROTECTED]> > > <<< 553 sorry, your sender is not liked (#5.7.1) > > 501 5.6.0 [EMAIL PROTECTED] Data format error > > If kde.org is blocking mail.com, what can we (or mutt) do? That's understandable. One of our users, long gone, seems to have set up a fwding accou

Re: Procmail & user+ext@bla.com addresses

> I think he was looking for a somewhat more general solution:) Maybe: > > :0: > * ^TO_user+\/.*@her\.com > `echo $MATCH | sed "s/@.*//"` > > Untested, of course. (You might have to escape the "+" in the second > line, cannot remember the procmail regex syntax right now, too late:) Yes, you h

Re: Procmail & user+ext@bla.com addresses

Ralf Hildebrandt writes: > I can use a (folder)-hook to set my From: header and envelope from to > [EMAIL PROTECTED] > But how can I motivate procmail to filter my mail into > /home/user/Maildir/muttusers > if a mail to [EMAIL PROTECTED] comes back in? What about :0: * ^TO_user+muttusers@her\.c

Re: Mutt, procmail, and sendmail

> > [Splutter] Useless Use of cat. > > > > > > Thanks, Lars, for that marvelously helpful comment. I didn't > find any better solution on my own, though. There is none. The problem, as you stated correctly, is that mutt passes sender and recipient addresses to $sendmail on the command l

Re: your mail

> Well, passing the message to a very simple one line script seems > to work. I made a ~/.mutt/mailout (mode +x to make it > executable): > > #!/bin/sh > cat | procmail ~/.procoutrc > # End of ~/.mutt/mailout [Splutter] Useless Use of cat.

Re: Sending mail with attachment from a shell script

Cristian Gheorghe writes: > Hello, > > I am trying to use mutt in order to be able to send e-mail notifications > in regards to the nightly source code builds that I am doing. Something > to the extent of "Build Failed", see attached file. > > I can see how to attach a file, specify the address,

Re: hostname

> I sent two msgs to two members of Mutt-Users' List (directly to their > email address) and both msgs were bounced back because of the ff. errors: So that was you ... > How can I fix the problem? Before I set ~/.procmailrc everything seems > fine. Could the error be cause by ~/.procmailrc?

Re: Minor build problem with 1.3.16i

> I have just built mutt 1.3.16i and had a (minor) problem. This is mutt-users. mutt-1.3.16.i is a development version, and feedback about this version should go to mutt-dev. The solution to your problem is in the mutt-dev archives. In fact, it was even posted here less than a week ago. >

Re: outlook 2000 attachments

> > There are plenty. Off my head, I can think of Convert-TNEF on CPAN, > > and a standalone conversion program called tnef on > > http://world.std.com/~damned/software.html. > > Amavis uses (or rather, requires) this damned program afaict. I find it extremely funny that you should mention

Re: outlook 2000 attachments

> Encapsulation Format." The product I QA for can read these, but there > isn't any publicly available code that I'm aware of to decompose TNEF > files. There are plenty. Off my head, I can think of Convert-TNEF on CPAN, and a standalone conversion program called tnef on http://world.std.com

Re: mutt 1.3.16i build problem

Marcelo Martinelli writes: > i have been trying to build mutt 1.3.16 on my machine (RH 7.0) and > when i run ./configure i get the following error message: > > sed: can't read ./doc/instdoc.sh.in: no such file or directory > > can anyone help. http://groups.yahoo.com/group/mutt-dev/message/102

Re: sending attachments

Mullen A.J. writes: > To elaborate on my earlier question about including attachments, > the following is what I'm sending out. This is the raw text of the > mail. When Mutt receives this, it's able to parse it without a problem > and treat the attachments and text appropriately. When other mai

Re: A newbie question regarding sending mail and the time it takes

Per Dalum Jensen writes: > Hi all! > > I've just downloaded and installed mutt on a Solaris system and have a > question. When I send a mail, it takes allmost forever for Mutt to > complete the action and return the control to me. Is that normal or is > there something I can do to change this beh

Re: how to overried mime types?

Michael S. Tsirkin writes: > Hello! > I get lots of mail from Outlook which all have attachments > of the type "application/octet-stream". > I would like in this case to use file extension to > select the viewer for the attachment. This is precisely what Dave Pearson's mutt.octet.filter does.

Re: autoconf and mutt-1.3.14

> Well, now I understand the directory structure of the mutt site a > little better, so in the future I won't get lost again. But is there > any documentation that would direct people to the "devel" directory > instead of "snapshots"? The intended target audience for devel hangs out on mutt-de

Re: autoconf and mutt-1.3.14

> Now I realize that this tarball probably contains the same data as > what I would have gotten if I went directly to CVS, and therefore, I > now see that the `prepare' script applies to this tarball, as well. Correct. The tarball you downloaded is a daily (or nightly :) snapshot of the cvs.

Re: autoconf and mutt-1.3.14

Michael Tatge writes: > Lloyd Zusman muttered: > > I have recently downloaded the current unstable mutt release, version > > 1.3.14. It doesn't come with a `configure' script > > Mine does: Maybe he downloaded the cvs version? It does indeed not have a configure script, and one needs to run t

Re: permission denied

> I entered the "application/octet-stream; /usr/local/bin/mutt.octet.stream > %s; copiousoutput" > in my /etc/mailcap file. I get the error: permission denied. In > /usr/local/bin, I have: > -rw-r--r-- 1 userid userid .. . mutt.octet.stream > > How do i fix this?. chmod a+x

Re: mutt-1.25.i message id errors

> Not me, a list-user ... I just get the crap bounces ... Oops, sorry, I misread your message. You are refering to <[EMAIL PROTECTED]>? Still, what I posted applies. The problem can be remedied by setting hostname explicitly in .muttrc. Besides, bouncing emails with malformed bad messag

Re: mutt-1.25.i message id errors

Steve Kennedy writes: > I dont know whether it's mutt or the mta, however someone > on the lists here was using mutt and generating a header > of the form > > > Message-ID: > > Which was being rejected by lots of MTA's (and thus causing > bounces). > > Is this mutt ? I guess mutt doesn't kno

Re: mutt and Maildir support

> Might be. But Procmail-3.15.1 can do this without a patch. > Isn't it great if an author accepts patches to his program... The procmail author hasn't been involved with the software in years!

Re: mutt and Maildir support

Ralf Hildebrandt writes: > Basically just a very basic question: You'll get a very basic answer, too :) > mutt can use Maildir type folders. But how can I tell procmail to sort my > Mail into Maildir type folders instead of Mbox type folders? man procmailrc. And you definitely want procmail

Re: Sender

Ilya writes: > Can I stop mutt from putting sender header? I have two domains setup on my > system. alchemistry.net and krel.org. The bsd's main host is > alchemistry.net. But my email is usually from @krel.org. I noticed that in > headers there is > User-Agent: Mutt/1.2.5i > Sender: Ilya Krel <[E

Re: mutt & postfix

[Please don't sign list email, or upload your key to one of the public keyservers. Thank you.] geoffrey writes: [..] > The problem is that I cannot get mutt to hand off mail to postfix for > delivery. When I attempt to send email, mutt stops with the message: > > "Error sending message, chil

Re: gnupg vs pgp?

Ralf Hildebrandt writes: > On Thu, Dec 14, 2000 at 07:44:57PM +0100, Thorsten Haude wrote: > > > >Yup. We're the good guys > > Well, I wouldn't go this far. > > We're considerably better than the most :) Sure. "Am deutschen Wesen soll die Welt genesen." Heard that before. Didn't like it.

Re: compressed mailbox & mutt

Please trim your long lines next time. > But when I try to access this oldlih.gz I am getting the message for a split second >decompressing oldlih.gz and than the mutt bar displays the message no mailbox. >What's wrong ? It's called *compressed* folders patch - not "tar'ed and compressed"

Re: gnupg vs pgp?

This is getting kind of off-topic for this list ... > Is the German government just as much a police state as the US? I'm not > sure, but I suspect that -- in spite of their Orwellian ban on teaching > the history of Germany in the 1930s and 1940s and other evidence -- they > are not. I am Ge

Re: Question regarding clearsigning emails automatically

[EMAIL PROTECTED] writes: > Hi, > I would first like to thank Graham, Brian, and Andrew for their responses to >my question regarding clearsigning my emails. As you can see, this message is >clearsigned. Please trim your lines to 72-76 chars per line. Thank you. IMHO signing list emai

Re: gnupg vs pgp?

Myrddin writes: > Just like the subject says. > > I see on the mutt homepage that gnupg is recommended over pgp. Are there > reasons for this beyond the whole 'use gnu whenever possible because of their > licensing'? Or are there real, functional reasons behind choosing gnupg over > pgp? Much

Re: From: depending on To:

> I want my mutt to use different "From: " field values depending on the "To: > " field. I managed to get it almost to work with the send-hook, but the > problem is that the "From: " field changed with "my_hdr" directive doesn't > get changed back to the default after sending the mail. Add ano

Re: [1.2.5] resend-message

Vincent Lefevre writes: > The resend-message function isn't documented in the manual. I submitted a patch for this back in August. It went straight into cvs (and 1.3.x). > Moreover, it doesn't set the Bcc and Fcc fields (unlike the > other send functions).

  1   2   3   4   >