Re: Problems sending mail

You'll need to set up the authentication for msmtp. Snippet from msmtprc: defaults account david-email host mx1.dreamhost.com port 25 protocol smtp auth on user youru...@fake.domain.com password yoursecretpassword On Mon, Sep 05, 2022 at 03:49:59PM -0500, David Bryant wrote: Hi. I'm new to th

Problems sending mail

Hi. I'm new to this group. I'm looking for some help. I recently built a Linux from Scratch system. I don't have any kind of graphical interface set up there yet. I would like to use mutt to send and receive email using a tty terminal. Mainyly for educational purposes. I'm composing this messag

Re: order of sending mail and saving to fcc

[Sent before I intended to.] On Sat, Jun 15, 2019 at 01:53:18AM +0200, Nicolas Rachinsky wrote: > @Derek: I've read your mails in this thread, and I'm in no way > convinced. I'd love for you to explain why. Note that Kevin confirmed that my arguments are technically correct. So despite that I t

Re: order of sending mail and saving to fcc

On Sat, Jun 15, 2019 at 01:53:18AM +0200, Nicolas Rachinsky wrote: > I can only say, Erik wrote the answer I wanted to write. > > @Kevin: The new change sounds very promising. Thank you for that > and all your work! > > @Derek: I've read your mails in this thread, and I'm in no way > convinced.

Re: Making attachments [Was: Re: order of sending mail and saving to fcc

On Sun, Jun 16, 2019 at 03:34:00PM +1000, Erik Christiansen wrote: That looks quite useful. There's also the CheckAttach vim plugin, by Christian Brabandt. Starting in 1.10, there is also $abort_noattach in Mutt. It's not quite as useful, because it waits until you hit send and then scans the

Making attachments [Was: Re: order of sending mail and saving to fcc

On 16.06.19 09:48, Cameron Simpson wrote: > I compose with edit_headers=yes, so recipients and subject are part of the > temporary file. > > Also, I attach using the Attach: pseudo header, so the attachment filename > is also part of the temp file. Provided I haven't exited the compose mode > (whe

Re: order of sending mail and saving to fcc

On 11Jun2019 20:21, Nicolas Rachinsky wrote: * Derek Martin [2019-06-11 12:47 -0500]: Not only that, but I neglected the fact that if the send fails, the file your editor produced in order for it to be passed to Mutt will still be on disk, so you do IN FACT still have a copy of the message.

Re: order of sending mail and saving to fcc

On 10Jun2019 11:56, Ben Boeckel wrote: On Mon, Jun 10, 2019 at 08:40:30 -0700, Felix Finch wrote: [...slightly extreme failure modes elided...] For me, the difference is that having extra Fcc copies is nowhere near as bad as not having any. If you're this paranoid, the only real fix is to h

Re: order of sending mail and saving to fcc

I can only say, Erik wrote the answer I wanted to write. @Kevin: The new change sounds very promising. Thank you for that and all your work! @Derek: I've read your mails in this thread, and I'm in no way convinced. HAND Nicolas

Re: order of sending mail and saving to fcc

On Wed, Jun 12, 2019 at 09:31:53AM -0700, Kevin J. McCarthy wrote: > On Tue, Jun 11, 2019 at 05:28:26PM -0500, Derek Martin wrote: > >Obviously you don't need to listen to me > > I do listen to you, Derek. The whole buffer pool migration is a > result of your recurring prods, and I will continue

Re: order of sending mail and saving to fcc

On Tue, Jun 11, 2019 at 05:28:26PM -0500, Derek Martin wrote: Obviously you don't need to listen to me I do listen to you, Derek. The whole buffer pool migration is a result of your recurring prods, and I will continue to work on that, likely through the next couple major releases. I also

Re: order of sending mail and saving to fcc

On Wed, Jun 12, 2019 at 05:20:02PM +1000, Erik Christiansen wrote: > On 11.06.19 12:36, Derek Martin wrote: > > I hesitate to go far as to say that if you think saving the message > > first is the right behavior, you are simply wrong... but I'm > > definitely thinking it. =8^) > > I like your styl

Re: order of sending mail and saving to fcc

On 11.06.19 12:36, Derek Martin wrote: > I hesitate to go far as to say that if you think saving the message > first is the right behavior, you are simply wrong... but I'm > definitely thinking it. =8^) I like your style, Derek. And respect that your use case works for you. What surprises me is th

Re: order of sending mail and saving to fcc

On 11.06.19 13:45, Kevin J. McCarthy wrote: > On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote: > > Something like $fcc_order or $fcc_before_send is possible, > > I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds > $fcc_before_send, default unset. Many grateful t

Re: order of sending mail and saving to fcc

Derek Martin wrote: > On Tue, Jun 11, 2019 at 01:45:18PM -0700, Kevin J. McCarthy wrote: > > On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote: > > I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds > > $fcc_before_send, default unset. > > Obviously you don't need

Re: order of sending mail and saving to fcc

On Tue, Jun 11, 2019 at 01:45:18PM -0700, Kevin J. McCarthy wrote: > On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote: > I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds > $fcc_before_send, default unset. Obviously you don't need to listen to me, but I do want to

Re: order of sending mail and saving to fcc

On Tue, Jun 11, 2019 at 06:43:25AM -0700, Kevin J. McCarthy wrote: Something like $fcc_order or $fcc_before_send is possible, I've pushed a branch up to gitlab, kevin/fcc-before-send. It adds $fcc_before_send, default unset. The caveats to enabling are as mentioned: message manipulation is

Re: order of sending mail and saving to fcc

On Tue, Jun 11, 2019 at 08:11:33PM +0200, Nicolas Rachinsky wrote: > > I hesitate to go far as to say that if you think saving the message > > first is the right behavior, you are simply wrong... but I'm > > definitely thinking it. =8^) > > You might consider it wrong but I do not seem to be the o

Re: order of sending mail and saving to fcc

Hi Mutters, I haven't been following the thread but just to reply to a few points with the names of the posters removed in order to focus on content rather than who said what: > > It's not your > > mail client's job to protect you from every conceibable system > > failure which might cause data

Re: order of sending mail and saving to fcc

* Derek Martin [2019-06-11 12:47 -0500]: > Not only that, but I neglected the fact that if the send fails, the > file your editor produced in order for it to be passed to Mutt will > still be on disk, so you do IN FACT still have a copy of the message. I did just (using my old mutt) set sendmail

Re: order of sending mail and saving to fcc

* Derek Martin [2019-06-11 12:36 -0500]: > On Tue, Jun 11, 2019 at 10:04:25PM +1000, Erik Christiansen wrote: > > In the event that send fails, the local copy is essential for a resend > > attempt. No ifs, no buts, no maybes. I'm at a loss to imagine any > > scenario in which mutt should risk inab

Re: order of sending mail and saving to fcc

* Derek Martin [2019-06-11 12:16 -0500]: > On Mon, Jun 10, 2019 at 11:24:11AM +0200, Nicolas Rachinsky wrote: > > * Jack M [2019-06-04 10:20 -0500]: > > > On Tue, June 4, 2019 5:30 am, Nicolas Rachinsky wrote: > > > > The other one (mail sent, but no local copy) > > > > > > Why would this situat

Re: order of sending mail and saving to fcc

On Tue, Jun 11, 2019 at 12:36:00PM -0500, Derek Martin wrote: > But also, just because the message failed to send, your ideas and the > impetus for writing them down didn't vanish. Your brain is the > back-up. Not only that, but I neglected the fact that if the send fails, the file your editor pr

Re: order of sending mail and saving to fcc

On Tue, Jun 11, 2019 at 10:04:25PM +1000, Erik Christiansen wrote: > In the event that send fails, the local copy is essential for a resend > attempt. No ifs, no buts, no maybes. I'm at a loss to imagine any > scenario in which mutt should risk inability to write that Fcc, through a > hang-up or co

Re: order of sending mail and saving to fcc

On Mon, Jun 10, 2019 at 11:24:11AM +0200, Nicolas Rachinsky wrote: > * Jack M [2019-06-04 10:20 -0500]: > > On Tue, June 4, 2019 5:30 am, Nicolas Rachinsky wrote: > > > The other one (mail sent, but no local copy) > > > > Why would this situation would ever occur? > > A power failure at the wron

Re: order of sending mail and saving to fcc

On Tue, Jun 11, 2019 at 10:04:25PM +1000, Erik Christiansen wrote: If developers insist on the backwards method for themselves, then is an fcc_order config option possible for the benefit of users seeking the old reliability? Something like $fcc_order or $fcc_before_send is possible, but with

Re: order of sending mail and saving to fcc

On 10.06.19 11:20, Nicolas Rachinsky wrote: > * "Kevin J. McCarthy" [2019-06-04 09:44 -0700]: > > On Tue, Jun 04, 2019 at 12:30:59PM +0200, Nicolas Rachinsky wrote: > > > Does anybody know the reason of this change? > > > > The most recent discussion on mutt-dev was > >

Re: order of sending mail and saving to fcc

* Ben Boeckel [2019-06-10 11:56 -0400]: > If you're this paranoid, the only real fix is to have your editor save a > backup somewhere before handing it off to mutt in the first place > anyways. After all, mutt could segfault and lose it before the Fcc! There is one big difference. If mutt crashes

Re: order of sending mail and saving to fcc

On 20190610, Ben Boeckel wrote: On Mon, Jun 10, 2019 at 08:40:30 -0700, Felix Finch wrote: As other(s) have mentioned, power failure, cat jumping on keyboard. I have also had sends hang seemingly forever, and the only way forward is tokill the tmux session. Then I have no Fcc copy. I can root

Re: order of sending mail and saving to fcc

On Mon, Jun 10, 2019 at 08:40:30 -0700, Felix Finch wrote: > As other(s) have mentioned, power failure, cat jumping on keyboard. I > have also had sends hang seemingly forever, and the only way forward > is tokill the tmux session. Then I have no Fcc copy. I can root > around /tmp to find the me

Re: order of sending mail and saving to fcc

On 20190610, Felix Finch wrote: Perhaps a compromise is to Fcc as a draft file first, then send, then move the draft Fcc file to its permanent location. Not so clever with IMAP draft files. It would have to be a special local file, and mutt would have to look for it on start. --

Re: order of sending mail and saving to fcc

On 20190604, Jack M wrote: The other one (mail sent, but no local copy) Why would this situation would ever occur? As other(s) have mentioned, power failure, cat jumping on keyboard. I have also had sends hang seemingly forever, and the only way forward is tokill the tmux session. Then I

Re: order of sending mail and saving to fcc

* Francesco Ariis [2019-06-04 19:52 +0200]: > Hello Grant, > > On Tue, Jun 04, 2019 at 04:46:50PM -, Grant Edwards wrote: > > On 2019-06-04, Jack M wrote: > > > > > The reason (or *a* reason) is that the old way led to the following > > > situation: Fcc first, then try to send, something we

Re: order of sending mail and saving to fcc

* Jack M [2019-06-04 10:20 -0500]: > On Tue, June 4, 2019 5:30 am, Nicolas Rachinsky wrote: > > The other one (mail sent, but no local copy) > > Why would this situation would ever occur? A power failure at the wrong moment. A crash at the wrong moment. ... These things tend to happen only at w

Re: order of sending mail and saving to fcc

* "Kevin J. McCarthy" [2019-06-04 09:44 -0700]: > On Tue, Jun 04, 2019 at 12:30:59PM +0200, Nicolas Rachinsky wrote: > > Does anybody know the reason of this change? > > The most recent discussion on mutt-dev was > . The issue is > contentious

Re: order of sending mail and saving to fcc

On 2019-06-04, Jack M wrote: > On Tue, June 4, 2019 10:46 am, Grant Edwards wrote: >> On 2019-06-04, Jack M wrote: >> >> >>> The reason (or *a* reason) is that the old way led to the following >>> situation: Fcc first, then try to send, something weird happens, but >>> the user has no idea whethe

Re: order of sending mail and saving to fcc

On Tue, June 4, 2019 10:46 am, Grant Edwards wrote: > On 2019-06-04, Jack M wrote: > > >> The reason (or *a* reason) is that the old way led to the following >> situation: Fcc first, then try to send, something weird happens, but >> the user has no idea whether the mail was actually sent or not >

Re: order of sending mail and saving to fcc

Hello Grant, On Tue, Jun 04, 2019 at 04:46:50PM -, Grant Edwards wrote: > On 2019-06-04, Jack M wrote: > > > The reason (or *a* reason) is that the old way led to the following > > situation: Fcc first, then try to send, something weird happens, but > > the user has no idea whether the mail

Re: order of sending mail and saving to fcc

On 2019-06-04, Jack M wrote: > The reason (or *a* reason) is that the old way led to the following > situation: Fcc first, then try to send, something weird happens, but > the user has no idea whether the mail was actually sent or not How could the user not know? If the send fails, mutt prints a

Re: order of sending mail and saving to fcc

On Tue, Jun 04, 2019 at 12:30:59PM +0200, Nicolas Rachinsky wrote: Does anybody know the reason of this change? The most recent discussion on mutt-dev was . The issue is contentious, and there are arguments on both sides. In this case, t

Re: order of sending mail and saving to fcc

On Tue, June 4, 2019 5:30 am, Nicolas Rachinsky wrote: > Hallo, > > > I just noted the entry in UPDATING: > ! Fcc now occurs after sending a message. If the fcc fails, mutt will > prompt to try again, or to try another mailbox. > > This seems to be: > https://gitlab.com/muttmua/mutt/commit/e106487

Re: order of sending mail and saving to fcc

On Tue, Jun 04, 2019 at 12:30:59 +0200, Nicolas Rachinsky wrote: > I considered the previous order (save to fcc, then send the mail) > always the correct one. If anything bad happens (network connectivity > failing (in case of imap), computer crashing,...), it seems to > produce the better outcome.

order of sending mail and saving to fcc

Hallo, I just noted the entry in UPDATING: ! Fcc now occurs after sending a message. If the fcc fails, mutt will prompt to try again, or to try another mailbox. This seems to be: https://gitlab.com/muttmua/mutt/commit/e106487b1f4ebe7128982486accec11ac6f54b5c Does anybody know the reason o

Re: Help with mutt - sending mail with body as html with attachments

Hello again, > Maybe you can set a custom header like “x-change-to-html”, and apply a > hook running an macro if this header is present? > Sounds more native to me. Maybe this is even easier: mutt -e 'set content_type="text/html"' -s 'Subject of your msg' spamreceipi...@server.gov -a attachmen

Re: Help with mutt - sending mail with body as html with attachments

Hello Cary, > 1. Mail whose content is html - I can do this by specify -e "my_hdr > Content-Type: text/html", and formatting the message as a pure html > file, e.g. no extra headers. I’m not entirely sure but I feel that it’s not too ideal to set the Content-Type via a my_hdr setting. Maybe you

Help with mutt - sending mail with body as html with attachments

I am trying to use mutt to send emails with the following characteristics: 1. Mail whose content is html - I can do this by specify -e "my_hdr Content-Type: text/html", and formatting the message as a pure html file, e.g. no extra headers. 2. Mail whose content is html, but must all support atta

Sending mail to mutt-users from gmail ?

Hey, I got all html stuff disabled on gmail webui but when I try post here via gmail my emails are being rejected as being html mail. Anyone know how to avoid that for the times where I don't have access to mutt ? /max

Re: Sending mail foreach

* Dmitry Bogatov on Friday, March 01, 2013 at 16:04:26 +0400 > Is it any convient way or macro to send a bunch of emails > to a list or recepients without letting them know each other? > > Of course, I can leave out To: field and put them all in BCC(to > get filtered) or use mutt from bash script

Re: Sending mail foreach

On Fri, Mar 01, 2013 at 04:04:26PM +0400, Dmitry Bogatov wrote: > Is it any convient way or macro to send a bunch of emails > to a list or recepients without letting them know each other? > > Of course, I can leave out To: field and put them all in BCC(to > get filtered) Lack of the recipient in

Re: Sending mail foreach

* Dmitry Bogatov [03-01-13 07:06]: > Is it any convient way or macro to send a bunch of emails > to a list or recepients without letting them know each other? > > Of course, I can leave out To: field and put them all in BCC(to > get filtered) or use mutt from bash script, but it is not too > con

Re: Sending mail foreach

On 2013–03–01 Dmitry Bogatov wrote: Sorry, I don't have an answer, but an additional question. > Is it any convient way or macro to send a bunch of emails > to a list or recepients without letting them know each other? > > Of course, I can leave out To: field and put them all in BCC(to > get fi

Sending mail foreach

Is it any convient way or macro to send a bunch of emails to a list or recepients without letting them know each other? Of course, I can leave out To: field and put them all in BCC(to get filtered) or use mutt from bash script, but it is not too convient. -- Best regards, Dmitry Bogatov ,

Re: [Solved] Sending Mail to the IMAP Sent Folder

On 28/06/12 08:13, Ian Barton wrote: On 28/06/12 01:53, William Yardley wrote: On Wed, Jun 27, 2012 at 06:46:21PM +0100, Ian Barton wrote: imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX set copy = yes set record = imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX.Sent I have also trie

Re: Sending Mail to the IMAP Sent Folder

On 28/06/12 01:53, William Yardley wrote: On Wed, Jun 27, 2012 at 06:46:21PM +0100, Ian Barton wrote: imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX set copy = yes set record = imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX.Sent I have also tried the following: set record = "+Sent"

Re: Sending Mail to the IMAP Sent Folder

On Wed, Jun 27, 2012 at 06:46:21PM +0100, Ian Barton wrote: > imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX > set copy = yes > set record = imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX.Sent > > I have also tried the following: > > set record = "+Sent" > set record = "Sent" > set re

Sending Mail to the IMAP Sent Folder

I am using Dovecot and am having trouble sending copies of sent mail to my Sent folder. Relevant bits of my .muttrc: imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX set copy = yes set record = imaps://i...@wilkesley.net@mail2.wilkesley.net/INBOX.Sent I have also tried the following: set r

Re: sending mail directly to MX based on To: addr

On 20 Sep 2010, at 16:36, Matthias Apitz wrote: > Do you know if mutt logs somewhere the SMTP dialog with the remote > server? I found nothing in the docs about... Run "mutt -d2". Server chat is then logged in ~/.muttdebug*. Increase the number 2 to larger numbers for more detail. (This assumes

Re: sending mail directly to MX based on To: addr

El día Friday, September 17, 2010 a las 04:44:46PM +0200, Luciano Rocha escribió: > > which put the mail to the local queue and the sendmail queue runner > > later to the SMTP smarterhost (of my ISP). So far so good. In some cases > > I would send the mail directly with SMTP to the destination, b

Re: sending mail directly to MX based on To: addr

El día Friday, September 17, 2010 a las 04:44:46PM +0200, Luciano Rocha escribió: > I use a send-hook: > send-hook . unset smtp_url > send-hook @example.com set smtp_url=smtp://example.com/ Thanks. I have had to update mutt to 1.5.19 but with this it works nicely now. The reason for all this was

Re: sending mail directly to MX based on To: addr

On Fri, Sep 17, 2010 at 04:07:42PM +0200, Matthias Apitz wrote: > > Hello, > > I have configured in ~/.muttrc: > > set sendmail="/usr/sbin/sendmail -oi -oem -f g...@unixarea.de -t" > > which put the mail to the local queue and the sendmail queue runner > later to the SMTP smarterhost (of my ISP

sending mail directly to MX based on To: addr

Hello, I have configured in ~/.muttrc: set sendmail="/usr/sbin/sendmail -oi -oem -f g...@unixarea.de -t" which put the mail to the local queue and the sendmail queue runner later to the SMTP smarterhost (of my ISP). So far so good. In some cases I would send the mail directly with SMTP to the d

Re: Sending mail from the command line

On 21-07-2009, at 13h 27'04", steve wrote about "Re: Sending mail from the command line" > > > > cat myfile.txt | mail -s 'test' m...@example.com > > > No. This will send a mail to m...@example.com (which is alright) but I > want to send a

[SOLVED] Sending mail from the command line

Le 21-07-2009, à 13:37:50 +0200, steve (dl...@bluewin.ch) a écrit : > Lignes : 19 > > > To the OP I only glanced at your attempt without reading the rest of > > your message. Having just previously been reading the ubuntu-user slop I > > also mistakenly assumed I was still reading that list.

Re: Sending mail from the command line

> To the OP I only glanced at your attempt without reading the rest of > your message. Having just previously been reading the ubuntu-user slop I > also mistakenly assumed I was still reading that list. Looking at it > again, I think you need to look at the -a option. > > mutt -s 'test' -a m

Re: Sending mail from the command line

> > But the message is not sent: > > > 0 (null) > > m...@example.com: 0 (null) > > Error sending message, child exited 70 (internal error). > > Could not send the message > > Which MTA? esmtp

Re: Sending mail from the command line

>> I'm trying: >> >> mutt -s "test" m...@example.com < my_file.txt >> >> >> But the message is not sent: >> >> 0 (null) >> m...@example.com: 0 (null) >> Error sending message, child exited 70 (internal error). >> Could not send the message >> >> >> Sending messages works fine from within mutt. >> >

Re: Sending mail from the command line

* steve > But the message is not sent: > 0 (null) > m...@example.com: 0 (null) > Error sending message, child exited 70 (internal error). > Could not send the message Which MTA? Andreas

Re: Sending mail from the command line

On 21-07-2009, at 11h 41'44", steve wrote about "Sending mail from the command line" > Hi list, > > I'm trying: > > mutt -s "test" m...@example.com < my_file.txt > > > But the message is not sent: > > 0 (null) > m...@e

Re: Sending mail from the command line

Andreas Kneib wrote: Useless Use of Cat Award? :) Andreas Or of a reply? To the OP I only glanced at your attempt without reading the rest of your message. Having just previously been reading the ubuntu-user slop I also mistakenly assumed I was still reading that list. Looking at it agai

Re: Sending mail from the command line

* Tim Tebbit > cat myfile.txt | mail -s 'test' m...@example.com Useless Use of Cat Award? :) Andreas

Re: Sending mail from the command line

steve wrote: Hi list, I'm trying: mutt -s "test" m...@example.com < my_file.txt But the message is not sent: 0 (null) m...@example.com: 0 (null) Error sending message, child exited 70 (internal error). Could not send the message Sending messages works fine from within mutt. I guess it's b

Sending mail from the command line

Hi list, I'm trying: mutt -s "test" m...@example.com < my_file.txt But the message is not sent: 0 (null) m...@example.com: 0 (null) Error sending message, child exited 70 (internal error). Could not send the message Sending messages works fine from within mutt. I guess it's because my linux

Re: How can I know if error happens when sending mail?

thanks, your suggestion is applied :) On Wed, 03 Jun 2009, Kyle Wheeler wrote: > On Wednesday, June 3 at 05:20 PM, quoth Chengqi(Lars) Song: > >-code > >lars:~$ less .bin/msmtp-wrap > >#! /bin/bash > > > >msmtp $* > >if [ $? != 0 ] > >then > > gxmessage -wrap -fg red -bg black -d

Re: How can I know if error happens when sending mail?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, June 3 at 05:20 PM, quoth Chengqi(Lars) Song: >-code >lars:~$ less .bin/msmtp-wrap >#! /bin/bash > >msmtp $* >if [ $? != 0 ] >then > gxmessage -wrap -fg red -bg black -default okay -center MSMTP: `tail -1 > ~/.getmail

Re: How can I know if error happens when sending mail?

Hi All, Eventually I solved it by a simple wrapper of msmtp. It looks like this: -code lars:~$ less .bin/msmtp-wrap #! /bin/bash msmtp $* if [ $? != 0 ] then gxmessage -wrap -fg red -bg black -default okay -center MSMTP: `tail -1 ~/.getmail/msmtp.log` fi --

Re: How can I know if error happens when sending mail?

Nicolas [02.Jun.2009 16:09]: * JP Bruns [2009-06-02 10:37 +0200]: Is there anything for console-only systems? Mutt is a great piece of software, but - in my eyes - is lacking this important feature. Would it be possible to take the return-code/-message of the *smtp program and display that o

Re: How can I know if error happens when sending mail?

yeah, the manual says we will be informed, but in fact i tested and didnt see any information about the error. lars On Tue, 02 Jun 2009, Nicolas Rachinsky wrote: > * JP Bruns [2009-06-02 10:37 +0200]: > Is there anything > for console-only > systems? Mutt is a great piece of software, but - i

Re: How can I know if error happens when sending mail?

* JP Bruns [2009-06-02 10:37 +0200]: > Is there anything for console-only systems? Mutt is a great piece of > software, but - in my eyes - is lacking this important feature. Would it be > possible to take the return-code/-message of the *smtp program and display > that on the status-line (or th

Re: sending mail via exchange

Hi, * Chris wrote: > Do I need to use external program like msmtp or is there any > configuration I can do in .muttrc to send mails as well. With 1.5.16 you have the choice. For using built-in SMTP support: http://dev.mutt.org/doc/manual.html#smtp Rocco pgpnxkaZz3zGu.pgp Description: PG

Re: How can I know if error happens when sending mail?

Kyle [02.Jun.2009 04:42]: On Tuesday, June 2 at 10:09 AM, quoth Chengqi(Lars) Song: indeed can not interrupt mutt, but can send a local mail to myself instead i think ... Actually, now that I think about it... you might be able to use xdialog (or something similar) to display an alert mess

Re: sending mail via exchange

On Tue, Jun 2, 2009 at 3:55 PM, Matthias Apitz wrote: > El día Tuesday, June 02, 2009 a las 03:45:14PM +1000, Chris escribió: > >> I have configured Mutt 1.5.16 to check mail via MS Exchange (IMAP). I >> can see all my mail boxes, query for email addresses from Exchange >> etc. However, I cannot s

Re: sending mail via exchange

El día Tuesday, June 02, 2009 a las 03:45:14PM +1000, Chris escribió: > I have configured Mutt 1.5.16 to check mail via MS Exchange (IMAP). I > can see all my mail boxes, query for email addresses from Exchange > etc. However, I cannot send mail from mutt via Exchange. > > Do I need to use extern

sending mail via exchange

I have configured Mutt 1.5.16 to check mail via MS Exchange (IMAP). I can see all my mail boxes, query for email addresses from Exchange etc. However, I cannot send mail from mutt via Exchange. Do I need to use external program like msmtp or is there any configuration I can do in .muttrc to send m

Re: How can I know if error happens when sending mail?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, June 2 at 10:09 AM, quoth Chengqi(Lars) Song: >indeed can not interrupt mutt, but can send a local mail to myself instead i >think ... Actually, now that I think about it... you might be able to use xdialog (or something similar) to d

Re: How can I know if error happens when sending mail?

indeed can not interrupt mutt, but can send a local mail to myself instead i think ... lars On Mon, 01 Jun 2009, Kyle Wheeler wrote: > On Tuesday, June 2 at 12:08 AM, quoth Chengqi(Lars) Song: > > Thanks for the method you provided. In fact I thought of that too. > > But still it's not effici

Re: How can I know if error happens when sending mail?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, June 2 at 12:08 AM, quoth Chengqi(Lars) Song: > Thanks for the method you provided. In fact I thought of that too. > But still it's not efficient to watch that log file everytime after > sending a mail. Logwatch should work but still I

Re: How can I know if error happens when sending mail?

cript, and in the script call pass all parameters to msmtp and watch consequential results? Have anybody done that? Thanks Lars On Mon, 01 Jun 2009, Markus Maria Miedaner wrote: > > > Hi, > > > > I'm using msmtp to send mail. I've set sendmail_wait=-1 in .muttrc to

Re: How can I know if error happens when sending mail?

> Hi, > > I'm using msmtp to send mail. I've set sendmail_wait=-1 in .muttrc to make > sending mail not blocking. But there comes a problem. If any error happens > when sending mail, I will not aware about it. And sometimes it cause trouble > to my work. How can

How can I know if error happens when sending mail?

Hi, I'm using msmtp to send mail. I've set sendmail_wait=-1 in .muttrc to make sending mail not blocking. But there comes a problem. If any error happens when sending mail, I will not aware about it. And sometimes it cause trouble to my work. How can I solve this problem? I need to

Re: error about TLS when sending mail

it works, great! thanks lars On Thu, 30 Apr 2009, Christian Ebert wrote: > * Chengqi(Lars) Song on Thursday, April 30, 2009 at 21:12:12 +0800 > > I always get this message when sending mail: > > > > Apr 30 20:24:19 host=smtp.abc.com tls=on auth=on user=lars > > f

Re: error about TLS when sending mail

but Outlook works well with that server... can mutt ignores that error msg? lars On Thu, 30 Apr 2009, Kyle Wheeler wrote: > On Thursday, April 30 at 09:12 PM, quoth Chengqi(Lars) Song: > >Hi, > > > >I always get this message when sending mail: > > > > Apr 30

Re: error about TLS when sending mail

* Chengqi(Lars) Song on Thursday, April 30, 2009 at 21:12:12 +0800 > I always get this message when sending mail: > > Apr 30 20:24:19 host=smtp.abc.com tls=on auth=on user=lars from=l...@abc.com > recipients=larsgg.tosp...@abc.com errormsg='TLS handshake failed: The Diffie >

Re: error about TLS when sending mail

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday, April 30 at 09:12 PM, quoth Chengqi(Lars) Song: >Hi, > >I always get this message when sending mail: > > Apr 30 20:24:19 host=smtp.abc.com tls=on auth=on user=lars from=l...@abc.com > recipients=larsgg.tosp...@abc

error about TLS when sending mail

Hi, I always get this message when sending mail: Apr 30 20:24:19 host=smtp.abc.com tls=on auth=on user=lars from=l...@abc.com recipients=larsgg.tosp...@abc.com errormsg='TLS handshake failed: The Diffie Hellman prime sent by the server is not acceptable (not long enough).'

Re: Problems with sending mail via Gmail

On 2008-11-26, Niels Rasmussen wrote: > Hi all > > I have a problem with sending mails through Gmail smpt server. > > everytime I'm sending a mail, mutt freezes and writes this below: > > Approving (LOGIN) ...Segmentation fault > > I have this in my .muttrc: > > set smtp_url='smtp://@smtp.gmail.c

Problems with sending mail via Gmail

I think I got it :) This was missing in my .muttrc folder-hook . "my_hdr From: " -- /Niels Registered Linux user #133791 Get counted at http://counter.li.org

Problems with sending mail via Gmail

Hi all I have a problem with sending mails through Gmail smpt server. everytime I'm sending a mail, mutt freezes and writes this below: Approving (LOGIN) ...Segmentation fault I have this in my .muttrc: set smtp_url='smtp://@smtp.gmail.com:587/' set smtp_pass='' What is wrong here ?? /Ni

Re: Blocking when sending mail

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, November 19 at 03:37 PM, quoth Chengqi(Lars) Song: > Mutt is blocked when sending mail. It takes a long time if the mail > is large. Is it possible to send mail in a non-blocking mode? Yes, unless you're using the built-in s

Blocking when sending mail

Hello, Mutt is blocked when sending mail. It takes a long time if the mail is large. Is it possible to send mail in a non-blocking mode? Thanks Lars

Re: Sending mail through IMAP fails

Many thanks. That's worked fine. Kirill Quoting Kyle Wheeler <[EMAIL PROTECTED]>: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thursday, October 16 at 09:32 PM, quoth K C H Mackenzie: > > Hello. I am having trouble setting up Mutt to send mail through IMAP on a > > university serv

  1   2   3   >