Re: Mutt, procmail, and sendmail
On Mon, Mar 26, 2001 at 11:09:22AM -0500, Wade A. Mosely wrote: Lars Hecking wrote: 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. Thanks, Lars, for that marvelously helpful comment. I didn't find any better solution on my own, though. Using 'set sendmail="procmail ~/.procoutrc"' didn't seem to work because of the recipients being included on the command line by Mutt. Is there a better way to get the message passed to procmail from Mutt? Have you tried making a script, just like the one you posted, but without the 'cat |' part? 'cat' does nothing but read from stdin and copy to stdout; procmail should handle reading from stdin just fine :) G'luck, Peter -- No language can express every thought unambiguously, least of all this one.
Re: vim and mutt question
On Sat, Mar 24, 2001 at 02:31:29AM -0600, Timothy Legant wrote: On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote: On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote: Hi All, I have an autocommand for temporary mutt files. I want to move the cursor down 6 positions automatically when I start a new mail (this would move the cursor right under the headers (i use edit headers). But i can't seem to figure out how to do this from a vimrc file... You could try setting the mutt 'editor' variable to something like /usr/local/bin/vim +6j This shall affect editing old messages, too, but it will probably do what you want. You might not always want to move down 6 lines. Perhaps in the future you will add a new header (using my_hdr) to certain messages. You might want to consider the following instead: set editor="vim -c ':0;/^$'" which will search for and move to the first blank line. In an email message that should be the first line after all the headers, no matter how many header lines there are. Yeah, that would work better :) G'luck, Peter -- No language can express every thought unambiguously, least of all this one.
Re: vim and mutt question
On Sat, Mar 24, 2001 at 01:06:22AM -0800, Jason Helfman wrote:
I'd like to use this setting, too, but right now I have:
set editor="vim -c 'set tw=72 et'"
Can I incorporate this into it??
set editor="vim -c ':0;/^$'"
From the vim manpage:
-c {command}
{command} will be executed after the first
file has been read. {command} is interpreted
as an Ex command. If the {command} contains
spaces it must be enclosed in double quotes
(this depends on the shell that is used).
Example: Vim "+set si" main.c
Note: You can use up to 10 "+" or "-c" com-
mands.
According to the note, it would be OK to do something like:
set editor="vim -c 'set tw=72 et' -c ':0;/^$'
G'luck,
Peter
--
I had to translate this sentence into English because I could not read the original
Sanskrit.
On Sat, Mar 24, 2001 at 02:31:29AM -0600, Timothy Legant muttered:
| On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote:
| On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote:
| Hi All,
|
| I have an autocommand for temporary mutt files. I want to move the
| cursor down 6 positions automatically when I start a new mail (this
| would move the cursor right under the headers (i use edit headers). But i
can't seem to figure out how to do this from a vimrc file...
|
| You could try setting the mutt 'editor' variable to something like
|
|/usr/local/bin/vim +6j
|
| This shall affect editing old messages, too, but it will probably
| do what you want.
|
| You might not always want to move down 6 lines. Perhaps in the future
| you will add a new header (using my_hdr) to certain messages. You might
| want to consider the following instead:
|
| set editor="vim -c ':0;/^$'"
|
| which will search for and move to the first blank line. In an email
| message that should be the first line after all the headers, no matter
| how many header lines there are.
Re: vim and mutt question
And btw, mail to the [EMAIL PROTECTED] address bounces.
G'luck,
Peter
--
I am the thought you are now thinking.
On Sat, Mar 24, 2001 at 01:47:25PM +0200, Peter Pentchev wrote:
On Sat, Mar 24, 2001 at 01:06:22AM -0800, Jason Helfman wrote:
I'd like to use this setting, too, but right now I have:
set editor="vim -c 'set tw=72 et'"
Can I incorporate this into it??
set editor="vim -c ':0;/^$'"
From the vim manpage:
-c {command}
{command} will be executed after the first
file has been read. {command} is interpreted
as an Ex command. If the {command} contains
spaces it must be enclosed in double quotes
(this depends on the shell that is used).
Example: Vim "+set si" main.c
Note: You can use up to 10 "+" or "-c" com-
mands.
According to the note, it would be OK to do something like:
set editor="vim -c 'set tw=72 et' -c ':0;/^$'
G'luck,
Peter
--
I had to translate this sentence into English because I could not read the original
Sanskrit.
On Sat, Mar 24, 2001 at 02:31:29AM -0600, Timothy Legant muttered:
| On Sat, Mar 24, 2001 at 09:59:45AM +0200, Peter Pentchev wrote:
| On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote:
| Hi All,
|
| I have an autocommand for temporary mutt files. I want to move the
| cursor down 6 positions automatically when I start a new mail (this
| would move the cursor right under the headers (i use edit headers). But i
can't seem to figure out how to do this from a vimrc file...
|
| You could try setting the mutt 'editor' variable to something like
|
| /usr/local/bin/vim +6j
|
| This shall affect editing old messages, too, but it will probably
| do what you want.
|
| You might not always want to move down 6 lines. Perhaps in the future
| you will add a new header (using my_hdr) to certain messages. You might
| want to consider the following instead:
|
| set editor="vim -c ':0;/^$'"
|
| which will search for and move to the first blank line. In an email
| message that should be the first line after all the headers, no matter
| how many header lines there are.
Re: send problems
On Sat, Mar 24, 2001 at 10:52:54AM -0700, Dave Murray wrote: I have trouble with sending messages, intermittently with another list. I use sendmail and my ISP's SMTP. Mutt shows me sending, a copy ends up in record, that's the end of my knowledge. I know that this is the mutt list but perhaps someone here could help. Does sendmail keep a log file? It would help me see if it thinks that it passed it on. Sendmail logs most transactions via syslog, using the facility 'mail'. Usually those end up in /var/log/messages, unless you've redirected them somewhere else in /etc/syslog.conf. G'luck, Peter -- This sentence is false.
Re: vim and mutt question
On Sat, Mar 24, 2001 at 07:35:12AM +, Viktor Lakics wrote: Hi All, I have an autocommand for temporary mutt files. I want to move the cursor down 6 positions automatically when I start a new mail (this would move the cursor right under the headers (i use edit headers). But i can't seem to figure out how to do this from a vimrc file... You could try setting the mutt 'editor' variable to something like /usr/local/bin/vim +6j This shall affect editing old messages, too, but it will probably do what you want. G'luck, Peter -- Do you think anybody has ever had *precisely this thought* before?
Re: bounce-message command ignores sendmail -f address
On Mon, Mar 19, 2001 at 01:48:48PM +0100, furio ercolessi wrote: So my original question should probably be turned into: - how do I change Resent-From: in bounced mail, so that mail appears to be resent from the address that I configured as From: (using my_hdr) and in envelope (using sendmail -f), rather then from my Unix username? Defining Resent-From: with my_hdr seems to be a no-no ;) That's strange. I'm using 1.2.5i with: set from="Peter Pentchev [EMAIL PROTECTED]" in my .muttrc, and when I tried to send a message to myself, and then bounce it again, it seemed to work ok - the last 4 lines of the bounced message are: User-Agent: Mutt/1.2.5i Resent-From: [EMAIL PROTECTED] Resent-Date: Mon, 19 Mar 2001 15:02:32 +0200 Resent-To: [EMAIL PROTECTED] From looking at the source, mutt determines the Resent-From: address in just the same way as the From: address in normal messages. G'luck, Peter -- If you think this sentence is confusing, then change one pig.
Re: Is the subscribe command good for anything?
On Tue, Jan 30, 2001 at 11:10:40AM +0100, Asmund Skjaveland wrote: I use mutt 1.2.5, and read a few mailing list. I also use automatic filtering of my mail to put it all in the appropriate mailboxes. And I'm wondering what the subscribe command in mutt does, other than showing what mailing list the mail was sent to rather than who sent it. Since each mailing list goes in its own mailbox, I already know the mails were sent to the mailing list in question, and would much rather see who sent the mail. So, does the subscribe command have any actual use, or is it just there to annoy? Even if I tell mutt "unsubscribe [EMAIL PROTECTED]", the list-reply command still works. The 'subscribe' command helps 1. if all your mail is delivered to one inbox, where you can easily see which messages go where, and 2. (MUCH more important, at least for me) in conjunction with the followup_to variable, it helps mutt generate a Mail-Followup-To: header when you List-reply or Group-reply. G'luck, Peter -- I am not the subject of this sentence.
Re: Is the subscribe command good for anything?
On Tue, Jan 30, 2001 at 12:31:40PM +0200, Peter Pentchev wrote: On Tue, Jan 30, 2001 at 11:10:40AM +0100, Asmund Skjaveland wrote: I use mutt 1.2.5, and read a few mailing list. I also use automatic filtering of my mail to put it all in the appropriate mailboxes. And I'm wondering what the subscribe command in mutt does, other than showing what mailing list the mail was sent to rather than who sent it. Since each mailing list goes in its own mailbox, I already know the mails were sent to the mailing list in question, and would much rather see who sent the mail. So, does the subscribe command have any actual use, or is it just there to annoy? Even if I tell mutt "unsubscribe [EMAIL PROTECTED]", the list-reply command still works. The 'subscribe' command helps 1. if all your mail is delivered to one inbox, where you can easily see which messages go where, and 2. (MUCH more important, at least for me) in conjunction with the followup_to variable, it helps mutt generate a Mail-Followup-To: header when you List-reply or Group-reply. (or even when you send a message to a list mutt has marked as subscribed-to like in your case - my mail in reply to your message only went to the list, not to you personally, because your message had a Mail-Followup-To: hdr) G'luck, Peter -- This sentence contains exactly threee erors.
Re: keymap_defs.h (FreeBSD)
On Sat, Jan 06, 2001 at 08:21:59PM +, Michael Wells wrote: Hi, Thanks for the replies, problem solved. If this could be integrated into the conventional build process that'd be great. It's in there already - in the FreeBSD Ports Collection - albeit in a slightly different form. --- Makefile.in.origTue May 9 17:15:37 2000 +++ Makefile.in Fri May 12 13:53:08 2000 @@ -210,7 +210,7 @@ SOURCES = $(mutt_dotlock_SOURCES) $(pgpring_SOURCES) $(makedoc_SOURCES) $(mutt_SOURCES) $(EXTRA_mutt_SOURCES) OBJECTS = $(mutt_dotlock_OBJECTS) $(pgpring_OBJECTS) $(makedoc_OBJECTS) $(mutt_OBJECTS) -all: all-redirect +all: $(BUILT_SOURCES) all-redirect .SUFFIXES: .SUFFIXES: .S .c .o .s $(srcdir)/Makefile.in: Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) ..to quote directly from /usr/ports/mail/mutt/files/patch-Makefile.in Why, indeed, are you not building mutt from the Ports Collection? :) Or at least - after you've encountered a problem, check to see if the port has not solved it in some way. That's the main purpose of the FreeBSD Ports Collection - to facilitate building various applications with any and all FreeBSD-specific changes. G'luck, Peter -- I am the meaning of this sentence. Cheers Michael On Sat, Jan 06, 2001 at 08:49:05PM +0100, Wilhelm Wienemann ([EMAIL PROTECTED]) wrote: Hello Michael! On Sat, 06 Jan 2001, Michael Wells wrote: Compiling Mutt on FreeBSD, I found that the build process couldn't generate keymap_defs.h (not sure exactly how this file is made, sorry). After the './configure' process is finished you have to do 1. 'make keymap_defs.h' *and* 2. 'make' and then it will build the header-file you want to finish the compilation with the needed executables and config-files. :-) bye and have a nice weekend Wilhelm -- MicroSoft "ILOVEYOU". Thanks for engineering a 100% Virus Enabled Platform! (C) by Al Hopper [EMAIL PROTECTED] 2 Jan 2001 on solarisonintel -- www.wells.org.uk +44 7715 747252
Re: Mutt and *nix clients and Qmail server
On Tue, Jan 02, 2001 at 07:53:54PM +0530, Suresh Ramasubramanian wrote: Subba Rao proclaimed on mutt-users that: I have no problem setting up Windows/OS/2 clients to connect to the Qmail server to relay the messages. The problem I am facing now is *nix clients. It looks like the *nix clients (with the exception of Pine) do require a local SMTP server to relay to the main SMTP server. One of the clients, I am using is mutt. It doesn't look like Mutt can send the message directly to the relaying SMTP server. Use something like masqmail / nullmailer and such on the local unix clients. The point is, Unix mail clients do not require a local SMTP server per se; they require a sendmail-like *program* to.. well.. to send mail :) It's much easier - and less error-prone - for mail clients to know they have to execute such-and-such program and pass such-and-such parameters to it, than to make all mail clients actually network-aware SMTP clients (with all the subtleties of SMTP and any network protocol - response parsing and such..) So, just as Suresh suggested, look into some mail delivery agents that act like the sendmail *program*, not SMTP server, and take care of all the SMTP talk. G'luck, Peter -- I've heard that this sentence is a rumor.
Re: Error messages
On Wed, Dec 13, 2000 at 06:12:43PM -0800, David Alban wrote:
Greetings!
At 2000/12/13/18:58 -0600 David Champion [EMAIL PROTECTED] wrote:
You mean just to test the muttrc file and report parse errors?
How about:
mutt -F test.muttrc -f /dev/null -e "push x" /dev/null
That's *way* cool!
Here's a script[1] which uses your idea to test $1 if it's defined and
$HOME/.muttrc if it isn't:
(the script itself quoted for context)
#!/bin/bash
pgm=`basename $0`
die () {
echo 12 "$pgm: $1"
exit 1
} # die
muttrc=$HOME/.muttrc.common
[[ -n $1 ]] muttrc="$1"
[[ ! -e $muttrc ]] die "$muttrc: no such file"
[[ ! -f $muttrc ]] die "$muttrc: not regular file"
[[ ! -r $muttrc ]] die "$muttrc: cannot open"
echo | mutt -F "$muttrc" -f /dev/null -e "push nnx" /dev/null
[snip]
P.S. If you run this script and get:
[[: command not found
[[: command not found
[[: command not found
[[: command not found
you need to upgrade to bash 2.x.
Just a side note - is there a reason you could not use the standard '['
test operator? Along with some quoting of possibly-null arguments, of
course.. something like:
[ -n "$1" ] muttrc="$1"
[ ! -e "$muttrc" ] die "$muttrc: no such file"
[ ! -f "$muttrc" ] die "$muttrc: not regular file"
[ ! -r "$muttrc" ] die "$muttrc: cannot open"
Just this way, it works for me in FreeBSD's /bin/sh, which is pretty much
as standard a Bourne shell as you can get..
G'luck,
Peter
--
This inert sentence is my body, but my soul is alive, dancing in the sparks of your
brain.
Re: Error messages
On Thu, Dec 14, 2000 at 11:12:48AM -0500, Josh Huber wrote: On Thu, Dec 14, 2000 at 07:37:47AM -0800, David Alban wrote: Of course, this would be O.K. I prefer the [[ ]] operator (found in ksh and bash 2.x) because it is smarter and more resistant to syntax errors that occur with [ ] if a variable is undefined. But certainly one can use [ ] and then double quote the variables within, as you have done. AFAIK, it also doesn't fork a process as well, using [[ ]] the tests are done internally to bash/ksh, and are thus much faster. I dare you to name a relatively-modern version of csh, tcsh, bash, ksh or zsh, which does not have test/[ as a builtin ;) And to answer an unquoted question in David Alban's mail, FreeBSD does not come with bash in the base system, it does have both bash1 and bash2 in its Ports Collection, and as packages on the officially distributed FreeBSD CD's. G'luck, Peter -- What would this sentence be like if it weren't self-referential?
Re: message to Peter Pentchev
On Mon, Dec 04, 2000 at 08:34:41PM +0100, William Maddler wrote: looks like in ur test u left [EMAIL PROTECTED] as ur mail address... ;))) I have a couple mails here for u... lemme know ur addie... ;)) Heh actually it's in the previous message's headers - [EMAIL PROTECTED] :) And I actually received the messages - they were CC:d to a mailing list or two. Sorry about that! :) G'luck, Peter -- This sentence no verb.
Re: Exec Error 127
On Sun, Dec 03, 2000 at 12:37:47PM -0800, Jason Helfman wrote: Look at your "set editor" variable in .muttrc file. Once I had it set to vi, when I didn't have that installed, but I had vim installed, and received the same error. On Sun, Dec 03, 2000 at 02:41:59PM +0100, Gian Piero Ascenso muttered: | Hi, | | I get the above error message when I try to send a message | with mutt 1.2.5i from a RH 7.0 Linux box on intel x686. I'm able to | fetch mail from my ISP, though, What's wrong? What should I check? | | PS - I'm writing this message from Netscape. | | Regards, | | Gian Piero This is not necessarily an editor problem. This error means that mutt encounters a problem when trying to execute an external program, most probably when trying to execute a program which does not exist or is not located where mutt's looking for it. My bet in this case would be that sendmail is not where mutt thinks it is. But just to be certain - does this error pop up after you've composed the message and are trying to send it, or does it show before you've had a chance to write your message? If it is the latter, then it might very well be what Jason said - mutt being unable to start up your editor. In that case, either set the EDITOR environment variable in your shell startup scripts to point to a valid editor, or set the 'editor' variable in your muttrc. If it is the former, then it's most probably a sendmail problem - check if you have /usr/sbin/sendmail on your system (or maybe /usr/lib/sendmail, or /usr/libexec/sendmail..). If you do not, then you will need to install it, or install some other kind of mail transport agent. Mutt, unlike Netscape, is purely a mail user agent - showing you the mail some other program has already delivered, and invoking some other program to send out mail you've written. Thus, it needs sendmail or some sendmail workalike to send outgoing messages. I like qmail better than sendmail, but that's a matter of personal preference :) Hope that was not too confuzzling :) G'luck, Peter -- This sentence no verb.
[Fwd: Re: set my_hdr via macro]
Whoops I forgot to CC: the list on that one.. G'luck, Peter -- This sentence no verb. - Forwarded message from Peter Pentchev [EMAIL PROTECTED] - Date: Mon, 4 Dec 2000 16:54:46 +0200 From: Peter Pentchev [EMAIL PROTECTED] To: William Maddler [EMAIL PROTECTED] Subject: Re: "set my_hdr" via macro User-Agent: Mutt/1.2.5i In-Reply-To: [EMAIL PROTECTED]; from [EMAIL PROTECTED] on Mon, Dec 04, 2000 at 03:40:18PM +0100 Several points on this. 1. If you need to set your from name and/or address, better let mutt know what you're trying to do - set the 'from' variable, do not add a new header. 2. Keyboard macros expand to just that - key sequences. Thus, if you want to enter a command, you need to prefix it with ':', just as you would've done if you'd tried to enter it on the mutt 'command line'. So.. macro index 'f9' ':set from="[EMAIL PROTECTED]"enter' 'Send as wm' And you could even try: macro index 'f9' ':set from="William Maddler [EMAIL PROTECTED]"enter' 'Send as wm' Hope that helps :) G'luck, Peter -- This sentence contradicts itself - or rather - well, no, actually it doesn't! On Mon, Dec 04, 2000 at 03:40:18PM +0100, William Maddler wrote: Hi all from a newcomer! :)) As a welcome I have a nice Q... :))) I need to send mails using different address/signature couples... I can use send_hooks for replying but can I use macros to issue a "set my_hdr" command? I have: macro index f9 "set my_hdr From: [EMAIL PROTECTED]" "Send as wm" in .muttrc now but whe I press F9 Mutt says "no mailbox open". Any clue? Thx... Oh... I really need this to leave Pine and move to Mutt! ;))) thx... - End forwarded message -
Re: sendmail error
On Thu, Nov 30, 2000 at 11:11:02AM -0600, Kelly Scroggins wrote: [snip] /etc/sendmail.cf: line 90: fileclass: cannot open /etc/sendmail.cw: Group writable directory [snip] # /etc/rc.d/init.d/sendmail start Starting sendmail: WARNING: Group writable directory /etc Can you show us the output of "ls -ld /etc" ? G'luck, Peter -- What would this sentence be like if pi were 3?
Re: pager scrolling question
On Tue, Nov 28, 2000 at 10:02:27PM -0800, Gary Johnson wrote: On Tue, Nov 28, 2000 at 11:45:35PM -0600, Jason wrote: I'd like the pager to scroll one line at a time instead of a page at a time. Anyone got the trick? I don't use the internal pager myself, but according to the mutt manual, 6.4.3. pager ... next-lineRET scroll down one line ... previous-line BackSpace scroll up one line Actually, these bindings - Space for next screenful, Return for next line - are common for most Unix pagers. I think 'more' has been that way for a long time (possibly from the start), 'less' has certainly been that way since its very first version. G'luck, Peter -- This inert sentence is my body, but my soul is alive, dancing in the sparks of your brain.
Re: User ID different from email address
On Mon, Nov 27, 2000 at 10:31:31AM -0500, Charles Krug wrote: List: [snip] "From: Charles Krug [EMAIL PROTECTED]" However, mutt does this: "From: Charles Krug [EMAIL PROTECTED]" Have you tried editing your muttrc file and setting the 'from' and 'envelope-from' mutt variables to [EMAIL PROTECTED]? G'luck, Peter -- .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI
Re: command line
On Thu, Nov 23, 2000 at 03:29:14PM +0800, Steve Marcionni wrote: I need to be able to send a mail message from the command line which allows me to attach a file. Can this be done without having the mail screen appear and making me select y to send the message ??? Yes, compose your message in a separate file, then use: mutt -a attachment.file user@domain message.file If you want to *only* send an attachment with an empty message body.. mutt -a attachment.file user@domain /dev/null I've just tested both of these with mutt-1.2.5i and they seem to work. Hope that helps. G'luck, Peter -- If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false.
Re: limiting to message size
On Tue, Nov 07, 2000 at 02:46:40PM -0600, David Champion wrote: [snip original discussion of word/character counting] However, I can imagine a pattern expression that pipes each message through a command, and matches based on that command's exit status: if 0, match; else, no match. This could work like: ~Z 'set -- `wc %s`; [ $2 -gt 1000 ] true || false' Just as a side note - the ' true || false' part is redundant - the shell evaluates and || based purely on the last command's exit status; so the ' true || false' expression is only useful for turning a "zero / non-zero" exit code into a "zero / one". In this particular case, the last command is '[' a.k.a. 'test' - which in all its incarnations I've seen so far returns zero or one. G'luck, Peter -- What would this sentence be like if pi were 3?
Re: View .doc .xls
On Tue, Nov 07, 2000 at 01:49:18AM +0300, Vitaly A. Repin wrote: On Tue, Nov 07, 2000 at 12:13:23AM +0100, Martin Schweizer wrote: How can I see the above files with mutt(1.0.1i) on a FreeBSD-Box (4.0) without StarOffice? Thanks in advance. At the first, you should get the program for viewing such files. I can't say anything about xls files, but there is a program named "catdoc" for viewing doc files, produced by MS WORD. I don't keep in mind the URL of catdoc, but it seems to me, you can find it easily in the internet. This program was written by Vitus Wagner. catdoc is in the FreeBSD ports collection - /usr/ports/textutils/catdoc/ The current version includes xls2csv and xlsview for viewing Excel spreadsheets - not perfect, but way better than nothing :) G'luck, Peter -- Thit sentence is not self-referential because "thit" is not a word.
save-hook for not just the sender?
Alright, sorry if this is an FAQ; but I did not seem to find anything about this in either the manual or the mailing list archives. I'm using mutt-1.2.5i. save-hook works perfectly alright, when filtering by the sender's address; however, I want to filter by something more than that - either the mail's subject (for mailing lists which add a token to the message subject), or by some string found in the message header (for e.g. Majordomo-run lists which may be identified by owner-listname in the header). Is there a way to do something similar to save-hook, but use an expression similar to the one used in tagging? Something like "~h owner-freebsd-bugs" or "~s BUGTRAQ"? And yes, I know I can do this with procmail and mutt's multiple inboxes support; is there an easier way though? :) Thanks in advance for any pointers to the source, the manual, the mailing list archives, or anything else which goes to show the futility of me attempting mutt configuration before lunch :) G'luck, Peter -- This sentence contradicts itself - or rather - well, no, actually it doesn't!
