Re: Attachment weirdness

2019-05-14 Thread jeremy bentham
On Tue, May 14, 2019 at 07:35:39AM +1000, Cameron Simpson wrote: > On 13May2019 15:45, Patrick Shanahan and Cameron Simpson wrote: > >>I used xwd to take a screen dump, then imagemagick to trim and > >>save it as a gif. > >iianm, mutt does not "decide" the file-type, mime does. you need to >

Attachment weirdness

2019-05-13 Thread jeremy bentham
I used xwd to take a screen dump, then imagemagick to trim and save it as a gif. When I tried to attach it to a message, mutt decided it was "audio/basic", as it did with a jpeg of the same image. png gave me "image/png" so I did, finally, get what I wanted. But the file, of course, is a lot

Re: Undependable macro

2013-06-20 Thread jeremy bentham
On Mon, Jun 17, 2013 at 10:28:54AM -0500, David Champion wrote: * On 16 Jun 2013, jeremy bentham wrote: I have a macro which works...sometimes. macro generic,pager ,t :set folder=imaps://mail.eskimo.comenterc =tomsenter*v/AMenterenter (All one long line in my muttrc; I broke it up

Undependable macro

2013-06-16 Thread jeremy bentham
I have a macro which works...sometimes. macro generic,pager ,t :set folder=imaps://mail.eskimo.comenterc =tomsenter*v/AMenterenter (All one long line in my muttrc; I broke it up for readability here.) If it fails, when I launch it mutt beeps immediately after I hit t and doesn't complete it.

Re: mail relaying [solved, sort of]

2012-06-27 Thread jeremy bentham
On Tue, Jun 26, 2012 at 01:16:24PM +0300, Alexander Gattin wrote: I tried my best to not give a clueless advice this time, so before suggesting to omit the user@ part from smtp_url I studied the mutt-1.5.20/smtp.c source: if (conn-account.flags M_ACCT_USER) { if (!mutt_bit_isset

Re: mail relaying [solved, sort of]

2012-06-25 Thread jeremy bentham
On Mon, Jun 25, 2012 at 11:13:15AM +0300, Alexander Gattin wrote: [...] msmtp does SMTP well, and I use msmtp instead of smtp_url -- that's why my advices earlier in the thread missed the target. I have the last suggestion though: try to omit user@ part from smtp_url. I'm sure I tried

Re: mail relaying [solved, sort of]

2012-06-24 Thread jeremy bentham
On Sat, Jun 23, 2012 at 07:45:32PM -0400, Patrick Shanahan wrote: * jeremy bentham d...@eskimo.com [06-23-12 19:36]: ... Ok, I installed msmtp and after a bit of flailing about got it working. Part of the flailing included an error message from mail.eskimo.com that it didn't support

Re: mail relaying [solved, sort of]

2012-06-23 Thread jeremy bentham
On Fri, Jun 22, 2012 at 06:37:54PM -0700, jeremy bentham wrote: On Jun 22 you wrote: Hello, On Thu, Jun 21, 2012 at 05:06:40PM -0700, jeremy bentham wrote: [stuff about inability to send mail from my own machine's mutt] instant connection refused, with either smtp or smtps

Re: mail relaying

2012-06-22 Thread jeremy bentham
On Jun 22 you wrote: Hello, On Thu, Jun 21, 2012 at 05:06:40PM -0700, jeremy bentham wrote: instant connection refused, with either smtp or smtps, ssl_starttls yes or no. I've checked ports on mail.eskimo.com with nmap: PORT STATESERVICE 25/tcp open smtp 465/tcp

Re: mail relaying

2012-06-21 Thread jeremy bentham
On Jun 21 you wrote: ... incoming-folders=Mail/[] eski {mail.eskimo.com/ssl/novalidate-cert}mail/today As I understand, mail.eskimo.com/ssl translates to smtp_url=smtps://u...@mail.eskimo.com:465, i.e. it's SSL from the beginning, not STARTTLS, and it's served on port 465, not 587 or 25.

Re: mail relaying

2012-06-20 Thread jeremy bentham
On Jun 20 you wrote: Hello, On Tue, Jun 19, 2012 at 11:47:53AM -0700, jeremy bentham wrote: I can't send mail from my local machine, using my isp's smtp server. I can do it just fine from pine, providing I have started an imap session on one of my isp's machines. (I'm doing

mail relaying

2012-06-19 Thread jeremy bentham
I recently switched to mutt from pine, and I like it a lot, except for one thing: I can't send mail from my local machine, using my isp's smtp server. I can do it just fine from pine, providing I have started an imap session on one of my isp's machines. (I'm doing this message in pine). But,