Virtualhost and jailing to ~...
I am having problems jailing users to their home dir. On one box this locks them in (Suse 7.0): DefaultRoot ~ But on a SuSe 6.4 box with updated proftd it doesn't work. Can someone suggest the best way to jail the user to their home dir? I know it has been a topic on and off, but I could not find anymore info (is there an archive?). Tia. -- [EMAIL PROTECTED]| Famous last words: -o) | Linux, the Choice /\ | of a GNU generation _\_v | |
Re: Virtualhost and jailing to ~...
Robert Sweet proclaimed on mutt-users that: [...] > But on a SuSe 6.4 box with updated proftd it doesn't work. [...] The proftpd list is down the hall, third door to the right :) -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI [Wisdom] is a tree of life to those laying hold of her, making happy each one holding her fast. -- Proverbs 3:18, NSV
Re: problem using quoted printable encoding with gpg
On 2000-12-01 07:55:05 -0500, Sam Varshavchik wrote: > Sendmail has been rewriting 8bit to quoted-printable content for > decades, when relaying 8bit mail to 7bit-only relays. This > involves rewriting both the headers and the actual content of the > MIME section. Of course MTAs are free to rewrite both headers > and contents. Sendmail was doing this right from the beginning. First of all, sendmail has of course not done that "from the beginning", since it's considerably older than MIME. That MIME rewriting stuff is a rather new invention, and can arguably be considered a bad design. > Interesting. RFC 1847 would seem to require the sending mail > client to telepathically determine, in advance, whether all mail > relays that will pass along this message, at some point in the > future, will be capable of handling the message's chosen > encoding. RFC 1847 mandates very strict restrcitions on the encodings to be used when sending multipart/signed (i.e., 7bit only), so this is not an issue. (But you could have easily found out about this yourself, just by reading that standard.) > And, if the mail relay cannot accomodate the message's transfer > encoding, there's no choice but to bounce the mail, because you > can't rewrite it even thuogh you technically can? Gee, what a > "secure" concept. Please, try reading and understanding the specifications before. >> Please also note that this does not only affect PGP/MIME, but >> S/MIME and MOSS as well. > I must've imagined all the PGP-signed messages I've been sending > all these years, with nary a problem. Let me guess - you have never ever used S/MIME's multipart/signed, and you are using old-style PGP messages, right? > Bottom line: RFC 1847 is broken. It breaks several decades' > worth of established mail protocols and conventions. This is nonsense. Please try getting a clue about e-mail standards before you start coding. -- Thomas Roessler <[EMAIL PROTECTED]>
grep PGP output?
hi, Am I the only feel the PGP output too long? >>> [-- PGP output follows (current time: Fri Dec 1 18:58:06 2000) --] signature not checked. Signature made 2000/11/28 20:13 GMT key does not meet validity threshold. 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: "(KeyID: 55F2B9B0)". 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. [-- End of PGP output --] >>> Is there a way just grep m/signautre not checked|Good signature/ ? thanks, jack
Re: Silly Macro Question
Hi Timothy Grant ! On Fri 01 Dec 2000 (17:03), you muttered on the list: > Hi all, > > This is probably a silly question, but I thought I would ask just in case. > > Is there a way to create a macro that will run a shell command and then > return to mutt without me having to press a key to continue? > Yep, there is unset wait_key in your macro before you process the shell-command and then set it back to its original value. Grtz, Nils. PGP signature
Re: grep PGP output? -- my solution
patch pgp.c as follows:
--
comment line 582, 585 and 586. write a short function will be called
before line 582:
void cleanOUT (FILE *pgpout, STATE *s)
{
char buf[1024];
size_t l, i;
int find = 0;
if ( (l = fread (buf, 1, sizeof(buf), pgpout)) > 0) {
if (l==1024) l--;
buf[l] = '\0';
for (i=0; i
Re: View .doc & .xls
On Tue, Nov 07, 2000 at 02:07:42PM -0100, Dirk Ruediger wrote:
> Hi all!
>
> On Tue, 07 Nov 2000, Jan Houtsma wrote:
>
> > On Tue, Nov 07, 2000 at 12:13:23AM +0100, Martin Schweizer wrote:
> > > Hello
> > >
> > > How can I see the above files with mutt(1.0.1i) on a FreeBSD-Box (4.0) without
> > > StarOffice?
> >
> > If you don't mind using X-programs, but like me only dont want to start
> > this beast StartOffice you can try AbiWord for .doc files and
> > (under gnome) gnumeric for xls files. Works great for me.
> For me too (despite of missing table support in Abiword).
>
> > For text only i use wvHtml for .doc files. I don't have anything for xls
> > that can display on text only terminals.
>
> XLS:
> http://www.xlhtml.org/
>
> Office filters:
> http://arturo.directmail.org/filtersweb/
>
> Word processors:
> http://www.w3.org/Tools/Word_proc_filters.html
>
> Converters in general:
> http://directory.google.com/Top/Computers/Software/Internet/Authoring/Converters/
>
> Ciao for now, Dirk
This script can be used for viewing a bunch of well known file types.
The script looks for an X environment and launches either a graphical
program or an ascii oriented program.
It looks at the extension and its magic number (in that order) to
determine the file type. Its by far complete but can be extended as
needed.
I am using this script almost everywhere for viewing files so also in mutt.
The script uses /bin/zsh, but /bin/bash should work as well.
Usage: pitview [-dtH] [ filename filename ... ]
or: pitview [-dtH]
-d = dump (implies -t)
-t = text mode
-H = you'r looking at it :-)
for example 'pitview memo.doc'
'pitview students.xls'
'pitview www.mutt.org'
'pitview RobbieWilliams_KylieMinogue-Kids.mp3'
...
e.g. .urlview: COMMAND pitview %s
e.g. mailcap: text/html; pitview %s; test=RunningX
text/html; pitview %s; nametemplate=%s.html
application/msword; pitview %s; test=RunningX
application/msword; pitview -d %s; copiousoutput
application/msexcel; pitview -d %s; copiousoutput
...
Just wanted to share with the group as someone might find it useful (or not).
jan
--
pgp: http:://www.houtsma.net/~jan/openpgp.asc
___ ___ ___
/ // // / Jan H. Houtsma
/ // // / Comeniushof 92
/ // // /1216 HH Hilversum
___ / _ _ / Netherlands
/ / / // // /
/ /__/ // // / http://www.houtsma.net
///__//__/[EMAIL PROTECTED]
#!/bin/zsh
#
SCRIPTNAME=${0##*/}
typeset Help="# View files of different types inside or outside X
#
# Usage: $SCRIPTNAME [-dtH] [ filename filename ... ]
#or: $SCRIPTNAME [-dtH]
#
# -d = dump (implies -t)
# -t = text mode
# -H = you'r looking at it :-)
#
# Author: Jan Houtsma
#
# This script can be used for viewing a bunch of well known file types.
# The script looks for an X environment and launches either a graphical
# program or an ascii oriented program.
# It looks at the extension and its magic number (in that order) to
# determine the file type."
#
# Note that this works under the Linux/Gnome/Enlightenment environment.
# Some programs mentioned below might need to be additionally installed.
#
# Needed programs to view various types files:
# RunningXto determine if X windows can be opened
# w3m htmlAscii
# netscapehtmlX11
# AbiWord M$ word X11
# wvHtml M$ word Ascii
# gnumericM$ xls X11
# xlHtml M$ xls Ascii
# gv postscript X11
# acroreadpdf X11
# ee gif, jpeg, tiff X11
# rpm rpm Ascii
# esdplay wav, au Ascii
# xmmsmp3 X11
# mpg123 mp3 Ascii
#
TMP=$HOME/tmp
h=$TMP/$SCRIPTNAME.$$.html
e=$TMP/$SCRIPTNAME.error
function mylynx
{
if ((dump))
then
#lynx -dump $1
w3m -dump -T text/html $1
else
w3m -T text/html $1
fi
}
function view_html
{
if [ -f $1 ]
then
# construct a valid local url (file://...)
d=`dirname $1`
f=${1##*/}
cd $d
p=`pwd`
cd - >/dev/null
f="file://$p/$f"
else
# if not a local filename it must be an url...
f=$1
fi
if ((!text)) && RunningX 2>/dev/null
then
if [ -L $HOME/.netscape/lock ]
then
netscape -remote "openURL($f)"
else
netscape $f
fi
else
mylynx $f
fi
}
function view_mp3
{
if ((!text)) && RunningX 2>/dev/null
then
how are quotes handled
I cannot decide whose fault it is, mutt or qmail, but I cannot send messages to addresses written in the form "foobar"@thales.memphis.edu My reading of rfc822 is that such a message should be dropped into foobar's mailbox on thales.memphis.edu. So I just do echo | mutt '"foobar"@thales.memphis.edu' and I get, in the bounce, Hi. This is the qmail-send program at thales.memphis.edu. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <"foobar"@thales.memphis.edu>: Sorry, no mailbox here by that name. (#5.1.1) --- Below this line is a copy of the message. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 18112 invoked by uid 502); 30 Nov 2000 21:18:39 - Date: Thu, 30 Nov 2000 15:18:39 -0600 From: [EMAIL PROTECTED] To: "foobar"@thales.memphis.edu Message-ID: <[EMAIL PROTECTED]> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i pine behaves similarly, but when I use qmail-inject, it removes the quotes around foobar before sending the message. Finally, I remark that specifying "foobar"@thales.memphis.edu during an smtp conversation as `rcpt to:' is fine; the quotes get removed. My impression is that mutt just simply puts <> around the address without removing the quotes ""---hence creating an invalid address in case of "foobar"@thales.memphis.edu. Thx -- --- Mate Wierdl | Dept. of Math. Sciences | University of Memphis
Re: Virtualhost and jailing to ~...OOPS...
On Sat, Dec 02, 2000 at 02:13:30PM +0530, Suresh Ramasubramanian wrote: > Robert Sweet proclaimed on mutt-users that: > > [...] > > But on a SuSe 6.4 box with updated proftd it doesn't work. > [...] > > The proftpd list is down the hall, third door to the right :) > > -- > Suresh Ramasubramanian + Wallopus Malletus Indigenensis > mallet @ cluestick.org + Lumber Cartel of India, tinlcI > [Wisdom] is a tree of life to those laying > hold of her, making happy each one holding her fast. > -- Proverbs 3:18, NSV Sorry...too many lists...not enough time <|80) -- [EMAIL PROTECTED]| Don't change the reason, just -o) | change the excuses! -- Joe Linux, the Choice /\ | Cointment of a GNU generation _\_v | |
Re: problem using quoted printable encoding with gpg
On 2000-12-02 10:43:07 -0500, Sam Varshavchik wrote: >>> Sendmail has been rewriting 8bit to quoted-printable content >>> for decades, when relaying 8bit mail to 7bit-only relays. >> First of all, sendmail has of course not done that "from the >> beginning", since it's considerably older than MIME. That MIME > Sorry to confuse you with facts, but the entire purpose behind > sendmail's creation was to be able to push mail between widely > dissimilar systems that used widely different mail formats. Oh yes, of course, it has been rewriting 8bit to quoted-printable "for decades", which was your original claim - see above. You may wish to notice that quoted-printable hasn't been specified before the early nineties. Maybe you try to get _your_ facts straight. > A small quote from the Oreilly book > (http://www.bigmouse.net/literature/Oreilly/sendmail/prf1_02.htm): >Responding to these and other changes, Eric evolved >delivermail into sendmail. To ensure that messages transferred >between networks would obey the conventions required by those >networks, Eric took a "liberal" approach - modifying address >information to conform, rather than rejecting it. At the time, >for example, UUCP mail often had no headers at all, so >sendmail had to create them from scratch. > Facts can be a stubborn thing, heh? Sendmail has been rewriting > messages for years -- yes, "from the beginning" -- even before > MIME came into being. MIME is just a modern standard for > rewriting mail in today's environment. You may wish to notice that there is a difference between rewriting headers (which sendmail has been doing for a long time), and between messing around with the mail body. >> rewriting stuff is a rather new invention, > No it's not. Of course not - when you rip things out of context. > Anything that requires mail to be delivered from point A to point > B with its headers intact is a completely broken protocol. This is ridiculous. One could, just as well, argue that any protocol which isn't even able to transport messages without messing around with them is broken. >>> Bottom line: RFC 1847 is broken. It breaks several decades' >>> worth of established mail protocols and conventions. >> This is nonsense. Please try getting a clue about e-mail >> standards before you start coding. > Well, then, Einstein, go ahead and code up a mail server, to show > me how. Why should I? There are nicely working MTAs which (1) don't ignore the relevant specifications and (2) whose authors do have a clue. Try looking at sendmail, postfix, or qmail for reference. -- Thomas Roessler <[EMAIL PROTECTED]>
my email address in From: is incorrect
Help, I've just recently begun using Mutt but the email address that it thinks is mine is incorrect. How does Mutt find my email address to use in the From: header when I send an email? And how do I change it? I'm not using Mutt to compose this so a direct response to me will reach me. Thanks, Ben - Get your own FREE, personal Netscape WebMail account today at http://home.netscape.com/webmail
Re: my email address in From: is incorrect
On Sat, Dec 02, 2000 at 09:27:58PM -0500, Ben Heard wrote: > Help, > > I've just recently begun using Mutt but the email address that it thinks is > mine is incorrect. How does Mutt find my email address to use in the From: > header when I send an email? And how do I change it? I'm not using Mutt to > compose this so a direct response to me will reach me. > Use "my_hdr From: <[EMAIL PROTECTED]>" in your ~/.muttrc kent -- "In order to make an apple pie from scratch, you must first create the universe." - Carl Sagan
(at least) a few questions...
Why doesn't mutt use summary files like Netscape to reduce mbox load time? Is there a command to advance to the next unread message in any mailbox specified by the 'mailboxes' setting? When I send mail fcc-ed to one of the mailboxes in 'mailboxes', mutt reports new mail in that mailbox. Is there any way to avoid this? When I type ":set pgp_verify_sig no", mutt 1.2.4i says, "unknown variable", though this variable is listed in my manual.txt. mutt -v reports > Mutt 1.2.4i (2000-07-07) > Copyright (C) 1996-2000 Michael R. Elkins and others. > Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. > Mutt is free software, and you are welcome to redistribute it > under certain conditions; type `mutt -vv' for details. > > System: Linux 2.2.5-15 [using slang 10202] > Compile options: > -DOMAIN > -DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK > -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX > +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -ENABLE_NLS > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/spool/mail" > SHAREDIR="/usr/local/share/mutt" > SYSCONFDIR="/usr/local/etc" > ISPELL="/usr/bin/ispell" With PGP/MIME, is there any easy solution that allows people with PGP/MIME-capable mail clients to receive PGP/MIME and everybody else to receive traditional PGP messages? I'm thinking a procmail recipe that looks at incoming email and puts the sender's email address in /home/dan/.pgpmime-capable or /home/dan/.pgpmime-notcapable. If the email is PGP/MIME, the sender goes in .pgpmime-capable. If the email is PGP traditional, the sender goes in .pgpmime-notcapable . If the User-Agent or X-Mailer or From is one of those that deal really really horribly with PGP/MIME (Outlook (Express?), Hotmail, et al.), the sender goes in pgpmime-notcapable . Then, in .muttrc... sendhook . 'unset pgp_create_traditional' # If we don't know, send them PGP/MIME to encourage them to # use PGP/MIME. source "sed -e \"s/^\\(.*\\)$/send-hook '~t \1' 'set pgp_create_traditional'/\" < /home/dan/.pgpmime-notcapable" source "sed -e \"s/^\\(.*\\)$/send-hook '~t \1' 'unset pgp_create_traditional'/\" < /home/dan/.pgpmime-capable" # (The escaping of shell commands in .muttrc is miserable, btw). Is there any better solution? Are there any other clients that deal horribly with PGP/MIME? BTW, how do you verify PGP/MIME signatures with PGP 6 for Windows? -- Daniel J. Peng /"\ \ / ASCII Ribbon Campaign Who is John Galt?X Against Outlook & HTML Mail / \ http://www.thebackrow.net/ Q: How many surrealists does it take to change a light bulb? A: Two, one to hold the giraffe, and the other to fill the bathtub with brightly colored machine tools. [Surrealist jokes just aren't my cup of fur. Ed.]
