On Fri, Dec 01, 2000 at 12:22:57AM -0500 or thereabouts, Ken Weingold wrote:
> When mutt sits for a while on 'Sending message...', is it a mutt or
> sendmail issue? Or something else?
This is the same problem that I have mentioned earlier. Many thought
it was a sendmail problem. However, I ha
When mutt sits for a while on 'Sending message...', is it a mutt or
sendmail issue? Or something else?
Thanks.
-Ken
--
[EMAIL PROTECTED]AIM: ScopusFest
I wrote a couple perl scripts that will display a signature path from your
key to the signer of an email, while verifying the signature of the email.
They can be found at http://www.chaosreigns.com/code/mutt-sigtrace/
The output looks like:
[-- PGP output follows (current time: Thu Nov 30 23:10:
On 001130, at 18:32:42, Anand Buddhdev wrote:
> Ok. I've done some more digging. After I send a signed message, I can
> verify the fcc copy. However, I can't verify the cc: copy, and also,
> the recipient can't verify the copy he receives. I've traced it down to
> the following:
>
> The boundary
Bruce A. Petro muttered:
> Can this be done? What I want is to do a tag and then a save to mailbox...
>
> For instance I thought it would be something like this:
> macro index .x "T~t [EMAIL PROTECTED]\n; ;s =bap-test"
> but that isn't seeming to do it. Any suggestions?
>
> Question2: How can
You were on the right track Anand. I changed the
permissions on the /etc directory per the other
reply (from Peter) to my plea for help. And now
you see this message is from the problem child
(linux box).
Thanks,
kelly
Quoting Anand Buddhdev <[EMAIL PROTECTED]>:
On Thu, Nov 30, 2000 at 11:1
Have you ever just felt really, really stupid? I
do now.
I could have sworn that I looked at that, but I
guess I just overlooked it.
Thanks Peter.
kelly
Quoting Peter Pentchev <[EMAIL PROTECTED]>:
On Thu, Nov 30, 2000 at 11:11:02AM -0600, Kelly Scroggins wrote:
[snip]
>
> /etc/se
On 2000-11-30 17:24:57 +, Steve Kennedy wrote:
> Upgrade to qmail ;)
... or postfix, which looks a bit better when you're looking for a
drop-in replacement for sendmail.
--
Thomas Roessler <[EMAIL PROTECTED]>
Kelly Scroggins proclaimed on mutt-users that:
> I'm having a problem sending mail *>OUT<* of my Linux box. Recieving
> mail works very well.
> Starting sendmail: WARNING: Group writable directory /etc
> WARNING: Group writable directory /etc
> WARNING: Group writable directory /etc
sounds obv
On Thu, Nov 30, 2000 at 11:11:02AM -0600, Kelly Scroggins wrote:
The problem isn't sendmail. It's your /etc directory, as the log shows.
Somehow, you've given it group write permission. As root, run the following
command, and you should be fine:
# chmod 0755 /etc
> I'm having a problem sending
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
Kelly Scroggins <[EMAIL PROTECTED]> wrote:
>
> This problem just 'suddenly' appeared a month or two ago. Everything
> worked very well for several months.
[...]
> Starting sendmail: WARNING: Group writable directory /etc
> WARNING: Group writable directory /etc
> WARNING: Group writable directo
On Mon, Nov 27, 2000 at 11:40:35PM -0800, David Ellement wrote:
[ Background: I was having trouble verifying PGP signatures within mutt. I
thought it might have been a mutt issue, and asked on the mutt list. Now
I think it is a courier issue, hence the Cc: to Sam Varshavchik ]
> Perhaps you woul
On Thu, Nov 30, 2000, Kelly Scroggins wrote:
> The error produced by Mutt is :
>
> /etc/sendmail.cf: line 90: fileclass: cannot open /etc/sendmail.cw:
> Group writable directory
It's not mutt, it's sendmail.
> -rw-r--r-- 1 root root 59 Sep 1 1999 /etc/sendmail.cw
It's complaining about th
On Thu, Nov 30, 2000 at 11:11:02AM -0600, Kelly Scroggins wrote:
> I'm having a problem sending mail *>OUT<* of my Linux box. Recieving
> mail works very well.
> This problem just 'suddenly' appeared a month or two ago. Everything
> worked very well for several months.
> The Linux box is Red Ha
I'm having a problem sending mail *>OUT<* of my Linux box. Recieving
mail works very well.
This problem just 'suddenly' appeared a month or two ago. Everything
worked very well for several months.
The Linux box is Red Hat 6.1, stock kernel, and the email client is Mutt
1.0pre3us.
The erro
Paul A. Cheshire [[EMAIL PROTECTED]] wrote:
> Can anyone tell me where to get this? I tried www.mutt.org and
> linux.tucows.com but they have only earlier versions.
www.mutt.org and tucows are listing the current *stable* version. 1.3.x is
the *development* version. Get them from ftp.mutt.org/p
Awhile ago, someone posted an extremely helpful save-hook:
save-hook . "+%(%Y%m)/%a" # Save mails to date-received/user@host
I'd like to turn that into an fcc-save-hook, but fcc doesn't work right.
I'm missing something obvious, but what?
--
Lance Simmons
- - - - - - - - - - - - - - - - -
On 2000-11-30 09:34:56 +, Conor Daly wrote:
> > mailboxes ! {server}INBOX.mutt-users
> What's the exclamation mark for.
It's a short-hand for your inbox.
--
Thomas Roessler <[EMAIL PROTECTED]>
On 2000-11-29 19:52:54 +, Paul A. Cheshire wrote:
> Subject: latest version of mutt (1.3.14i?)
1.3.12i is the latest version.
--
Thomas Roessler <[EMAIL PROTECTED]>
On Mon, Nov 27, 2000 at 09:06:29PM -0500 or thereabouts, Tabor J. Wells wrote:
> On Mon, Nov 27, 2000 at 08:01:29PM +,
> Conor Daly <[EMAIL PROTECTED]> is thought to have said:
>
> > Ah, got it!
> >
> > use
> >
> > folder-hook INBOX.mutt-users set sort=thread
> >
> > instead so long as the
On Wed, Nov 29, 2000 at 10:05:49PM +0100, Daniel González Gasull wrote:
> Hi! :-)
>
> * Magnus Bodin <[EMAIL PROTECTED]> wrote To [EMAIL PROTECTED]:
>
> > Couldn't it be left as an exercise to the witted
> > user or 3rd-party-developer to write a good
> > search-enginge (probably based on grepma
On Wed, Nov 29, 2000 at 10:47:58AM +0100, Jesper Holmberg wrote:
>
> Subject: Re: Konstituerande =?iso-8859-1?Q?m=F6te?= , FRV
>
> My guess would be that this means there is something wrong with the
> character encoding between the systems. But how would one correct
> this, apart from manually e
23 matches
Mail list logo