On Tue, May 23, 2006 at 10:40:11AM +0200, Bruno Boettcher wrote:
> Hello!
>
> since i passed onto a amd64 machine i noticed that the basic charset
> used is utf8
>
> but mutt displays that in hex codes, with a \ prepended...
>
> reading french and german mails in the great majority, this isn't v
[pushing the discussion back on-list]
At 1148408048 past the epoch, Bruno Boettcher wrote:
> On Tue, May 23, 2006 at 04:06:57PM +0100, Jon Dowland
> wrote:
> > I do have some issues, however, using this underneath a
> > screen session.
>
> ehm i am exactly under a screen session since i migrate
>
At 1148378437 past the epoch, Andrew Sackville-West wrote:
> edit the link in /etc/alternatives so that editor points to vim
> instead of nano.
That'll still get zapped on upgrade if nano carries a lower priority
(which it seems to).
--
Jon Dowland
http://alcopop.org/
--
To UNSUBSCRIBE, email
On Tue, May 23, 2006 at 01:26:13PM +0200, Florian Kulzer wrote:
> On Tue, May 23, 2006 at 10:40:11 +0200, Bruno Boettcher wrote:
>
> [...]
>
> > BTW at each update my default editor is changed to that horrible nano
> > instead of the normal vim, any way to stop this?
>
> I did not yet have time
On Tue, May 23, 2006 at 10:40:11AM +0200, Bruno Boettcher wrote:
[...]
>
> BTW at each update my default editor is changed to that horrible nano
> instead of the normal vim, any way to stop this?
>
edit the link in /etc/alternatives so that editor points to vim
instead of nano.
A
signature.a
At 1148380811 past the epoch, Bruno Boettcher wrote:
> since i passed onto a amd64 machine i noticed that the
> basic charset used is utf8
>
> but mutt displays that in hex codes, with a \ prepended...
>
> is there a solution to this?
Well it doesn't happen to me with LANG=en_GB.UTF-8, locales
2
On Tue, May 23, 2006 at 10:40:11 +0200, Bruno Boettcher wrote:
[...]
> BTW at each update my default editor is changed to that horrible nano
> instead of the normal vim, any way to stop this?
I did not yet have time to figure out why every vim upgrade now
redirects /etc/alternatives/editor to so
Hello!
since i passed onto a amd64 machine i noticed that the basic charset
used is utf8
but mutt displays that in hex codes, with a \ prepended...
reading french and german mails in the great majority, this isn't very
practical...
is there a solution to this?
BTW at each update my default edi
* Dan Hunt <[EMAIL PROTECTED]> [2003-09-04 11:22]:
> > set ssl_starttls=no
> >
> > And try to connect. Just a WAG, but it might help.
> >
> Great guess, fixed that right up.
Excellent! Glad I could help.
Regards,
--
dave [ please don't CC me ]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
* David J. Weller-Fahy <[EMAIL PROTECTED]> [2003-09-04 08:02]:
> * Dan Hunt <[EMAIL PROTECTED]> [2003-09-03 20:32]:
> > * David J. Weller-Fahy <[EMAIL PROTECTED]> [2003-09-03 21:10]:
> > > * Dan Hunt <[EMAIL PROTECTED]> [2003-09-03 18:22]:
> > > > * Grzesiek Sedek <[EMAIL PROTECTED]> [2003-09-03 18
* Dan Hunt <[EMAIL PROTECTED]> [2003-09-03 20:32]:
> * David J. Weller-Fahy <[EMAIL PROTECTED]> [2003-09-03 21:10]:
> > * Dan Hunt <[EMAIL PROTECTED]> [2003-09-03 18:22]:
> > > * Grzesiek Sedek <[EMAIL PROTECTED]> [2003-09-03 18:43]:
> > > > I'm getting this weird error when trying to connect to im
* David J. Weller-Fahy <[EMAIL PROTECTED]> [2003-09-03 21:10]:
> * Dan Hunt <[EMAIL PROTECTED]> [2003-09-03 18:22]:
> > * Grzesiek Sedek <[EMAIL PROTECTED]> [2003-09-03 18:43]:
> > > I'm getting this weird error when trying to connect to imap server:
> > >
> > > gnutls_handshake: A TLS packet with
* Dan Hunt <[EMAIL PROTECTED]> [2003-09-03 18:22]:
> * Grzesiek Sedek <[EMAIL PROTECTED]> [2003-09-03 18:43]:
> > I'm getting this weird error when trying to connect to imap server:
> >
> > gnutls_handshake: A TLS packet with unexpected length was received
>
> Hey! I am having the same problem with
* Grzesiek Sedek <[EMAIL PROTECTED]> [2003-09-03 18:43]:
> Hello everybody,
> I'm getting this weird error when trying to connect to imap server:
>
> gnutls_handshake: A TLS packet with unexpected length was received
Hey! I am having the same problem with a new installation, and a Red-Hat
serve
Hello everybody,
I'm getting this weird error when trying to connect to imap server:
gnutls_handshake: A TLS packet with unexpected length was received
and then session drops.
When I'm on the server itself and connect to imap everything is fine!
any ideas?
Many thanks.
ps: please cc me
--
Grze
On Fri, Mar 22, 2002 at 09:13:02PM -0600, ktb wrote:
> On Fri, Mar 22, 2002 at 06:09:21PM -0300, Marcelo Chiapparini wrote:
> > Hello,
> >
> > I am running woody and mutt. I have a problem with the attached files in
> > mutt:
> > mutt insists in put the attached file in the body of the message,
On Fri, Mar 22, 2002 at 06:09:21PM -0300, Marcelo Chiapparini wrote:
> Hello,
>
> I am running woody and mutt. I have a problem with the attached files in
> mutt:
> mutt insists in put the attached file in the body of the message, either in
> the messages I send as well as the messages I receiv
On Fri, Mar 22, 2002 at 06:09:21PM -0300, Marcelo Chiapparini wrote:
> Hello,
>
> I am running woody and mutt. I have a problem with the attached files in
> mutt:
> mutt insists in put the attached file in the body of the message, either in
> the messages I send as well as the messages I receiv
Hello,
I am running woody and mutt. I have a problem with the attached files in mutt:
mutt insists in put the attached file in the body of the message, either in
the messages I send as well as the messages I receive with attached files.
Does exist an option for fix this problem?
Thank you!
Ma
Sean,
> Today I upgraded mutt to 1.3.24-3. Now mutt seems to think
> that my mailbox is read-only, which it is not. Checked out
> the on-line help and muttrc files but didn't see anything
> helpful. Suggestions anyone?
# chown root:mail /usr/bin/mutt_dotlock
# chmod 2755 /usr/bin/mutt
Hello,
Today I upgraded mutt to 1.3.24-3. Now mutt seems to think
that my mailbox is read-only, which it is not. Checked out
the on-line help and muttrc files but didn't see anything
helpful. Suggestions anyone?
Thanks,
sean
ps. cc: me please
pgpvgbmoEH8sd.pgp
Description: PGP signature
Hi all...
Don't know if this has been addressed already or not, but if so I
missed it.
For about the last week I've been unable to update mutt in unstable.
This is what apt says:
(03:21pm) root: ~ $ apt-get install mutt
Reading Package Lists... Done
Building Dependency Tree... D
On Sun, Jan 09, 2000 at 07:53:28PM +, Paul J. Keenan wrote:
> On Sat, Jan 08, 2000 at 02:50:14PM +, Paul J. Keenan wrote:
> > On Sat, Jan 08, 2000 at 12:24:26PM +0100, Wojciech Zabolotny wrote:
> > > Hi All,
> > >
> > > The problem is that I don't know what does mean the underscore precee
On Sat, Jan 08, 2000 at 02:50:14PM +, Paul J. Keenan wrote:
> On Sat, Jan 08, 2000 at 12:24:26PM +0100, Wojciech Zabolotny wrote:
> > Hi All,
> >
> > The problem is that I don't know what does mean the underscore preceeding
> > the paranthesis around the string definition?
> > Is it a GCC ext
On Sat, Jan 08, 2000 at 12:24:26PM +0100, Wojciech Zabolotny wrote:
> Hi All,
>
> The problem is that I don't know what does mean the underscore preceeding
> the paranthesis around the string definition?
> Is it a GCC extension?
> --
> Wojciech Zabolotny
>
Hi All,
A few days ago I've written about problems with self-packaged
mutt 1.0.1 in slink.
I've investigated problem more thoroughly, and found, that the
failing instruction is:
623 mutt_message (_("Reading %s..."), ctx->path);
The stack trace is as follows:
(gdb) bt
#0 0x40089387 in
On Mon, Dec 20, 1999 at 10:50:21PM +, Jonathan McDowell wrote:
>
> On Mon, Dec 20, 1999 at 11:41:52PM +0100, Wojciech Zabolotny wrote:
>
> > > I had this problem too and upgraded to mutt 1.0i and it's gone away, so
> > > I guess it was a known bug that got fixed.
> > Is the mutt 1.0i availabl
> On Mon, Dec 20, 1999 at 11:41:52PM +0100, Wojciech Zabolotny wrote:
> 1.0 appears to be in unstable according to a search on
> http://www.debian.org/distrib/packages
>
> > Is it able to handle automatically multipart/splitted messages (eg.
> > generated by mpack)?
Mutt has very sophsticated han
On Mon, Dec 20, 1999 at 11:41:52PM +0100, Wojciech Zabolotny wrote:
> > I had this problem too and upgraded to mutt 1.0i and it's gone away, so
> > I guess it was a known bug that got fixed.
> Is the mutt 1.0i available somewhere as a debian package?
1.0 appears to be in unstable according to a
On Mon, Dec 20, 1999 at 08:48:36PM +, Jonathan McDowell wrote:
>
> I had this problem too and upgraded to mutt 1.0i and it's gone away, so
> I guess it was a known bug that got fixed.
Is the mutt 1.0i available somewhere as a debian package?
Is it able to handle automatically multipart/splitt
On Mon, Dec 20, 1999 at 06:57:17PM +0100, Wojciech Zabolotny wrote:
> I can't force my mutt/gpg set to work properly. Signing of messages
> works fine (as can be seen from this message :-) ), but I can't
> encrypt a message to be sent to somebody. I have the recipient's
> public key in my public
Hi all,
I can't force my mutt/gpg set to work properly. Signing of messages works fine
(as can be seen from this message :-) ), but I can't encrypt a message to be
sent
to somebody. I have the recipient's public key in my public keyring. I can
encrypt the date with this recipient's public key usi
You can also set exim up to do this. In the past I have had success with
the following at the bottom of my exim.conf file, in the REWRITE
CONFIGURATION part of the file:
# This rule performe a rewrite on all outgoing mail (possibly only all
# non-local mail, I'm not quite clear, but probably moo
33 matches
Mail list logo
