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 very
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 to figure
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
[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
quite
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
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
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
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.asc
On Wed, May 26, 2004 at 10:35:58 +0200, bing yu wrote:
when i attache a MS doc file in my outgoing mail. the doc file can
display properly in mutt
but mutt can not display doc when i got doc attachment from others.
A typical cause is that those messages don't declare the proper MIME type
i have installed wvHtml and it works
~/.mailcap
application/msword; wvHtml --charset=gb2312 %s - | lynx --dump -stdin;
nametemplate=%s.html; copiousoutput
text/html; lynx --dump %s; nametemplate=%s.html; copiousoutput
~/.muttrc
set implicit_autoview = yes
auto_view text/html application/msword
On Tue, Apr 13, 2004 at 10:37:37PM +0200, Kai Timmer wrote:
Hallo,
ich hab da folgendes Problem mit mutt und esmtp. Wie sich schon aus dem
Programmen schließen lässt versende ich meine Mails mit mutt und als
MTA benutze ich esmtp. esmtp leitet die Mails dann auf meinen Mailserver
weiter
* Jakob Lell [EMAIL PROTECTED] [2004-04-14 12:29]:
On Tue, Apr 13, 2004 at 10:37:37PM +0200, Kai Timmer wrote:
das liegt definitiv an deinem richtigen Mailserver. Dieser erzeugt
einen Received-Header, in dem steht, dass er die Mail von deiner IP
bekommen hat. Spamassassin liest den
On Wed, Apr 14, 2004 at 07:54:54PM +0200, Kai Timmer wrote:
* Jakob Lell [EMAIL PROTECTED] [2004-04-14 12:29]:
On Tue, Apr 13, 2004 at 10:37:37PM +0200, Kai Timmer wrote:
das liegt definitiv an deinem richtigen Mailserver. Dieser erzeugt
einen Received-Header, in dem steht, dass er die Mail
Hallo,
ich hab da folgendes Problem mit mutt und esmtp. Wie sich schon aus dem
Programmen schließen lässt versende ich meine Mails mit mutt und als
MTA benutze ich esmtp. esmtp leitet die Mails dann auf meinen Mailserver
weiter.
Nun bekomme ich, wenn ich mir selber eine Mail schreibe von
Hallo Liste,
auf meinem Rechner läuft Debian 3.0(Woody) und als Mailprogramm
will ich mutt verwenden.
Postfix und fetchmail funktionieren wunderbar nur mutt macht
mir Probleme.
Mutt zeigt mir keine deutschen Umlaute an, wenn ich mails
lese.
Ich habe die Umgebungsvariablen LANG und LC_CTYPE beide
On Sun, Oct 26, 2003 at 02:45:35PM +0100, Thomas Bulka wrote:
Ich habe die Umgebungsvariablen LANG und LC_CTYPE beide
auf de_DE
gesetzt, aber das hat keine Auswirkung.
Habe ich etwas vergessen ?
vielleicht fehlt bei dir diese locale ?
1) ist das packet locales installiert ?
2) wenn ja:
Hallo Liste,
es klappt jetzt, ich glaube ich hatte vergessen
locale-gen auszuführen.
Vielen Dank.
Gruß :
Thomas
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject
On Sun, Oct 26, 2003 at 02:45:35PM +0100, Thomas Bulka wrote:
Hallo Liste,
...
Mutt zeigt mir keine deutschen Umlaute an, wenn ich mails
lese.
Ich habe die Umgebungsvariablen LANG und LC_CTYPE beide
auf de_DE
gesetzt, aber das hat keine Auswirkung.
Habe ich etwas vergessen ?
(Meine
Hi,
I've been using mutt with vim for a couple of years with no problem.
But recently I've noticed that when I reply and begin inserting text (on
the same line as, and right before the original message), the line does
not wrap when I get to 77 spaces (what I have set in .vimrc). What
happens is
Thus spake Ric Otte:
Hi,
I've been using mutt with vim for a couple of years with no problem.
But recently I've noticed that when I reply and begin inserting text (on
the same line as, and right before the original message), the line does
not wrap when I get to 77 spaces (what I have set in
Nathan,
I tried your suggestion, but that doesn't seem to change the behaviour. The
lines still don't wrap (I had to hit a Return to get the above line to
break).
I am using Mutt 1.5.4-1 and vim 6.1-320+1.
Thanks,
Ric
On Wed, Oct 01, 2003 at 01:03:30PM -0500, Nathan Poznick wrote:
Thus spake
On Wed, Oct 01, 2003 at 10:50:41AM -0700, Ric Otte wrote:
I've been using mutt with vim for a couple of years with no problem.
But recently I've noticed that when I reply and begin inserting text (on
the same line as, and right before the original message), the line does
not wrap when I get to
Hi,
Well, after trying many different things, I finally got it to work. I
put the following line in my .vimrc:
au FileType mail set tw=70 fo=tcrq2 nomodeline
I don't know why that solved the problem, and the line:
set textwidth=77
in .vimrc didn't work. But at least it is working. Thanks
On Wed, Oct 01, 2003 at 02:21:46PM -0700, Ric Otte wrote:
Hi,
Well, after trying many different things, I finally got it to work. I
put the following line in my .vimrc:
au FileType mail set tw=70 fo=tcrq2 nomodeline
I've been seeing the same thing, but attributed it to me being new to
* 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 imap server:
* 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:43]:
I'm
* 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]
with a
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
--
* 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
server.
* 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 a new
* 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 unexpected length
At Tue, Sep 10 2002 [22:21 +0200], Steffen Schulz aroused my curiosity with:
So wie ich das sehe, ändert Kmail den absender in [EMAIL PROTECTED]
und dein mutt tut das nicht, sondern trägt als Absender
[EMAIL PROTECTED] ein. Abhilfe könnte die Datei sender_canonical in
/etc/postfix/
hallo,
nach einem upgrade auf sarge kann ich mit mutt keine mails mehr versenden.
/var/log/syslog sagt dazu:
Sep 10 12:32:07 client10 postfix/pickup[1229]: 75A9BF7483: uid=1000
from=celine
Sep 10 12:32:07 client10 postfix/cleanup[1603]: 75A9BF7483:
message-id=[EMAIL PROTECTED]
Sep 10 12:32:07
On Tue, Sep 10, 2002 at 12:49:08PM +0200, michael bode wrote:
hallo,
nach einem upgrade auf sarge kann ich mit mutt keine mails mehr versenden.
/var/log/syslog sagt dazu:
Sep 10 12:32:11 client10 postfix/smtp[1610]: B2AB0F742B: to=[EMAIL PROTECTED],
relay=mx0.gmx.net[213.165.64.100],
Eigentlich steht da sicherlich alles,
ich habe mir das jetzt ein weiteres mal angeguckt wenn ich die mail mit kmail
verschicke, das sieht dann so aus:
Sep 10 13:57:00 client10 postfix/smtpd[1918]: connect from
localhost[127.0.0.1]
Sep 10 13:57:00 client10 postfix/smtpd[1918]: D2787F742B:
On 020910 at 17:50, michael bode [EMAIL PROTECTED] wrote:
Eigentlich steht da sicherlich alles,
ich habe mir das jetzt ein weiteres mal angeguckt wenn ich die mail mit kmail
verschicke, das sieht dann so aus:
[...]
wenn ich das logfile nun richtig lese ist das der gleiche absender, der
On Tue, Jul 02, 2002 at 11:40:38PM +0200, Thorsten Gunkel wrote:
On Mon, Jul 01, 2002 at 10:30:59PM +0200, Norbert Preining wrote:
Hi,
Es gibt andere Möglichkeiten: es fliegen divers epatches herum, die
das erledigen. patch-1.3.26.dw.pgp-traditional.2.txt zb. Ich habe für die
Soweit
hi
ich wollte gerade eine mit gnupg signierte mail an jemand schicken
der outlook express als mail prgramm benutzt. der jemand hat auch
pgp 6.5.8 drauf. das problem ist das mein text den ich schreibe
dort als anhang (ATTzahl) ankommt. was muss ich machen damit mutt
meine mails auch fuer
On Mon, Jul 01, 2002 at 09:58:52PM +0200, Janto Trappe wrote:
macro compose xNAME Fgpg -es --textmode --armor -r DEINE_KEY-ID -r
EMPFAENGER_KEY-ID\ny
hi
hmm das wuerde aber dann nur fuer einen bestimmten empfaenger gehen da ich ja die
empfaenger-key-id eigegeben habe
oder?
mfg
olli
--
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, either in
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 receive
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 receive
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!
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
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
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...
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 extension?
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 preceeding
the
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 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
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 handling
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 available
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
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
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/splitted
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
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
57 matches
Mail list logo
