RE: Error when sending mail
Thanks for the hint. I'm using qmail's sendmail wrapper. The sendmail binary is executable and all qmail processes are running. cheers -Original Message- From: Suresh Ramasubramanian [mailto:[EMAIL PROTECTED]] Sent: Friday, January 19, 2001 7:15 AM To: '[EMAIL PROTECTED]' Subject: Re: Error when sending mail Redak, Dorian proclaimed on mutt-users that: > Dear All! > When sending mail I receive the following error: > Error sending message, child exited 127 (Exec error.) Sendmail (or whatever MTA you have) is not running I expect. Start it -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Error when sending mail
On Fri, Jan 19, 2001 at 09:17:07AM +0100, Redak, Dorian wrote: > Thanks for the hint. > I'm using qmail's sendmail wrapper. The sendmail binary is executable and > all qmail processes are running. Do you have dsn_notify or dsn_return enabled? If so, don't. qmail doesn't support DSN. Brian
Re: Default mailbox display?
On Thu, Jan 18, 2001 at 09:01:42PM -0800, Trae McCombs wrote:
> One thing that I think would help not only me, but tons of others is
> something like this:
>
> mailbox 1 3 new messages
> mailbox 2 12 new messages
> mailbox 3 8 new messages
>
>
> Where you had the "status bar" that you could move up and down between
> mailboxes... and then you would get into the messages of that mailbox.
Although it doesn't give you the count you're after it sounds more or less
like you're asking for the screen you'll be presented with if you start mutt
with the "-y" switch ("man mutt" lists all the available switches).
If you want mutt to do this on startup you could create an alias or
something or stick this:
,
| push "?"
`
at the end of your ~/.muttrc.
> I'd also think it would be cool to have some sort of key binding that
> would allow you to get back out to the main mailbox once deep in another
> mailbox so you wouldn't have to quit.
That's what the macro system is for. For example:
,
| macro index "h" "!\n"
`
choose the key of your choice (in the above "h" (for "home") would be the
key, look at the binding list (help screen) for the section of mutt in
question to see that you won't be overriding a useful binding), also
remember to define the macro for the pager and anywhere else that makes
sense.
Or, perhaps, when you say "main mailbox" you mean the initial display you're
talking about? If so you can use the macro system again. For example:
,
| macro pager "y" "?"
`
with the above in place pressing "y" in the pager would take you back to the
screen you get when you do a "mutt -y".
> Sorry I'm such a lamer, especially if this is something easy to fix. If
> someone has the time, and can provide a .muttrc to accomplish this, or
> better still, what I need to toss into my .muttrc, I would be forever in
> your debt. :)
The debt is noted. :>
--
Dave Pearson: | mutt.octet.filter - autoview octet-streams
http://www.davep.org/ | mutt.vcard.filter - autoview simple vcards
Mutt: | muttrc2html - muttrc -> HTML utility
http://www.davep.org/mutt/ | muttrc.sl - Jed muttrc mode
Re: Default mailbox display?
I also wanted to use my arrow keys to navigate through folders. (like I did in pine.) what I have now is: macro index "?" this binds the key to get you to the change-folder menu, f you are in the message index. (I think you need the mailboxes command to tell mutt which folders you have) also, I did: bind pager exit this will get me from the pager back to the index. On Thu 2001-01-18, Trae McCombs wrote: > Hey gang, > Sorry to bug *. I have a question that has long plagued me with using > Mutt. I've always had to have everything come to one mailbox, and then > simply leave everything in one huge archive. > > I have procmail setup, and that's great, but I hate having to change into > the mailboxes to see if there is anything new in those mailboxes. > > One thing that I think would help not only me, but tons of others is > something like this: > > mailbox 1 3 new messages > mailbox 2 12 new messages > mailbox 3 8 new messages > > > Where you had the "status bar" that you could move up and down between > mailboxes... and then you would get into the messages of that mailbox. > > I'd also think it would be cool to have some sort of key binding that > would allow you to get back out to the main mailbox once deep in another > mailbox so you wouldn't have to quit. > > Anyhoo... > Sorry I'm such a lamer, especially if this is something easy to fix. If > someone has the time, and can provide a .muttrc to accomplish this, or > better still, what I need to toss into my .muttrc, I would be forever in > your debt. > :) > > Yours, > Trae > > -- > Trae McCombs | [EMAIL PROTECTED] > Community Evangelist > 1 888 546 8948 ext. 76900 > Founder: Themes.org -- Linux.com > http://octobrx.com/ -- Personal page
Re: Default mailbox display?
On Fri, Jan 19, 2001 at 09:27:53AM +, Dave Pearson wrote:
> On Thu, Jan 18, 2001 at 09:01:42PM -0800, Trae McCombs wrote:
>
> > One thing that I think would help not only me, but tons of others is
> > something like this:
> >
> > mailbox 1 3 new messages
> > mailbox 2 12 new messages
> > mailbox 3 8 new messages
how about this ?
Mail/mutt-users [Msgs:413 New:18 1.1M]
Mail/sf/vuln-dev [Msgs:141478K]
Mail/nymip [Msgs:54 368K]
now wouldn't that be nice ?
> >
> >
> > Where you had the "status bar" that you could move up and down between
> > mailboxes... and then you would get into the messages of that mailbox.
>
> Although it doesn't give you the count you're after it sounds more or less
> like you're asking for the screen you'll be presented with if you start mutt
> with the "-y" switch ("man mutt" lists all the available switches).
the problem with "-y" is that it simply doesn't work reliably.
to quote the docs:
---
Note: new mail is detected by comparing the last modification time to
the last access time. Utilities like biff or frm or any other program
which accesses the mailbox might cause Mutt to never detect new mail
for that mailbox if they do not properly reset the access time. Backup
tools are another common reason for updated access times.
---
same happens when you change to one of those folders and you quit
without saving changes to another folder. if you change into that
folder again you will see mails marked as new though the folder was
not marked by "N" in the folder menue.
i'm not sure if saving a mail from your main incoming folder to one of
the other folders will reset its access time as well .. havn't tried
yet.
BTW: unread but old mail is not detected that way at all.
i see the problem but i have not yet seen a correct solution to it.
i guess i could hatch one if somebody told me how mutt recognizes new
and unread mail inside a folder. yes i am to damn lazy to read the
source :-)))
-heinrich
--
Heinrich Langos <[EMAIL PROTECTED]>
pgp: http://wh9.tu-dresden.de/~heinrich/pub_pgp_key.asc
_
|o| The reason we come up with new versions is not to fix bugs. |o|
|o| It's absolutely not. It's the stupidest reason to buy a new |o|
|o| version I ever heard. -- Bill Gates, Microsoft Corporation |o|
~
Re: German umlauts and alternates in Mutt.
Jens Paulus muttered: > 1.) How can I configure Mutt and teach it to display German umlauts? I could > not find any instructions in Mutt's manual about this topic. In the default > settings, it always replaces these special characters by a question mark (`?') > in the builtin pager and by a dot (`.') in the normal index and compose index. set charset="iso-8859-1" > 2.) If I use "set [EMAIL PROTECTED]", Mutt considers > [EMAIL PROTECTED] as one of my email addresses. But now I want Mutt consider > two or more addresses as belonging to me, how can I do this? > "set [EMAIL PROTECTED],[EMAIL PROTECTED]" doesn't work. Quoting the manual: alternates Type: regular expression set [EMAIL PROTECTED]|[EMAIL PROTECTED] > If you could give me an advice how to change these settings I would be > thankful. I'm still using Mutt 1.0.1i (2000-01-18). I would consider an upgrade since many bugs are fixed in recent versions. HTH, Michael -- Your job is being a professor and researcher: That's one hell of a good excuse for some of the brain-damages of minix. (Linus Torvalds to Andrew Tanenbaum) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
Re: Default mailbox display?
On Fri, Jan 19, 2001 at 12:24:40PM +0100, Heinrich Langos wrote:
> On Fri, Jan 19, 2001 at 09:27:53AM +, Dave Pearson wrote:
> > On Thu, Jan 18, 2001 at 09:01:42PM -0800, Trae McCombs wrote:
> >
> > > mailbox 1 3 new messages
> > > mailbox 2 12 new messages
> > > mailbox 3 8 new messages
>
> how about this ?
>
> Mail/mutt-users [Msgs:413 New:18 1.1M]
> Mail/sf/vuln-dev [Msgs:141478K]
> Mail/nymip [Msgs:54 368K]
>
> now wouldn't that be nice ?
Nice, be expensive. Each mailbox would have to be read to get that
information (at least, that's true for mbox style mailboxes).
> > Although it doesn't give you the count you're after it sounds more or less
> > like you're asking for the screen you'll be presented with if you start mutt
> > with the "-y" switch ("man mutt" lists all the available switches).
>
> the problem with "-y" is that it simply doesn't work reliably.
Yes it does.
> to quote the docs:
> ---
> Note: new mail is detected by comparing the last modification time to
> the last access time. Utilities like biff or frm or any other program
> which accesses the mailbox might cause Mutt to never detect new mail
> for that mailbox if they do not properly reset the access time. Backup
> tools are another common reason for updated access times.
> ---
That quote is informing you that if you allow other tools to modify the
timestamps. It doesn't say that mutt's detection of mailboxes with new mail
is unreliable.
> same happens when you change to one of those folders and you quit without
> saving changes to another folder. if you change into that folder again you
> will see mails marked as new though the folder was not marked by "N" in
> the folder menue.
The "N" status of a mailbox tells you that it has been updated since you
last read the mailbox.
--
Dave Pearson: | mutt.octet.filter - autoview octet-streams
http://www.davep.org/ | mutt.vcard.filter - autoview simple vcards
Mutt: | muttrc2html - muttrc -> HTML utility
http://www.davep.org/mutt/ | muttrc.sl - Jed muttrc mode
Re: how to "toggle-signature" display in pager?
On Thu, Jan 18, 2001 at 10:51:58PM -0500 or so it is rumoured hereabouts, mike polniak thought: > Many of the signatures are getting larger than the informational > part of the message. I would like to remove this clutter from the pager > with something like "toggle-signature" which would be analogous to toggling > the display of quoted material in the message with toggle-quoted. > Anyone have a ready solution for this new "toggle-signature" > function? You could try color signature black black in .muttrc. You'll get lots of empty lines for long sigs but, at least, no text clutter You dould bind a key to that and another to display the sig with some other colours. -- Conor Daly <[EMAIL PROTECTED]> Domestic Sysadmin :-) - 9:44am up 3 days, 10:03, 1 user, load average: 0.19, 0.20, 0.10
Re: Default mailbox display?
Hi Heinrich, > > > One thing that I think would help not only me, but tons of others is > > > something like this: > > > > > > mailbox 1 3 new messages > > > mailbox 2 12 new messages > > > mailbox 3 8 new messages > > how about this ? > > Mail/mutt-users [Msgs:413 New:18 1.1M] > Mail/sf/vuln-dev [Msgs:141478K] > Mail/nymip [Msgs:54 368K] > > now wouldn't that be nice ? This implies that mutt scans all folders with new mail (at least with mbox style folders)to determine the new-mail-count. This could be a huge performance loss at start up. Ciao for now, Dirk -- Dirk Ruediger, Rostock, Germany
RE: Error when sending mail
Thanks to all, problem is solved: set sendmail="/var/qmail/bin/qmail-inject" -Original Message- From: Brian D. Winters [mailto:[EMAIL PROTECTED]] Sent: Friday, January 19, 2001 9:57 AM To: Redak, Dorian Cc: [EMAIL PROTECTED] Subject: Re: Error when sending mail On Fri, Jan 19, 2001 at 09:17:07AM +0100, Redak, Dorian wrote: > Thanks for the hint. > I'm using qmail's sendmail wrapper. The sendmail binary is executable and > all qmail processes are running. Do you have dsn_notify or dsn_return enabled? If so, don't. qmail doesn't support DSN. Brian
Re: Encrypting attachments with GnuPG so that Eudora can see it... SOLUTION
MM -- ...and then msquared said... % On Wed, Jan 17, 2001 at 01:23:06PM -0500, David T-G wrote: % % > encrypt and sign a message to Eudora users. As far as I can tell, you % > can only send with pgp_create_traditional, and I haven't even seen % > attachments working with encryption. % % Yes! I figured it out! Hey, awesome! % % In order to send encrypted attachments and such to Eudora, the MIME % content that is encrypted MUST have the following as its FIRST header: % % MIME-Version: 1.0 Very interesting. % % Anyone know the correct procedure for notifying the development team? % Anyone know if they already know about it? Well, you certainly don't reply just to me :-) I've bounced your email over to mutt-users, but you could also drop a note to mutt-dev. I think there might even be a "bugs" address or a muttbug script, but I haven't looked in a while; dig through your source to see. % % Anyone know how you could configure Mutt to do that without modifying the % source? :) That doesn't sound like a type you could easily set, but perhaps your sendmail directive could really just be a script that will add that for you for certain addresses and then send it on... % % 2 % Regards, /|/| % / | :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! PGP signature
Re: Error when sending mail
On Fri, Jan 19, 2001 at 11:45:24AM +0530, Suresh Ramasubramanian wrote: >Redak, Dorian proclaimed on mutt-users that: > >> Dear All! >> When sending mail I receive the following error: >> Error sending message, child exited 127 (Exec error.) > > Sendmail (or whatever MTA you have) is not running I expect. Start it Typically, the Sendmail daemon doesn't have to be running. Sendmail will simply deliver the mail. A noted exception would be if the configuration (i.e., sendmail.cf) specifies queueing-only mode. That (semi-obviously) would throw the mail into the spool directory, and then yes, the daemon has to be running to do queue runs. What's more likely is that sendmail is not in PATH. One reason for this might be that Sendmail isn't on the system at all :^) -- Oo---o, Oo---o, O-weem-oh-wum-ooo-ayyy In the jungle, the silicon jungle, the process sleeps tonight. Joe Philipps <[EMAIL PROTECTED]>, http://www.philippsfamily.org/Joe/ public PGP/GPG key 0xFA029353 available via http://www.keyserver.net PGP signature
Procmail Filtering
Good day/night everyone, I know this is not the place for this, but I'll give it a try anyways. A couple of months ago I found myself in the need of changing the "Realname" part of an email. To make myself a little clear, I tried to change: 'JOSEFINA EDWARDS to Sophy Edwards'. For this I users procmail and a little filter someone wrote for me. But to this day It's still to work. I've read the manual page for procmailrc a thousand times and still, I haven't found out the way of doing this. I emaild this list with the hope that someone can help me out or at least point me in the right direction. These are the lines I added to my .procmailrc: :0 FBw * ^From:.*JOSEFINA | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g' These are the lines I get from my .procmail_log: procmail: Skipped "FBw" From [EMAIL PROTECTED] Fri Jan 19 09:56:54 2001 Folder: /root/mail/Inbox I put the email '[EMAIL PROTECTED]' in order to maintain the email anonymnous. Thanks in advanced, Nelson D. Guerrero
Re: how to "toggle-signature" display in pager?
Conor Daly wrote: > On Thu, Jan 18, 2001 at 10:51:58PM -0500 or so it is rumoured hereabouts, > mike polniak thought: > > Many of the signatures are getting larger than the informational > > part of the message. I would like to remove this clutter from the pager > > with something like "toggle-signature" which would be analogous to toggling > > the display of quoted material in the message with toggle-quoted. > > Anyone have a ready solution for this new "toggle-signature" > > function? > > You could try > > color signature black black > > in .muttrc. You'll get lots of empty lines for long sigs but, at least, > no text clutter > > You dould bind a key to that and another to display the sig with some > other colours. he configuration command color works ok, but you can only bind to a function not a command. Unfortunately uncolor does'nt apply here either. Since Mutt already detects signature for the color command, the code could be probably be changed there, although i am not a programmer i might give it a try.
Re: Procmail Filtering
On Fri, Jan 19, 2001 at 11:17:29AM +, Nelson wrote: > These are the lines I added to my .procmailrc: > > :0 FBw > * ^From:.*JOSEFINA > | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g' what is "F"?, "f" is filter so do you mean fBw? -- Frank Booth - Consultant
Re: Encrypting attachments with GnuPG so that Eudora can see it... SOLUTION
On Wed, Jan 17, 2001 at 01:23:06PM -0500, David T-G wrote: > % PROBLEM: > % > % Suppose I send a GPG-encrypted email that has an attachment. I then send > % it to someone who is using Eudora 5.0 with PGP Freeware 6.5.8 to read > % their email. > > That's certainly a problem -- a known one. You're right; you cannot > encrypt and sign a message to Eudora users. As far as I can tell, you > can only send with pgp_create_traditional, and I haven't even seen > attachments working with encryption. Yes! I figured it out! In order to send encrypted attachments and such to Eudora, the MIME content that is encrypted MUST have the following as its FIRST header: MIME-Version: 1.0 Anyone know the correct procedure for notifying the development team? Anyone know if they already know about it? Anyone know how you could configure Mutt to do that without modifying the source? :) 2 Regards, /|/| / |
Re: Procmail Filtering
* On Fri Jan 19 2001, Frank Booth screamed: -> On Fri, Jan 19, 2001 at 11:17:29AM +, Nelson wrote: -> > These are the lines I added to my .procmailrc: -> > -> > :0 FBw -> > * ^From:.*JOSEFINA -> > | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g' -> -> what is "F"?, "f" is filter so do you mean fBw? -> -> -- -> Frank Booth - Consultant Frank, I changed the 'F' for the 'f' and I got the following lines in my .procmail_log procmail: Extraneous filter-flag ignored procmail: Skipped "| sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g'" From [EMAIL PROTECTED] Fri Jan 19 11:47:04 2001 Folder: /home/nelsong/mail/Inbox 568
Re: Encrypting attachments with GnuPG so that Eudora can see it... SOLUTION
* msquared <[EMAIL PROTECTED]> [010119 15:53]: > Yes! I figured it out! In order to send encrypted attachments and > such to Eudora, the MIME content that is encrypted MUST have the > following as its FIRST header: > > MIME-Version: 1.0 > > Anyone know the correct procedure for notifying the development team? > Anyone know if they already know about it? Anyone know how you > could configure Mutt to do that without modifying the source? :) This is a problem of Eudora, right? Tell the Eudora developers! Adding workarounds to mutt for other broken software is WRONG! After all, a workaround for mutt just solves this for mutt - but not for users of other mailers when sending to Eudora. Summary: Eudora is broken - fix Eudora! Sven
Re: Procmail Filtering
Quoting Nelson D. Guerrero <[EMAIL PROTECTED]>: > * On Fri Jan 19 2001, Frank Booth screamed: > -> On Fri, Jan 19, 2001 at 11:17:29AM +, Nelson wrote: > -> > These are the lines I added to my .procmailrc: > -> > > -> > :0 FBw > -> > * ^From:.*JOSEFINA [--- snipped intermediate message where 'F' was changed to 'f' ---] Don't believe you need the 'B' in there, you are matching on the Header lines not the body lines. BEgrep the body. -Doug -- *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=* Douglas L. Potts Spectral Systems, Inc. Url: http://www.bigfoot.com/~pottsdl "There are no real ANSWERS; just cross references..." - Steve Presutti 7/31/97 *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Re: Procmail Filtering
* On Fri Jan 19 2001, Douglas L . Potts screamed: -> [--- snipped intermediate message where 'F' was changed to 'f' ---] -> Don't believe you need the 'B' in there, you are matching on the Header -> lines not the body lines. -> -> B Egrep the body. -> Ok, I removed the 'B' from the filter, But I keep getting: procmail: Extraneous filter-flag ignored From [EMAIL PROTECTED] Fri Jan 19 12:40:04 2001 Subject: Test Folder: Inbox673 and my .procmailrc reads: :0 fw ^From:.*[EMAIL PROTECTED] Inbox | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g'
SCO version?
I'm trying to get mutt working on SCO Unix OSR5, without much success. SCO does distribute a pre-compiled copy as part of their "Skunkware" project, but it is version 0.93.1 and there seems to be a problem with the From: field when sending messages (it comes up root@@, which can't be replied to). Also, I don't want to distribute a beta to my customers. I've downloaded the most recent source package, and installed gcc on my SCO test drive, but when I run compile it tells me my gcc doesn't work: checking whether the C compiler works... no configure: error: installation or configuration problem: C compiler cannot create executables. I'm hoping somebody can either help me through these problems or send me a compiled copy for SCO. All we're trying to do is send an email with an attachment from the command line - I don't need any of the fancy stuff working. All I should need is the mutt executable itself, along with anything it's dependent upon. Thanks, Steve -- Steven J Hall Lamneth Inc Phone: 504/887-2112 Unix System AdministrationPager: 504/565-2112 Metairie LA Fax: 504/887-0422
Re: Procmail Filtering
Quoting Nelson D. Guerrero <[EMAIL PROTECTED]>: [--- snip ---] > procmail: Extraneous filter-flag ignored > From [EMAIL PROTECTED] Fri Jan 19 12:40:04 2001 > Subject: Test >Folder: Inbox673 > > and my .procmailrc reads: > > :0 fw > ^From:.*[EMAIL PROTECTED] > Inbox > | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g' What's this second line for??? You didn't mention that one before. As is, it never gets to the filter line, you've already put the mail in your INBOX. Try this instead: :0 fw ^From:.*[EMAIL PROTECTED] | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g' >> INBOX -Doug -- *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=* Douglas L. Potts Spectral Systems, Inc. Url: http://www.bigfoot.com/~pottsdl "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -Benjamin Franklin *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Re: German umlauts and alternates in Mutt.
Hello Jens! On Thu, 18 Jan 2001, Jens Paulus wrote: > Hi there, I have two questions. Why didn't read you the answers to the same question from ---> cut here < - From: Jens Paulus <[EMAIL PROTECTED]> Subject: German umlauts and alternates in Mutt. To: [EMAIL PROTECTED] Date: Tue, 12 Dec 2000 18:29:00 +0100 X-Mailer: Mutt 1.0.1i ---> cut here < - bye - Wilhelm -- .~. ___ _ _ ___ ___ __ __ /V\ | |(_) | __ \ | | | | \ \/ / Wilhelm Wienemann // \\ | |__ | | | | | | | |_| | || Amselweg 10 /( )\|| |_| |_| |_| \| /_/\_\ D-47546 Kalkar/Germany ^`~'^ powered by Linux - solutions for smart penguins
Re: Procmail Filtering
At 12:41 -0500 19 Jan 2001, "Douglas L . Potts" <[EMAIL PROTECTED]> wrote: > :0 fw > ^From:.*[EMAIL PROTECTED] > | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g' >> INBOX If you redirect the output to a file, the recipe is no longer working as a filter so the f flag should be removed. You should also tell procmail to use a lockfile by putting a colon at the end of the first line. Also you need an asterisk at the beginning of the condition line. Backslash quoting the dots (other than the first one) in this line would also be a good idea. The modified recipe would then be: :0w: * ^From:.*j\.edward@codetel\.net\.do | sed -e 's/"JOSEFINA EDWARD"/"Sophy Edwards"/g' >> INBOX -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ However, since procmail is the ultimate supply of rope for mail hacking, here are the directions for tying a noose: -- Philip Guenther
addressing problem
I am using mutt on an internal screened network and it seems that somehow my hostname and domainname are not getting put together properly. Let me explain. My FQDN machine name is bnoble.inhouse.us.lan (this is not the actual name) and the mail server that I am using is named mail.us.lan (again, this mail server is only internal). But, when the email goes out it should use a header of [EMAIL PROTECTED] as the sender. It does not do this as it should. My email goes out with the sendname of [EMAIL PROTECTED] instead of [EMAIL PROTECTED] Hence, some mail servers that I am sending to cannot resolve the sender domain and never accept the email. (This is a guess, but I see the mail still in my queue as "deferred" for this reason) I think that they think I am trying to relay mail or something. I can use netscape messenger on my system to send email to the same mail servers that are complaining about the mutt mail without a problem. This leads me to believe that mutt is at issue rather than any network configuration on my side (which I still highly suspect, but cannot prove given the fact that netscape msgr works fine). Any ideas?
Re: addressing problem
On Friday, January 19, 2001 (CS:5.03.019) 11:53:32 [AM] (-0800) Brian Noble [[EMAIL PROTECTED]] wrote... 1: Please trim your lines to 76-78 chars per line! THX 2: This list is [EMAIL PROTECTED] NOT [EMAIL PROTECTED] > I am using mutt on an internal screened network and it seems that somehow my > hostname and domainname are not getting put together properly.Let me explain Try one or more of these: (all in your muttrc) set envelope_from set hostname="yourhostnamehere.com" set from="Your Name <[EMAIL PROTECTED]>" set hidden_host=yes HTH mh -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Linux - Always running, never booting! - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - PGP signature
SSL Error, Mutt 1.2.5
I've compiled Mutt 1.2.5 on a Debian 2.2 (potato) system,
using the following configure options:
--enable-imap --with-ssl --enable-pop
The build goes fine, but when I attempt to connect to our
SSL-wrapped IMAP server, I get an error immediately after accepting
the site certificate. For example:
tres$ mutt -f '{imap/ssl}'
[I see:
-- Mutt: SSL Certificate check
(r)eject, accept (o)nce
]
I type "o", then Mutt fails with this error:
SSL connection using (NONE)
"imap" is the name of our IMAP server, which works fine
with Netscape Messenger with the "Use secure connection (SSL)"
option checked.
Any suggestions?
--
Tres Hofmeister <[EMAIL PROTECTED]> http://www.rap.ucar.edu/~tres/
Research Applications Program, National Center for Atmospheric Research
Re: addressing problem
A couple of this to check and try. The first thing to do is check your mail configuration. You can do this via a command line invocation of sendmail I like to set debug mode so I can see what sendmail sets the from header to. Unless the machine you're sending the mail from is visable on the internet your mail setup should set the from headers to the mailhub. This would of course be accessable from the outside and would in your case be known as "somewhere.com". The next thing you need to do is add an entry to your ".muttrc" file to set the FROM: header. The syntax is "set [EMAIL PROTECTED]". Frank On Fri, Jan 19, 2001 at 11:53:32AM -0800, Brian Noble wrote: > I am using mutt on an internal screened network and it seems that somehow my >hostname and domainname are not getting put together properly. Let me explain. > > My FQDN machine name is bnoble.inhouse.us.lan (this is not the actual name) and the >mail server that I am using is named mail.us.lan (again, this mail server is only >internal). But, when the email goes out it should use a header of >[EMAIL PROTECTED] as the sender. It does not do this as it should. My email goes >out with the sendname of [EMAIL PROTECTED] instead of >[EMAIL PROTECTED] Hence, some mail servers that I am sending to cannot resolve >the sender domain and never accept the email. (This is a guess, but I see the mail >still in my queue as "deferred" for this reason) I think that they think I am trying >to relay mail or something. > > I can use netscape messenger on my system to send email to the same mail servers >that are complaining about the mutt mail without a problem. This leads me to believe >that mutt is at issue rather than any network configuration on my side (which I still >highly suspect, but cannot prove given the fact that netscape msgr works fine). > > Any ideas?
Multi-Line Colored Quoting?
I really like mutt's ability to color quoted text. Unfortunately, it appears to only be able to recognize quotes on a single line. On some mailing lists I'm on, people use multiline quoting mechanisims that mutt doesn't understand. An example: This is the beginning of the quoted text. It continues for a bit and wraps onto other lines. This line doesn't have any prefix, but it's still quoted. My questions are three: Is it possible to have mutt colorize the entire quoted area above? If so, how? If not, can I have mutt filter a message through an external program before viewing the message? Not entirely mutt-related, but does anyone know, off the top of their head, if there are any perl modules for manipulating email messages. (If I have to parse the message externally, a perl module that understands headers and MIME would be a big help.)
Re: Multi-Line Colored Quoting?
On Fri, Jan 19, 2001 at 05:19:08PM -0500, Phil Gregory ([EMAIL PROTECTED]) wrote: > > Not entirely mutt-related, but does anyone know, off the top of their > head, if there are any perl modules for manipulating email messages. > (If I have to parse the message externally, a perl module that > understands headers and MIME would be a big help.) Dozens. See http://search.cpan.org/>. -Rich -- -- Rich Lafferty --- Sysadmin/Programmer, Instructional and Information Technology Services Concordia University, Montreal, QC (514) 848-7625 - [EMAIL PROTECTED] --
Re: Default mailbox display?
Hello Heinrich! On Fri, 19 Jan 2001, Heinrich Langos wrote: > On Fri, Jan 19, 2001 at 09:27:53AM +, Dave Pearson wrote: > > On Thu, Jan 18, 2001 at 09:01:42PM -0800, Trae McCombs wrote: > > > > > One thing that I think would help not only me, but tons of others is > > > something like this: > > > > > > mailbox 1 3 new messages > > > mailbox 2 12 new messages > > > mailbox 3 8 new messages > > how about this ? > > Mail/mutt-users [Msgs:413 New:18 1.1M] > Mail/sf/vuln-dev [Msgs:141478K] > Mail/nymip [Msgs:54 368K] > > now wouldn't that be nice ? What about 'frm Mail/mutt-users' or 'frm Mail/sf/vuln-dev' or 'frm Mail/nymip'? bye - Wilhelm -- MicroSoft "ILOVEYOU". Thanks for engineering a 100% Virus Enabled Platform! (C) by Al Hopper <[EMAIL PROTECTED]> 2 Jan 2001 on solarisonintel
Re: SSL Error, Mutt 1.2.5
On Fri, Jan 19, 2001 at 02:13:57PM -0700, Tres Hofmeister wrote:
> The build goes fine, but when I attempt to connect to our
> SSL-wrapped IMAP server, I get an error immediately after accepting
> the site certificate. For example:
>
> tres$ mutt -f '{imap/ssl}'
> [I see:
> -- Mutt: SSL Certificate check
> (r)eject, accept (o)nce
> ]
> I type "o", then Mutt fails with this error:
>
> SSL connection using (NONE)
This is not an error message, it's an informational message telling you
the SSL parameters used on the connection. Seeing 'NONE' there means that
the connection is *unencrypted*, and we all know that sending passwords
over an unencrypted link is not a good idea. Instead of 'NONE' you should
see something more like 'EDH-RSA-DES-CBC3-SHA' to indicate that the
connection is secure.
IIRC the reason for 'NONE' is that there's a slight mismatch between
client and server SSL protocols and versions. See below.
> Any suggestions?
Four words: RTFM =)
In this case the FM would be README.SSL:
--8<8<--
Troubleshooting
---
If after doing the above, you are unable to successfully connect, it
is likely that your IMAP server does not support one of the SSL protocols.
There exist three different protocols, TLSv1, SSLv2, and SSLv3. To check
each of these, you use the following:
openssl s_client -host -port -verify -debug -no_tls1
openssl s_client -host -port -verify -debug -no_ssl2
openssl s_client -host -port -verify -debug -no_ssl3
You can also combine the options until you get a successfull connect. Once
you know which options do not work, you can set the variables for non-working
protocols to know. The variables for the protocols are ssl_use_tlsv1,
ssl_use_sslv2, and ssl_use_sslv3.
--8<8<--
--
Tommi Komulainen [EMAIL PROTECTED]
GPG 1024D/68388EE66FD6 DD79 EB38 BF6F 3533 09C0 04A8 9871 6838 8EE6
PGP signature
pgp 6.5.8 encrypt fails
When invoked from mutt 1.2.5, pgp 6.5.8 fails when trying to encrypt to an untrusted (it works with a trusted key) key with the message: === Pretty Good Privacy(tm) Version 6.5.8 (c) 1999 Network Associates Inc. Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security, Inc. Export of this software may be restricted by the U.S. government. WARNING: Because this public key is not certified with a trusted signature, it is not known with high confidence that this public key actually belongs to: "xxx <[EMAIL PROTECTED]>". Encryption error For a usage summary, type: pgp -h For more detailed help, consult the PGP User's Guide. Press any key to continue... == But if pgp is invoked from the command line, it prompts: == WARNING: Because this public key is not certified with a trusted signature, it is not known with high confidence that this public key actually belongs to: "xxx <[EMAIL PROTECTED]>". Are you sure you want to use this public key (y/N)? == A "y" response encrypts properly, but the default "N" response gives: == Encryption error For a usage summary, type: pgp -h For more detailed help, consult the PGP User's Guide. == So the failure appears to be that mutt uses the default response of "N" instead of "y". I tried adding "+force" to the encryption line in pgp6.rc, because the pgp 6.5.8 Guide claims this will always force a "y" response. It does in some cases, but not to the above prompt. I searched the archives and found only the thread that Rod Pike started. He ultimately gave up on 6.5.8, but for a different reason. Are there any fixes to make mutt allow the user to respond to the prompt instead of hiding it and responding with the default? TIA -rex
Re: SSL Error, Mutt 1.2.5
On 2001-01-20, Tommi Komulainen <[EMAIL PROTECTED]> wrote: : : IIRC the reason for 'NONE' is that there's a slight mismatch between : client and server SSL protocols and versions. See below. Ah, thanks. That's helpful. : In this case the FM would be README.SSL: I've already tried all of Mutt's ssl_use_* options in various combinations, with no difference in the behaviour. The "openssl" tests all seem to be about the same, looks like there's a handshaking problem. The results are below. Maybe this is a problem with the stunnel "wrapper" I'm using on the IMAP server, though why it should work with Netscape Messenger is beyond me. tres$ openssl s_client -host imap -port 993 -verify -debug -no_tls1 verify depth is 0 CONNECTED(0003) depth=0 [EMAIL PROTECTED] verify error:num=18:self signed certificate verify return:1 depth=0 [EMAIL PROTECTED] verify return:1 9577:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:958:SSL alert number 40 9577:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:216: tres$ openssl s_client -host imap -port 993 -verify -debug -no_ssl2 verify depth is 0 CONNECTED(0003) depth=0 [EMAIL PROTECTED] verify error:num=18:self signed certificate verify return:1 depth=0 [EMAIL PROTECTED] verify return:1 9578:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:958:SSL alert number 40 9578:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:216: tres$ openssl s_client -host imap -port 993 -verify -debug -no_ssl3 verify depth is 0 CONNECTED(0003) depth=0 [EMAIL PROTECTED] verify error:num=18:self signed certificate verify return:1 depth=0 [EMAIL PROTECTED] verify return:1 9583:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:958:SSL alert number 40 9583:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:216: Last bit: here are a few representative log entries from the IMAP server: Jan 19 16:11:56 imap stunnel[20202]: /usr/sbin/imapd connected from 128.117.193.5:1843 Jan 19 16:11:56 imap stunnel[20202]: Generating Diffie-Hellman key... Jan 19 16:11:56 imap stunnel[20202]: could not load DH parameters Jan 19 16:11:56 imap stunnel[20202]: SSL_accept: error:0906D06C:PEM routines:PEM_read_bio:no start line Jan 19 16:11:56 imap /usr/sbin/imapd[20203]: port 2472 service init from 127.0.0.1 Jan 19 16:11:56 imap /usr/sbin/imapd[20203]: Broken pipe, while reading line user=??? host=UNKNOWN -- Tres Hofmeister <[EMAIL PROTECTED]> http://www.rap.ucar.edu/~tres/ Research Applications Program, National Center for Atmospheric Research
Re: pgp 6.5.8 encrypt fails
On Fri, Jan 19, 2001 at 02:52:33PM -0800, [EMAIL PROTECTED] wrote: > When invoked from mutt 1.2.5, pgp 6.5.8 fails when trying to encrypt > to an untrusted (it works with a trusted key) key with the message: [...] > So the failure appears to be that mutt uses the default response of > "N" instead of "y". I tried adding "+force" to the encryption line > in pgp6.rc, because the pgp 6.5.8 Guide claims this will always > force a "y" response. It does in some cases, but not to the above > prompt. > > Are there any fixes to make mutt allow the user to respond to the > prompt instead of hiding it and responding with the default? Correction: Mutt does pass the PGP query to the user, but a "y" response apparently does not get passed back to PGP. BTW, pgp6.rc has "+encrypttoself". pgp2rc does not. IMO, encrypttoself is a security risk because it's extremely easy to forget to turn it off when sending anonymously. And, most users of prior versions of PGP would not expect the default behavior of Mutt to have changed without warning.
Re: SSL Error, Mutt 1.2.5
On Fri, Jan 19, 2001 at 04:13:55PM -0700, Tres Hofmeister wrote: > I've already tried all of Mutt's ssl_use_* options in various > combinations, with no difference in the behaviour. The "openssl" > tests all seem to be about the same, looks like there's a handshaking > problem. The results are below. Are you sure you tried all the combinations? I managed to get a reasonable response from the server with the following command: openssl s_client -host imap.rap.ucar.edu -port 993 -verify -debug \ -no_tls1 -no_ssl3 So, 'unset ssl_use_tlsv1 ssl_use_sslv3' should fix this problem. > Maybe this is a problem with the stunnel "wrapper" I'm using on the IMAP > server, though why it should work with Netscape Messenger is beyond me. Maybe Netscape Messenger doesn't use OpenSSL...? :) -- Tommi Komulainen [EMAIL PROTECTED] GPG 1024D/68388EE66FD6 DD79 EB38 BF6F 3533 09C0 04A8 9871 6838 8EE6 PGP signature
resizing error - compiling
Reply-To: I am trying to fix an annoying problem in mutt in that it refuses to resize - stick at 24 lines for example. Installed ncurses 5.0 and tried [root@apple mutt-1.2.5]# ./configure --with-curses=/usr/include/ncurses ... during make, got this: cc -DSHAREDIR=\"/usr/local/share/mutt\" -DSYSCONFDIR=\"/usr/local/etc\"-DBINDIR=\"/usr/local/bin\" -DHAVE_CONFIG_H=1 -I. -I. -Iintl -I/usr/local/include -I/usr/include/ncurses/include -I./intl -Wall -pedantic -g -O2 -c dotlock.c gcc -Wall -pedantic -g -O2 -L/usr/include/ncurses/lib -o mutt addrbook.o alias.o attach.o base64.o browser.o buffy.o colour.o commands.o complete.o compose.o copy.o curs_lib.o curs_main.o date.o edit.o enter.o flags.o init.o filter.o from.o getdomain.o handler.o hash.o hdrline.o headers.o help.o hook.o keymap.o main.o mbox.o menu.o mh.o mx.o pager.o parse.o pattern.o postpone.o query.o recvattach.o recvcmd.o rfc822.o rfc1524.o rfc2047.o rfc2231.o score.o send.o sendlib.o signal.o sort.o status.o system.o thread.o charset.o history.o lib.o muttlib.o editmsg.o pgp.o pgpinvoke.o pgpkey.o pgplib.o gnupgparse.o resize.o dotlock.o -lncurses colour.o: In function `_mutt_parse_color': /usr/s/mutt-1.2.5/colour.c:710: undefined reference to `use_default_colors' resize.o: In function `mutt_resize_screen': /usr/s/mutt-1.2.5/resize.c:75: undefined reference to `resizeterm' make[2]: *** [mutt] Error 1 make[2]: Leaving directory `/usr/s/mutt-1.2.5' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/s/mutt-1.2.5' make: *** [all-recursive-am] Error 2 Its failing at one of the functions that I have a problem with viz. mutt_resize_screen. TO fix ... ? Thanx -- Eric Smith
Re: Nvi saved the file mutt-incursion-5855-11
Hey, How do I get rid of this annoying message that I get on a daily basis. I have editor="emacs -nw" in my .muttrc Thanks Rob On Fri, Jan 19, 2001 at 08:51:24AM +1100, Nvi recovery program wrote: > On Mon Nov 13 22:27:45 2000, the user mlaich was editing a > file named /tmp/mutt-incursion-5855-11 on the machine > incursion, when it was saved for recovery. You can recover > most, if not all, of the changes to this file using the -r > option to editor: > > editor -r /tmp/mutt-incursion-5855-11 > -- ---> mlaich.com Robert Martinovic [EMAIL PROTECTED] www.mlaich.com icq# 77465568
Re: addressing problem
Hey, On Fri, Jan 19, 2001 at 09:45:58PM +0100, Martin wrote: > 1: Please trim your lines to 76-78 chars per line! THX I am curious on how this is done. Rob -- ---> mlaich.com Robert Martinovic [EMAIL PROTECTED] www.mlaich.com icq# 77465568
Re: how to "toggle-signature" display in pager?
At 09:46 AM 1/19/01 +, Conor Daly wrote: >You could try >color signature black black >in .muttrc. You'll get lots of empty lines for long sigs but, at least, >no text clutter Sadly, people with long signatures often lack the clue to have a proper sig seperator (dash dash space ) so this recipe doesnt usually work :( -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
