Re: is there a way to create a "group"
Jeff -- ...and then Jeff Morris said... % Hello, I just started using mutt today and I was wondering if anyone knows a way to create a group for broadcast messages...I can't find anything in the man pages or the documentation. Yes, you can; aliases can be either single or multiple. Check out section 3.2 of the manual. % Thanks HTH & HAND :-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! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
is there a way to create a "group"
Hello, I just started using mutt today and I was wondering if anyone knows a way to create a group for broadcast messages...I can't find anything in the man pages or the documentation. Thanks
Appoligies for posting mistake.
I appologise for the error in my just posted question on GNOME. Sorry. :(
[jverel@home.com: Re: Gnome Sound -- Startup wav not working]
This is a repost. I sent it last night and it appears it got lost along the way. My appologies if you get more than one copy. John __ And yet more! (This is endlessly entertaining ;) The startup wav will launch upon reboot, if I log in as root. But, never again in that boot session. I've tried killing esd, clearing out lock files, temp files, etc. Still baffled On Mon, Mar 06, 2000 at 11:31:32PM -0500, John P. Verel wrote: > Here's some more on this problem. > > - The startup wav fails only in Gnome, but not in KDE. > - The wav file works fine in the Gnome control center setup and test. > - All other sound work fine in Gnome. > - I get the following message in my .xsession-errors log: > > SESSION_MANAGER=local/CV150607-A:/tmp/.ICE-unix/1351,tcp/CV150607-A:1103 > esd: Esound sound daemon already running or stale UNIX socket > /tmp/.esd/socket > This socket already exists indicating esd is already running. > Exiting... > xscreensaver-command: no screensaver is running on display :0.0 > xscreensaver disabling server builtin screensaver. > xscreensaver: you can re-enable it with "xset s on". > subshell.c: couldn't get terminal settings: Inappropriate ioctl for > device > > GnomeUI-WARNING **: Could not open help topics file NULL > > Gtk-CRITICAL **: file gtkcontainer.c: line 730 (gtk_container_remove): > assertion `widget->parent == GTK_WIDGET (container)' failed. > > Gtk-WARNING **: invalid cast from `(unknown)' to `GtkWidget' > > Gtk-CRITICAL **: file gtkwidget.c: line 3500 (gtk_widget_get_style): > assertion `GTK_IS_WIDGET (widget)' failed. > > Gtk-CRITICAL **: file gtkctree.c: line 5130 > (gtk_ctree_node_set_foreground): assertion `GTK_IS_CTREE (ctree)' > failed. > > > Is the reference to the Esound daemon provide a clue? > > Thanks. > > John > > On Sun, Mar 05, 2000 at 11:53:00PM -0500, John P. Verel wrote: > > For no reason I can discern, Gnome has stopped playing any startup wav > > file I may select. Worked fine yesterday...not working today. I'm > > baffled! Any thoughts? > > > > Jo > > > > > > -- > > To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" > > as the Subject.
Re: Introduction to Maildir (was Re: mutt and mh/procmail)
OK, somebody has to say this:
Philip's latest revision of the procmailrc code in question is as follows:
| :0
| * conditions
| {
| :0 r
| foldername/tmp/$XXX
|
| :0 air
| |mv foldername/tmp/$XXX foldername/new/$XXX
| }
Shouldn't the first recipe inside the braces have a `c' flag? And shouldn't
there be some provision for fall-through?
In fact, if we are going to do nothing about fall-through, do we need braces
at all?
:0rc
* conditions
foldername/tmp/$XXX
:0air
|mv foldername/tmp/$XXX foldername/new/$XXX
# ^^^
# would $LASTFOLDER work there?
Re: Reply to full name from alias list
Hi,
On Wed, Mar 08 2000 06:18:58 -0500 wrote David T-G
with subject "Re: Reply to full name from alias list":
> % I was close to ask the same question. Mutt doesn't have this feature
>
> I asked exactly this question, in fact, on 2000Feb08 but got absolutely
> no response. You guys must have been on vacation or something ;-)
I joined the list a little bit later but searched the archive for
similar questions (maybe not good enough) and found nothing.
> % so far. My solution was to modify `send.c' in that way that it takes
> % the alias address and real name rather than the presented `from' line
> % when I reply to someone. This is just a quick solution and there is no
>
> That's *exactly* what I'd like ...
Here comes my patch which should now work also for list replies and
group replies, but is not perfect when a `to' or `cc' line with more
than one recipient is presented (i.e works only on the first address).
I leave it to the developers to do something more with it :-). I also
did this reverse of aliases on the `Mail-Followup-To' header, not sure
if it works or if I break some rfc's with that.
Use at your own risk! (Do I have to say that? :)
> % way to turn it off (yet). And I'm not sure if it works in list-replys,
>
> ... and I can't see any reason to turn it off (for me, anyway).
just in case...
Enjoy, Stefan.
--
One Page Principle:
A specification that will not fit on one page of 8.5x11 inch
paper cannot be understood.
-- Mark Ardis
--- send.c.orig Wed Mar 8 16:14:17 2000
+++ send.c Wed Mar 8 18:04:52 2000
@@ -422,16 +422,22 @@ static int default_to (ADDRESS **to, ENV
{
char prompt[STRING];
int i = 0;
+ ADDRESS *adr_from, *adr_reply_to, *adr_to, *adr_cc, *adr_fup;
+ if(!(adr_from=alias_reverse_lookup(env->from))) adr_from = env->from;
+ if(!(adr_reply_to=alias_reverse_lookup(env->reply_to))) adr_reply_to =
+env->reply_to;
+ if(!(adr_to=alias_reverse_lookup(env->to))) adr_to = env->to;
+ if(!(adr_cc=alias_reverse_lookup(env->cc))) adr_cc = env->cc;
+ if(!(adr_fup=alias_reverse_lookup(env->mail_followup_to))) adr_fup =
+env->mail_followup_to;
+
if (flags && env->mail_followup_to)
{
snprintf (prompt, sizeof (prompt), _("Follow-up to %s%s?"),
- env->mail_followup_to->mailbox,
- env->mail_followup_to->next ? "..." : "");
+ adr_fup->mailbox, adr_fup->next ? "..." : "");
if (query_quadoption (OPT_MFUPTO, prompt) == M_YES)
{
- rfc822_append (to, env->mail_followup_to);
+ rfc822_append (to, adr_fup);
return 0;
}
}
@@ -445,7 +451,7 @@ static int default_to (ADDRESS **to, ENV
if (!option(OPTREPLYSELF) && mutt_addr_is_user (env->from))
{
/* mail is from the user, assume replying to recipients */
-rfc822_append (to, env->to);
+rfc822_append (to, adr_to);
}
else if (env->reply_to)
{
@@ -463,7 +469,7 @@ static int default_to (ADDRESS **to, ENV
* in his From header.
*
*/
- rfc822_append (to, env->from);
+ rfc822_append (to, adr_from);
}
else if (!(mutt_addrcmp (env->from, env->reply_to) &&
!env->reply_to->next) &&
@@ -475,20 +481,19 @@ static int default_to (ADDRESS **to, ENV
* provides a way to do that.
*/
snprintf (prompt, sizeof (prompt), _("Reply to %s%s?"),
- env->reply_to->mailbox,
- env->reply_to->next?",...":"");
+adr_reply_to->mailbox, adr_reply_to->next?",...":"");
if ((i = query_quadoption (OPT_REPLYTO, prompt)) == M_YES)
- rfc822_append (to, env->reply_to);
+ rfc822_append (to, adr_reply_to);
else if (i == M_NO)
- rfc822_append (to, env->from);
+ rfc822_append (to, adr_from);
else
return (-1); /* abort */
}
else
- rfc822_append (to, env->reply_to);
+ rfc822_append (to, adr_reply_to);
}
else
-rfc822_append (to, env->from);
+ rfc822_append (to, adr_from);
return (0);
}
@@ -496,9 +501,13 @@ static int default_to (ADDRESS **to, ENV
int mutt_fetch_recips (ENVELOPE *out, ENVELOPE *in, int flags)
{
ADDRESS *tmp;
+ ADDRESS *adr_to, *adr_cc;
+ if(!(adr_to=alias_reverse_lookup(in->to))) adr_to = in->to;
+ if(!(adr_cc=alias_reverse_lookup(in->cc))) adr_cc = in->cc;
+
if (flags & SENDLISTREPLY)
{
-tmp = find_mailing_lists (in->to, in->cc);
+tmp = find_mailing_lists (adr_to, adr_cc);
rfc822_append (&out->to, tmp);
rfc822_free_address (&tmp);
@@ -514,8 +523,8 @@ int mutt_fetch_recips (ENVELOPE *out, EN
if ((flags & SENDGROUPREPLY) && !in->mail_followup_to)
{
/* if(!mutt_addr_is_user(in->to)) */
- rfc822_append (&out->cc, in->to);
- rfc822_append (&out->cc, in->cc);
+ rfc822_append (&out->cc, adr_to);
+ rfc822_append (&out->cc, adr_cc);
}
}
return 0;
Re: unable to get mutt_dotlock to work
On Wed, Mar 08, 2000 at 09:26:42PM +1100, CaT wrote: > Nope. chgrp mail /var/spool/mail > Whopps... how could I be so stupid not to notice that? ;-) Thanks -- Jeremy Lunn Melbourne, Australia ICQ: 19255837
Re: Introduction to Maildir (was Re: mutt and mh/procmail)
I wrote:
>Bennett Todd <[EMAIL PROTECTED]> writes:
>>Note to the procmail-list folks, the mutt list grew this thread that
>>spawned the question, how to deliver to Maildirs safely from an old,
>>musty, non-maildir-supporting procmail. Various suggestions were
>>bashed back and forth, and after I read the thread it looked to me
>>like we were closing in on something actually [potentially] useful.
>>Supposing a user's ISP won't upgrade their procmail, or allow them
>>to install a nice tight efficient compact maildir.c executable, how
>>about something like:
...
>>
>> # Needed only once, in the preamble of the procmailrc
>> XXX=`date +%S`.$$.$HOST
>
>That isn't particularly unique: %S is just the seconds of the minute.
>Perhaps you meant %s, GNU's extension that gives the time_t value
>(number of seconds since midnight 1970-1-1). That would be almost
>certainly unique: pids are *very* unlikely to be resused within a second.
...
>However, since you're trusting for $XXX to be unique, you might as well
>go all the way and save two processes (a shell and the cat) by saving
>the message directly:
>
> :0
> * conditions
> {
> :0
> foldername/tmp/$XXX
>
> :0 ai
> |mv foldername/tmp/$XXX foldername/new/$XXX
> }
I just realized that the first of the nested recipes should have the 'r'
flag, as maildir format doesn't need embedded "From " lines to be escaped.
Also, placing the 'r' flag on the second of the nested recipes will
marginally speed things by saving procmail a tiny bit of work.
:0
* conditions
{
:0 r
foldername/tmp/$XXX
:0 air
|mv foldername/tmp/$XXX foldername/new/$XXX
}
Philip Guenther
Re: Auto headers
Terje Elde <[EMAIL PROTECTED]> wrote on Wed, 08 Mar 2000: > Is there a magic trick that will allow mutt to automatically dump in the Cc: > and From: headers when I reply to mails on this list? I'm not entirely sure that this would work, but how about just using g(roup-reply) when answering these messages? The results as I see them are: 1) The original sender and the recipient address (hostmaster/postmaster) get both added to the recipient list. 2) Because the hostmaster/postmaster is marked as a recipient, your existing send-hook for changing the From: header for all @some-other.com emails should come into play, and change your From: header. 3) The other members of the administrative list will get the message via the hostmaster/postmaster alias. Maybe this would this work? If you want to make sure you automatically use group-reply instead of just reply for these emails, filter these emails to their own folder and bind r to group-reply for that folder. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / That government is best which governs least. -- Henry David Thoreau
Auto headers
Hi all, I'm using send-hooks to make sure my From: header is set correctly when writing to mailing lists and so on, and I match it with the email I'm sending to. What I'm looking for is a way to do the same thing, but somehow doing a match on the Sender: header when replying to a person, where the mail I'm replying to is sent to a list. To explain my situation a bit more: I've got two emails, [EMAIL PROTECTED], and [EMAIL PROTECTED] The first is my private, and default email, and the second is the one I use from work. When replying to a mail from a customer, it automatically sets my From: header because [EMAIL PROTECTED] is listed in alternates, and I've got the option set (don't remember the name) that allows mutt to reply from the right email if it's listed in alternates. The [EMAIL PROTECTED] email also gets used when I reply to anybody else @some-other.com. The problem is that we've got a mailing list, to which [host|post][EMAIL PROTECTED] and all the other admin related things get forwarded, and I often need to reply to a customer when a mail gets sent to this list. Whet I now need to do is to manually edit the From: header, to set it to [EMAIL PROTECTED], as well as add the appropriate CC to the mail gets to the others on the list as well. Is there a magic trick that will allow mutt to automatically dump in the Cc: and From: headers when I reply to mails on this list? Thanks, Terje Elde -- Xlehveh rhkau fudwuh få mydtemi dåh tk aqd rhkau jyt få kdyn (jyt == fudwuh?)
Re: Reply to full name from alias list
Stefan, et al -- ...and then Stefan Bender said... % Hi, % % On Wed, Mar 08 2000 14:02:23 +0530 wrote Mrinal Kalakrishnan % with subject "Reply to full name from alias list": % % > the whole name and address from my alias file - i.e. `The Mutt Users % > List <[EMAIL PROTECTED]>', instead of what the original sender put % > in his `To:' line. % % I was close to ask the same question. Mutt doesn't have this feature I asked exactly this question, in fact, on 2000Feb08 but got absolutely no response. You guys must have been on vacation or something ;-) % so far. My solution was to modify `send.c' in that way that it takes % the alias address and real name rather than the presented `from' line % when I reply to someone. This is just a quick solution and there is no That's *exactly* what I'd like ... % way to turn it off (yet). And I'm not sure if it works in list-replys, ... and I can't see any reason to turn it off (for me, anyway). % as I thought _this_ would not be necessary. % I started thinking I would be the only one who needs it. But it may be % a suggestion for the next release(?) to make it to an option like % `reverse_alias_reply' (or something less intuitive :). Sounds good to me! % % Regards, Stefan. % % PS: I have a `send.c.diff' which worked on 1.1.4, 1.1.5 and 1.1.8 but % I'm not sure if i did the very correct thing. Should I post it anyway % here or should I go to the mutt-dev list with that? Patches often get posted here, though it's my understanding that patches for release consideration should go to mutt-dev. I think that there's also a patching guideline somewhere to keep the code looking the same, but maybe not -- it certainly doesn't apply to me :-) % % -- % Help me, I'm a prisoner in a Fortune cookie file! *grin* :-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! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: attachments appear as NoName
> This q. was discused here few month ago and ppl from mutt-dev say thats problem > of dtmail. > > Best on the end, dtmail from Solaris 8 distribution have this "bug" too. And that with me recommending Solaris dtmail to all DecUnix users here because Dec's dtmail sucks even worse ...
Re: unable to get mutt_dotlock to work
On Wed, Mar 08, 2000 at 05:26:53PM +1100, Jeremy Lunn wrote: > Hi, > > don't have to have /var/spool/mail world writable. But it doesn't seem > to be working, I get get that error where it says mailbox is read-only. > > Here are the permissions I have: > $ ls -l /var/spool/ > drwxrwxr-t3 root root 1024 Mar 8 16:56 mail > > $ ls -l /usr/bin/mutt_dotlock > -rwxr-sr-x1 root mail 7108 Feb 18 07:54 > /usr/bin/mutt_dotlock > > Are these right? Nope. chgrp mail /var/spool/mail -- CaT ([EMAIL PROTECTED]) URL: http://www.zip.com.au/dev/null 'He had position, but I was determined to score.' -- Worf, DS9, Season 5: 'Let He Who Is Without Sin...'
Re: Automatically have a default body?
On Tue, 07 Mar 2000, Mikko Hänninen wrote: > So, any solutions to this -- how could I have a default body text when > sending email to this particular address? I suppose I could change the > contents of $signature but that's kind of ugly, as I'd need to play with > $sigdashes too (or whatever the variable was). > > > > Any suggestions? > I have a similar situation with the website I work on. There are two message types I regularly send, which I've made into text files with gaps for the new information. I start a new message and Vim comes up, at which point I use :r to read in a file. The nifty history feature of Vim means I just have to select the right include file with the cursor keys and press return. I'm sure you could do something similar in other editors. These messages all go to different addresses though so perhaps it isn't so useful for you. Adam Huffman
Re: Reply to full name from alias list
Hi, On Wed, Mar 08 2000 14:02:23 +0530 wrote Mrinal Kalakrishnan with subject "Reply to full name from alias list": > I was wondering if there is a feature by which, when I reply to, say > this mailing list ([EMAIL PROTECTED]), the `To:' line should become > the whole name and address from my alias file - i.e. `The Mutt Users > List <[EMAIL PROTECTED]>', instead of what the original sender put > in his `To:' line. I was close to ask the same question. Mutt doesn't have this feature so far. My solution was to modify `send.c' in that way that it takes the alias address and real name rather than the presented `from' line when I reply to someone. This is just a quick solution and there is no way to turn it off (yet). And I'm not sure if it works in list-replys, as I thought _this_ would not be necessary. I started thinking I would be the only one who needs it. But it may be a suggestion for the next release(?) to make it to an option like `reverse_alias_reply' (or something less intuitive :). Regards, Stefan. PS: I have a `send.c.diff' which worked on 1.1.4, 1.1.5 and 1.1.8 but I'm not sure if i did the very correct thing. Should I post it anyway here or should I go to the mutt-dev list with that? -- Help me, I'm a prisoner in a Fortune cookie file!
unable to get mutt_dotlock to work
Hi, don't have to have /var/spool/mail world writable. But it doesn't seem to be working, I get get that error where it says mailbox is read-only. Here are the permissions I have: $ ls -l /var/spool/ drwxrwxr-t3 root root 1024 Mar 8 16:56 mail $ ls -l /usr/bin/mutt_dotlock -rwxr-sr-x1 root mail 7108 Feb 18 07:54 /usr/bin/mutt_dotlock Are these right? Thanks Jeremy P.S. I am not on this list so please Cc: all corronspondence to me -- Jeremy Lunn Melbourne, Australia ICQ: 19255837
Re: Reply to full name from alias list
Mrinal Kalakrishnan <[EMAIL PROTECTED]> wrote on Wed, 08 Mar 2000: > I was wondering if there is a feature by which, when I reply to, say > this mailing list ([EMAIL PROTECTED]), the `To:' line should become > the whole name and address from my alias file - i.e. `The Mutt Users > List <[EMAIL PROTECTED]>', instead of what the original sender put > in his `To:' line. There isn't such a feature, and I miss that too... Maybe I'll try to hack together a patch for that some day. :-) Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / My mail reader can beat up your mail reader.
Reply to full name from alias list
Hi, I was wondering if there is a feature by which, when I reply to, say this mailing list ([EMAIL PROTECTED]), the `To:' line should become the whole name and address from my alias file - i.e. `The Mutt Users List <[EMAIL PROTECTED]>', instead of what the original sender put in his `To:' line. Hope this was clear enough. I didn't find any option for this in the docs (1.1.8i). -- Mrinal Kalakrishnan <[EMAIL PROTECTED]> (PGP:B1E86F5B) http://listen.to/mrinal - - - - = ( Redhat Linux 6.1 ) = - - - - = ( Kernel 2.2.12-20 ) = - - - - DUNGEON MASTERS do it in ways contrary to the laws of physics
Re: attachments appear as NoName
Lars Hecking ([EMAIL PROTECTED]) wrote : > > > At the company where I work, it seems that most people are using > > dtmail or netscape mail. > > > > When I send mail with attachments from mutt, the attachments appear > > in those other mail clients as "NoName". > > If these attachments do not have a Content-Disposition filename= > field, this would appear correct. > > > I can't figure this out. The attachments appear just fine in the > > Bcc: copy of the mail that I receive. > > > > What can I do to fix this? > > I can confirm this behaviour with dtmail under Solaris 7. > > For instance, a recent message sent to mutt-dev with the structure > > I 1 [multipa/mixed, 7bit, 1.6K] > I 2 |-> [text/plain, quoted, us-ascii, 0.6K] > A 3 `->TODO.diff [text/plain, quoted, us-ascii, 0.7K] > I 4 [applica/pgp-signat, 7bit, 0.2K] > > appears in dtmail with an empty message field and three NoName > attachments. So, I'd say that dtmail has certain problems with > multipart/mixed. Attachment 3 _is_ named > > Content-Disposition: attachment; filename="TODO.diff" > > and dtmail doesn't recognise this. This q. was discused here few month ago and ppl from mutt-dev say thats problem of dtmail. Best on the end, dtmail from Solaris 8 distribution have this "bug" too. -- Keso don't worry about glory
