difficult-to-obtain smtppush
can anyone give me a link to smtppush (by Michael Elkins)? niether http://www.sigpipe.org/~me/smtppush/ nor http://www.toesinperil.com/~me/smtppush/ does not work. Michael? ;-) 10x, karlov.
Re: difficult-to-obtain smtppush
On Tue, 22 Jan 2002 07:06:30 -0500, David T-G [EMAIL PROTECTED] wrote: % % can anyone give me a link to smtppush (by Michael Elkins)? % niether http://www.sigpipe.org/~me/smtppush/ Try sigpipe.org:8080, IIRC. -- exactly. 404. but: have been found at http://kldp.org/~eunjea/mutt.php#sendmail 10x to Im Eunjea ;-) % nor http://www.toesinperil.com/~me/smtppush/ does not work. % Michael? ;-)
Re: charset in text/plain attachments: how to tune?
On Fri, 28 Dec 2001 17:55:55 +0100, Michael Tatge [EMAIL PROTECTED] wrote: boris karlov muttered: On Fri, Dec 28, 2001 at 03:56:56PM +0100, Michael Tatge wrote: Well, is a charset too, isn't it? i've tried this already. but, unfortunately, it does not work: :charset-hook koi8-r\n empty (sub)expression Strange canAt reproduce this with 1.2.5: $ ./mutt -v Mutt 1.2.5i (2000-07-28) mutt -F /dev/null :charset-hook koi8-r no error message. -- i permanently get such an error with FreeBSD 3 and 4 (both STABLE). forget-about, i've found suitable regexp ;-) 10x, karlov.
Re: error sending message
On Fri, 11 Jan 2002 13:30:04 +0100, Nick Wilson [EMAIL PROTECTED] wrote: Hi I'm getting this odd error when sending to a particular address. :error sending message, child exited 67 (User unkown) -- imho, that's MTA report. 10x, karlov.
Re: For messages without charset specified
On Fri, 11 Jan 2002 23:05:19 +0800, Charles Jie [EMAIL PROTECTED] wrote: Thank you, Boris. But that's weird for your case. If you have attachment, your header should have only 'Content-Type: multipart/...' instead of 'text/plain' or 'text/html'. -- but every attachment has its own `Content-Type:' header. e.g. text/plain For my cases, they have the latter content-type and no attachment. They send me inline 8-bit muitibyte (big5) text. Mutt will depend on the charset specified in Content-Type: filed. -- it doesn't matter. attachments were the first thing i've noticed. inline data looks the same. charset-hook: This doesn't look matching my problem. If a message speicifies a strange charset, it can map it. But for my case, messages miss 'charset=big5' and mutt thinks to use some DEFAULT that I don't know where it comes from. -- read referred thread (especially Michael Tatge's comments) thoroughly ;-) My locale is LANG=zh_TW.big5. And my mutt has 'set charset=big5'. I don't know what is missing. -- charset part in header is missing ;-). and mutt assumes us-ascii in this case (check this by view-attachments, usually is bound to v). 10x, karlov. best, charlie On Thu, Jan 10, 2002 at 07:41:38PM +0300, boris karlov wrote: On Thu, 10 Jan 2002 09:48:30 +0800, Charles Jie [EMAIL PROTECTED] wrote: In our country, I used to receive messages without 'charset' specifed in Content-Type:, while the text body is encoded in big5. I have my mutt set charset=big5 but the pager just display '?'s for such messages (other charset-tagged messages are OK). -- i have the same problem. check by view-attachments for assumed charset - is it us-ascii? i have the last one if there's no charset part in header. How can I do it in mutt? set charset=big5 looks not working. On Fri, 28 Dec 2001 Michael Tatge [EMAIL PROTECTED] in thread `charset in text/plain attachments: how to tune?' has supposed to use charset-hook (e.g. charset-hook big5). i have `empty (sub)expression' error in this case, but Michael does not. it's worth a try 10x, karlov.
Re: strange TABs in header
On Tue, 08 Jan 2002 12:04:15 -0500, Andy Spiegl [EMAIL PROTECTED] wrote: Dear Mutters, I suspect that it doesn't have anything to do with mutt, but I don't know who else to ask. The thing is that all of a sudden all mails from a friend of mine (who also uses mutt) have TABs in these three header lines: From:TABname etc To:TABname etc Date:TABdate We have no idea why this happened. So far I didn't even notice it, but now that I use SpamAssassin to filter out my spams (works great!) it complained that these TABs weren't RFC822 compatible. Anyone has seen this before or knows where it could come from? -- imho, that's MTA deal. i have such a TABs in headers with certain ZMailer Server. 10x, karlov.
Re: Saving attachments with unusual names
On Wed, 09 Jan 2002 17:01:30 +0100, Volker Moell [EMAIL PROTECTED] wrote: [..skip..] But isn't it possible that mutt detects the correct/intended filename to save the file Datei Volker Moll 1.jpg instead the file ?iso-8859-1?Q?Datei=5FVolker_M=F6ll=5F1.jpg?= in the $folder directory (=)? [..skip..] -- man muttrc(5). search for `rfc2047_parameters'. 10x, karlov.
saving attach [was: Re: Attachment umask]
On Mon, 31 Dec 2001 12:18:19 +0100, Markus Boelter [EMAIL PROTECTED] wrote: [..skip..] 022? Is it also possible to define a path in the configuration? -- from http://www.mutt.org/changes.html ;-) macro attach s Home~/End Pre-pend ~/ when saving attachments I want to save all attachments in ~/attachments and export this dir via nfs onto my workstation/webserver.
charset in text/plain attachments: how to tune?
mutt-1.2.5i i have charset=koi8-r in .muttrc, but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. so i need to edit-type or manually recode affected attachments :-(. mutt-1.0i works more suitable ;-) using charset from user locale (or may be $MM_CHARSET) while display attachments _without_ charset specified in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? 10x in advance, ~borman
Re: charset in text/plain attachments: how to tune?
On Fri, Dec 28, 2001 at 03:04:41PM +0100, Michael Tatge wrote: boris karlov muttered: i have charset=koi8-r but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? Look for charset-hook in the manual. -- in muttrc(5) i've seen: charset-hook alias charset This command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to mutt. ...messages which _are_tagged_ with a character set name not to mutt... but i mean attachments with Content-Type: text/plain, there is no charset part _at_all_. 10x in advance, ~borman
Re: charset in text/plain attachments: how to tune?
On Fri, Dec 28, 2001 at 03:56:56PM +0100, Michael Tatge wrote: boris karlov muttered: On Fri, Dec 28, 2001 at 03:04:41PM +0100, Michael Tatge wrote: boris karlov muttered: i have charset=koi8-r but mutt always assumes that my text/plain attachments are in us-ascii charset if there is no certain charset record in `Content-Type:' field. do you know how to avoid such a behaviour of 1.2.5? Look for charset-hook in the manual. charset-hook alias charset This command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to mutt. ...messages which _are_tagged_ with a character set name not to mutt... but i mean attachments with Content-Type: text/plain, there is no charset part _at_all_. Well, is a charset too, isn't it? -- i've tried this already. but, unfortunately, it does not work: :charset-hook koi8-r\n empty (sub)expression gonna try `charset-hook another_regexp koi8-r' (e.g. `charset-hook .* koi8-r' ;-)) Michael, 10x. charset kio8-r or the matching ISO-whatever does what you want. I use charset-hook iso-8859-1 for the very same reason. Mutt assumes us-ascii, if nothing is specified - according to the relevant RFCs, I presume. I often get mail with German umlauts from people with broken mailers and the above helps me reading those messages a lot. :)
