Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP

On Tuesday, September 13, 2022 at 14:34:39 +, Nacho via Mutt-users wrote: > In 2022 I find astonishing how much of Microsoft's antispam seems > to rely on lists (addresses, IP blocks…). Leading to annoying > false positives, with rates well higher than Google's. Those "false positives" are

Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP

On 2022-09-12, Mihai Lazarescu wrote: >> Mihai Lazarescu wrote on Mon, 12 Sep 2022 at >> 15:07:37 EDT in : >> >> > Only Microsoft (outlook.com, hotmail.com) seem to filter the whole >> > IP block, but I am too lazy to ask the provider to fix or change >> > provider altogether. [...] > 1. [...]

Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP

> In 2022 I find astonishing how much of Microsoft's antispam seems > to rely on lists (addresses, IP blocks…). Leading to annoying > false positives, with rates well higher than Google's. Those "false positives" are clearly made on purpose to boycott independent mail providers, it doesn't

Re: Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP

lf a year ago. Before, everything was rolling > just fine (for more than 10 yrs). No dead ends of my outgoing mails. > After transferring the domain over to the new hoster, some destinations > did not receive my mails. Either filtered into spam, some got denied > (where I got a nice SMTP error

Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP

share. Deciding that it's OK to not worry about them suggests a very different attitude toward email reliability and interoperability than most people would choose. I never claimed that my specific case is universal: 1. I only have one contact on Hotmail and then I can use Google SMTP. I had my

Re: Is linewrap dead? Now: Self hosted SMTP

(Replying to Mihai, but keeping Bastian's subject-line change...an operation which Mutt is not great at, but better than most...I dunno what to do with In-Reply-To/References: here, tho.) Mihai Lazarescu wrote on Mon, 12 Sep 2022 at 15:07:37 EDT in : > It took some work to set it up, but

Re: [Mutt] Is linewrap dead? Now: Self hosted SMTP

d ends of my outgoing mails. After transferring the domain over to the new hoster, some destinations did not receive my mails. Either filtered into spam, some got denied (where I got a nice SMTP error reply) and some just got silently dropped. This took me some time to figure out with each desti

Re: Using several SMTP servers

On Fri, Aug 12, 2022 at 10:57:41PM +0200, Sébastien Hinderer wrote: > As I see it, the SMTP configuration to use is fully determined by the > from address of the mail to be sent. > > [...] there shouldn't be any need for interactivity. For each outoging > mail, pick up the right SM

Re: Using several SMTP servers

doesn't really have or need much > configuration.) So, if that's what you meant, then yes, it's possible. > > > CASE 2 I am definitely in that case. Thanks for having raised the point, because it was obvious to me but, fortunately for everybody, not everybody is living in my h

Re: Using several SMTP servers

On Fri, Aug 12, 2022 at 08:53:23PM +0200, Daniel Tameling wrote: > On Fri, Aug 12, 2022 at 03:58:02PM +, Sam Kuper wrote: >> - Test/tweak/re-test msmtp until working. (E.g. using Mutt or GNU >> Mailutils's `mail` command to send emails from the command-line, >> with relevant

Re: Using several SMTP servers

On Fri, Aug 12, 2022 at 07:01:52PM +0200, Sébastien Hinderer wrote: > 1. Am I correct that it will be possible, when calling smstp-queue, to > specify which smarthost to use? > > In other words, am I correct that this will let me associate one smart > host (SMTP configuratio

Re: Using several SMTP servers

Daniel Tameling (2022/08/12 20:53 +0200): > On Fri, Aug 12, 2022 at 03:58:02PM +, Sam Kuper wrote: > > - Test/tweak/re-test msmtp until working. (E.g. using Mutt or GNU > > Mailutils's `mail` command to send emails from the command-line, > > with relevant command-line options set so

Re: Using several SMTP servers

On Fri, Aug 12, 2022 at 03:58:02PM +, Sam Kuper wrote: > - Test/tweak/re-test msmtp until working. (E.g. using Mutt or GNU > Mailutils's `mail` command to send emails from the command-line, > with relevant command-line options set so as to ensure that msmtp is > used as the

Re: Using several SMTP servers

Thanks a lot, Sam! Everything you write makes sense. Just one question and one remark, if you don't mind. 1. Am I correct that it will be possible, when calling smstp-queue, to specify which smarthost to use? In other words, am I correct that this will let me associate one smart host (SMTP

Re: Using several SMTP servers

in the queue, if > network is available. Is this understanding correct? `msmtp-queue -r` tells msmtp to try to send the emails from msmtp-queue's queue to your mail provider's SMTP server. In order for that to succeed, you need to have a network connection - otherwise the attempt will time-out and t

Re: Using several SMTP servers

On Thu, Aug 11, 2022 at 06:23:56PM +0200, Sébastien Hinderer wrote: > Dear all, > > Sorry if the question is off-topic, hopefully not completely though. > > I am wondering what's the best way to use different SMTP servers to send > mails, depending on which e-mail account I

Re: Using several SMTP servers

Hello Sam, many thanks for your interesting response! Sam Kuper (2022/08/11 17:43 +): > Consider using msmtp for sending, and msmtp-queue for queueing: > > >https://lists.mutt.org/pipermail/mutt-users/Week-of-Mon-20210208/002485.html My understanding is that, on one side, mutt would call

Re: Using several SMTP servers

On Thu, Aug 11, 2022 at 06:23:56PM +0200, Sébastien Hinderer wrote: > So far I use exim4 to send e-mails but I didn't see a way to specify > which "smarthost" to use to send e-mails e.g. on the sendmail command > line. So, even if I could use mutt send hooks to choose which S

Using several SMTP servers

Dear all, Sorry if the question is off-topic, hopefully not completely though. I am wondering what's the best way to use different SMTP servers to send mails, depending on which e-mail account I am currently using (the From address). I do realise that the two things (the SMTP server used

Re: GMail SMTP: no authenticators available?

On Tue, Jan 26, 2021 at 10:32 -1000, Baron Fujimoto wrote: > - I don't seem to have /usr/lib/libsasl2.2.dylib Me neither actually, but it still works: # ls /usr/lib/libsasl2.2.dylib ls: /usr/lib/libsasl2.2.dylib: No such file or directory # otool -L ~/bin/mutt

Re: GMail SMTP: no authenticators available?

On Fri, 22 Jan 2021, Robin Sommer wrote: On Wed, Jan 20, 2021 at 16:22 -1000, Baron Fujimoto wrote: Our org's email is hosted by Gmail (via GSuite). I had been using neomutt (built from MacPorts) successfully for years. Maybe I can point you in some useful direction: I had exactly this

Re: GMail SMTP: no authenticators available?

On Wed, 20 Jan 2021, Will Yardley wrote: On Wed, Jan 20, 2021 at 04:22:04PM -1000, Baron Fujimoto wrote: The following in my muttrc was used successfully util this problem began: set smtp_url = smtp://u...@example.org@smtp.gmail.com Do you have smtp_authenticators (unset by default) set

Re: GMail SMTP: no authenticators available?

On Fri, Jan 22, 2021 at 13:48 +, I wrote: > so things must have reverted. But it's all still working fine I take that back: the problem persists when linking against MacPorts' libsasl2. Linking against the system's library lets SMTP work for me. Robin -- Robin Sommer * ICSI/LBNL *

Re: GMail SMTP: no authenticators available?

On Wed, Jan 20, 2021 at 16:22 -1000, Baron Fujimoto wrote: > Our og's email is hosted by Gmail (via GSuite). I had been using > neomutt (built from MacPorts) successfully for years. Maybe I can point you in some useful direction: I had exactly this problem with a self-built mutt recently after

Re: GMail SMTP: no authenticators available?

On Wed, Jan 20, 2021 at 08:26:11PM -0800 or thereabouts, Will Yardley wrote: > On Wed, Jan 20, 2021 at 04:22:04PM -1000, Baron Fujimoto wrote: > > The following in my muttrc was used successfully util this problem began: > > set smtp_url = smtp://u...@example.org@smtp.gmail.co

Re: GMail SMTP: no authenticators available?

On Wed, Jan 20, 2021 at 04:22:04PM -1000, Baron Fujimoto wrote: > > The following in my muttrc was used successfully util this problem began: > > set smtp_url = smtp://u...@example.org@smtp.gmail.com Do you have smtp_authenticators (unset by default) set? set smtp_url =

Re: GMail SMTP: no authenticators available?

On Wed, Jan 20, 2021 at 04:22:04PM -1000, Baron Fujimoto wrote: Our org's email is hosted by Gmail (via GSuite). I had been using neomutt (built from MacPorts) successfully for years. Recently though, I can no longer send email successfully using GMail's SMTP servers. I get the error

GMail SMTP: no authenticators available?

Our org's email is hosted by Gmail (via GSuite). I had been using neomutt (built from MacPorts) successfully for years. Recently though, I can no longer send email successfully using GMail's SMTP servers. I get the error, "No authenticators available". IMAP still works fine. T

Re: Gmail SMTP 501-5.5.4

So this is the correct line you must have in your .muttrc file? set imap_user = "usern...@gmail.com" Just substituting your username for "username." Thanks, DR On Thu, Nov 26, 2020 at 8:30 PM Kevin J. McCarthy wrote: > > On Thu, Nov 26, 2020 at 07:14:10PM -0500, D.J.J. Ring, Jr. wrote: >

Re: Gmail SMTP 501-5.5.4

On Thu, Nov 26, 2020 at 07:14:10PM -0500, D.J.J. Ring, Jr. wrote: Does that mean that this line has to be set to just username and not the usern...@gmail.com set imap_user = "usern...@gmail.com" Should be: set imap_user = "username" No, I believe the $imap_user for gmail needs to have the

Re: Gmail SMTP 501-5.5.4

> >I am having is that I can not send emails via Gmal, but I can receive just > >fine. > > Have you manually set hostname in your muttrc? It looks like it is set > to your gmail login. Mutt's SMTP client uses $hostname in the EHLO > command, but gmail doesn't app

Re: Gmail SMTP 501-5.5.4

t;fine. > > Have you manually set hostname in your muttrc? It looks like it is set > to your gmail login. Mutt's SMTP client uses $hostname in the EHLO > command, but gmail doesn't appreciate it being an email address, instead > of your actual hostname. > > -- > Kevin J. McCart

Re: Gmail SMTP 501-5.5.4

is that I can not send emails via Gmal, but I can receive just fine. Have you manually set hostname in your muttrc? It looks like it is set to your gmail login. Mutt's SMTP client uses $hostname in the EHLO command, but gmail doesn't appreciate it being an email address, instead of your actual

Gmail SMTP 501-5.5.4

2020-11-26 17:10:56] 5< 220 smtp.gmail.com ESMTP k31sm3554405qtd.40 - gsmtp [2020-11-26 17:10:56] 5> EHLO usern...@gmail.com [2020-11-26 17:10:56] 5< 501-5.5.4 HELO/EHLO argument "usern...@gmail.com" invalid, closing [2020-11-26 17:10:56] 5< 501-5.5.4 connection. [20

Re: smtp not working

then. Maybe the IMAP GSSAPI handler can be ported over to be used for SMTP too. I'll take a look at that for next cycle... Perhaps you could try an external MTA? msmtp's website seems to mention working with GSSAPI. They use a different SASL library, so you might have better luck. -- Kevin J

Re: smtp not working

me: mycompany\\myuser > > Just a thought - should that be a double backslash or a single > backslash? I may need go back and test this next week. But the current config works for imap, and I have smtp_url="smtp://$imap_u...@server.com:587" in muttrc.

Re: smtp not working

On Thu, Nov 05, 2020 at 01:53:15PM +, isdtor wrote: [2020-11-05 13:35:13] SASL: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server not found in Kerberos database) At this point, I'm just guessing, as I have almost no experience with Kerberos. The

Re: smtp not working

> Try running mutt at debug level 2 and see what it prints. There should be a > message: > smtp_authenticate: Trying method XXX > for each method, and then hopefully something inside the SASL authentication > starting with: > smtp_auth_sasl: > > I don't know what the problem is, but

Re: smtp not working

On Wed, Nov 04, 2020 at 05:48:52PM +, isdtor wrote: The --with-gss is actually only used for IMAP authentication. For SMTP, Mutt's (simple) implementation relies entirely on SASL. Is it possible you don't have the modules installed for SASL's GSSAPI support? If you're on a Debian

Re: smtp not working

> The --with-gss is actually only used for IMAP authentication. For SMTP, > Mutt's (simple) implementation relies entirely on SASL. Is it possible you > don't have the modules installed for SASL's GSSAPI support? > > If you're on a Debian derivative, try installing libsasl2-mod

Re: smtp not working

that the smtp server requires "250-AUTH GSSAPI NTLM", and also, that I had built this mutt without gss. So I rebuilt with gss The --with-gss is actually only used for IMAP authentication. For SMTP, Mutt's (simple) implementation relies entirely on SASL. Is it possible you don't have t

Re: smtp not working

t could be the problem here? I have the same settings configured under > thunderbird, and sending works fine there. I figured out that the smtp server requires "250-AUTH GSSAPI NTLM", and also, that I had built this mutt without gss. So I rebuilt with gss Configure options: '--pre

smtp not working

under thunderbird, and sending works fine there. Thunderbird did complain about server certs twice, once for the incoming and once for the outgoing server, for which I created permanent exceptions. mutt, I think, asked once. Is the problem then that the smtp server cert is missing? And how do I

Re: use-after-free in smtp digest-md5

On Wed, Apr 17, 2019 at 04:29:35PM +0200, Philipp Gesang wrote: this was indeed an issue in cyrus-sasl which thanks to a patch by Simo Sorce is now fixed in master: https://github.com/cyrusimap/cyrus-sasl/commit/ca6c587cc9da51235b125a97e841fa786aaad7ff Thank you Philipp, for taking the

Re: use-after-free in smtp digest-md5

:33AM +0200, Philipp Gesang wrote: > > > > I’ve come across a use after free in sasl calls when > > > > authenticating using digest-md5 against an smtp server: > > > > > > Thanks for the trace. > > > > > > > PS: Bringing this up here because mu

Re: use-after-free in smtp digest-md5

hen > > > authenticating using digest-md5 against an smtp server: > > > > Thanks for the trace. > > > > > PS: Bringing this up here because mutt is what crashes for me. > > > As far as I can see, mutt follows the example code provided > > &

Re: use-after-free in smtp digest-md5

On Mon, Apr 15, 2019 at 06:38:40AM -0700, Kevin J. McCarthy wrote: On Mon, Apr 15, 2019 at 08:59:33AM +0200, Philipp Gesang wrote: I’ve come across a use after free in sasl calls when authenticating using digest-md5 against an smtp server: Thanks for the trace. PS: Bringing this up here

Re: use-after-free in smtp digest-md5

On Mon, Apr 15, 2019 at 08:59:33AM +0200, Philipp Gesang wrote: I’ve come across a use after free in sasl calls when authenticating using digest-md5 against an smtp server: Thanks for the trace. PS: Bringing this up here because mutt is what crashes for me. As far as I can see, mutt

use-after-free in smtp digest-md5

Hi, I’ve come across a use after free in sasl calls when authenticating using digest-md5 against an smtp server: --8<-- free 1 --->8-- #0 free_rc4 (text=text@entry=0x21d3460) at digestmd5.c:1227 #1 0x7f1fa8416b92 in make_client_response

Re: Local mail agent suggestions (gmail -> local postgres -> {local IMAP+SMTP} <-> mutt)?

Hi Ben -- Thanks. I did see it a few days ago (it is well indexed on Google!), but while it would provide good search, it leaves most of the other requirements off the list. Probably I should have also stated one of the other requirements, which is that I'm looking for a single tool which can

Re: Local mail agent suggestions (gmail -> local postgres -> {local IMAP+SMTP} <-> mutt)?

should be able to sync from gmail to the local store. - Provide an SMTP server or sendmail-like command line interface for mutt to use to send mail I'd just use the local mail system. For exanmple, my Mac comes with postfix preinstalled; I've just configured it correctly

Re: Local mail agent suggestions (gmail -> local postgres -> {local IMAP+SMTP} <-> mutt)?

On Mon, Jan 21, 2019 at 17:26:31 -0800, Jonathan Gold wrote: > I currently use the mbox format, fetchmail, procmail, and msmtp, but it > is a bit unwieldy and doesn't give me the SQL search interface I'd like. It isn't postgres, but have you looked at notmuch? It has mail-oriented search tools

Local mail agent suggestions (gmail -> local postgres -> {local IMAP+SMTP} <-> mutt)?

directly, filtering by headers and bodies (attachments not so important) - Provide an IMAP server on localhost to be mutt's interface to the postgres mailstore. - Provide an SMTP server or sendmail-like command line interface for mutt

Re: SMTP error from remote mail server after RCPT TO:

El día viernes, octubre 26, 2018 a las 03:47:03p. m. -0500, Hokan escribió: > This rejection is the result of the "percent hack" implimented on > sendmail, postfix and, perhaps, other mail servers. > > Nothing to do with Mutt. Yes, it's a bit off-topic. And, thanks for the pointer to that

Re: SMTP error from remote mail server after RCPT TO:

ry failed: returning message to sender > > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This is a permanent error. The following address(es) failed: > > jw%leserini-

SMTP error from remote mail server after RCPT TO:

This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: jw%leserini-...@gmx.de host 172.16.28.206 [172.16.28.206] SMTP error from remote mail

cannot send large email (with large attachment) using SMTP directly

I find that sending a empty email with a ~12M attachment using SMTP directly will cause a SMTP session error at the end. Is that a mutt problem or the SMTP server (which is Gmail) problem? Yubin -- Yubin Ruan <http://fastdrivers.org>

Re: Sending SMTP email to lookout -- RESOLVED

, "fe...@crowfix.com" <fe...@crowfix.com> wrote: It was smtp_url. The definition in the mutt manual says smtp[s]://[user[:pass]@]host[:port] and I guess I got it confused with http://user:pass@domain, so had smtp://me:p...@corp.com@smtp.of

Re: Sending SMTP email to lookout -- RESOLVED

It was smtp_url. The definition in the mutt manual says smtp[s]://[user[:pass]@]host[:port] and I guess I got it confused with http://user:pass@domain, so had smtp://me:p...@corp.com@smtp.office365.com:port but it should be smtp://m...@corp.com:p...@smtp.office365.com:port

Re: Sending SMTP email to lookout

need help with is the configuration. If K-9 can talk to > > smtp.office365.com, surely so can (neo)mutt. What am I doing wrong? > > > > I use the following with office 365: > -- > set folder=imaps://%40:$my_pass_@outlook.office365.com > set smtp_url = > &q

Re: Sending SMTP email to lookout

Given the number of typos in your email ("lookout", "Ubunto", "smtp.offic365.com"), are you sure that you have the protocol ("smtp" vs. "smtps"), server, port, & credentials typed properly? -tkc On 2017-10-01 15:35, fe...@crowfix.com wro

Re: Sending SMTP email to lookout

. If K-9 can talk to > smtp.office365.com, surely so can (neo)mutt. What am I doing wrong? > I use the following with office 365: -- set folder=imaps://%40:$my_pass_@outlook.office365.com set smtp_url = "smtp://@:$my_pass_@smtp.office365.com:587" set imap_check_subscribed=yes set imap

Re: Sending SMTP email to lookout

I doubt very much this is a bug in (neo)mutt. I also didn't think there was enough difference in the two for it to matter that I post here. What I need help with is the configuration. If K-9 can talk to smtp.office365.com, surely so can (neo)mutt. What am I doing wrong? On Tue, Oct 03, 2017

Re: Sending SMTP email to lookout

You do realize that you are using NeoMutt, which is a fork of Mutt? Actually, you did paste the correct place to ask for assistance in your message... On 2 Oct 2017, at 0:35, fe...@crowfix.com wrote: To learn more about NeoMutt, visit: http://www.neomutt.org/ If you find a bug in NeoMutt,

Sending SMTP email to lookout

I have K-9 email on my Android phone, and it can send email to outlook just fine. But mutt on my Ubunto 17.?? system cannot send email; it always gets "SASL authentication failed". Here is what K-9 has for its outgoing server: SMTP serversmtp.office365.com

Re: Muttrc example needed POP3/SMTP

On 04.02.17 17:04, sunrise wrote: > > Are there any suggestions for which MTA would be most suitable for > this purpose (sending queued messages on a system that is not online > when composing messages)? They would all handle that, straight out of the box. Mail spooling is a basic MTA function.

Re: Muttrc example needed POP3/SMTP

compatibility interface, so that we old folks >could move over painlessly. But now my muscle memory is Postfix oriented.) > >> I use Postfix and both send and receive mail using SMTP as my desktop >> machine is on all the time. Thus I have no need for POP3/IMAP mail >&

Re: Muttrc example needed POP3/SMTP

Thanks for your input; I will definitely be looking at the possibility of using offlineimap. I am on a dial up connection - does offlineimap handle dropped connections well? Thanks again. On Fri, 3 Feb 2017 21:57:21 + (UTC) Arkadiusz Drabczyk wrote: >On

Re: Muttrc example needed POP3/SMTP

On 2017-02-03, sunrise wrote: > I would like to start using mutt but am somewhat intimidated by all the > possible options > in the muttrc config file. Would someone be willing to provide me with a > basic muttrc I > could use to get started? > > Here is what I'm looking

Re: Muttrc example needed POP3/SMTP

old folks could move over painlessly. But now my muscle memory is Postfix oriented.) > I use Postfix and both send and receive mail using SMTP as my desktop > machine is on all the time. Thus I have no need for POP3/IMAP mail > collection. As my machine is shut down each night, I use fetch

Re: Muttrc example needed POP3/SMTP

aintainer, configuration of exim4 is simple and quick. > ... and if you're on a distribution where Postfix is the standard that's also pretty easy to set up. I personally prefer Postfix from the ease of configuration point of view. I use Postfix and both send and receive mail using SMTP as my desktop

Re: Muttrc example needed POP3/SMTP

On Thu, February 2, 2017 10:37 pm, sunrise wrote: > I already had getmail set up but didn't have msmtp installed. If exim4 is installed and configured, there is no need for msmtp, unless you need the profile feature of msmtp which gives you the ability to send messages through any of a number of

Re: Muttrc example needed POP3/SMTP

quot; and "/etc/exim4/password-client". > One question I still have is: What are the advantages of using getmail > and msmtp versus using mutt's built in POP3 and SMTP capabilities? The author and maintainer of getmail has taken great pains to ensure that getmail4 w

Re: Muttrc example needed POP3/SMTP

) for retrieving messages * SMTP for sending * Mail stored in maildir format in $HOME Using Mutt 1.5.21 Thanks! I think there is an example .muttrc in /etc/mutt -- dale | http://www.dalekelly.org

Re: Muttrc example needed POP3/SMTP

you need more help fire again in the mailing >list and please consider updating the wiki with your use case when >you succeed. Thanks a lot for both replies; I feel I am now several steps closer to getting a working system. I already had getmail set up but didn't have msmtp installed. One question I still have is: What are the advantages of using getmail and msmtp versus using mutt's built in POP3 and SMTP capabilities? Thank you for your time.

Re: Muttrc example needed POP3/SMTP

On Thu, Feb 02, 2017 at 08:44:34PM -0600, sunrise wrote: > I would like to start using mutt but am somewhat intimidated by all the > possible options > in the muttrc config file. Would someone be willing to provide me with a > basic muttrc I > could use to get started? This is what I have: set

Re: Muttrc example needed POP3/SMTP

On Thu, February 2, 2017 8:44 pm, sunrise wrote: > I would like to start using mutt but am somewhat intimidated by all the > possible options in the muttrc config file. Would someone be willing to > provide me with a basic muttrc I could use to get started? That's why they make search engines;

Muttrc example needed POP3/SMTP

I would like to start using mutt but am somewhat intimidated by all the possible options in the muttrc config file. Would someone be willing to provide me with a basic muttrc I could use to get started? Here is what I'm looking for: * POP3 (one provider) for retrieving messages * SMTP

Re: mutt smtp/pop

y send, no message when I use SMTP How do you "directly send" without using SMTP? with the default sending mechanism that came with it before I configured SMTP variables I believe the default is to use the "sendmail" command to submit the message to the local mail delive

Re: mutt smtp/pop

y send, no message when I use SMTP How do you "directly send" without using SMTP? with the default sending mechanism that came with it before I configured SMTP variables I believe the default is to use the "sendmail" command to submit the message to the local mail delive

Re: mutt smtp/pop

On Thu, Jul 28, 2016 at 20:23:49 -0400, dale wrote: > On 07/28/2016 07:39 PM, dale wrote: > >On 07/28/2016 04:10 PM, Grant Edwards wrote: > >>On 2016-07-28, dale <d...@dalekelly.org> wrote: > >> > >>>I get a reply from my ISP when I try to d

Re: mutt smtp/pop

On 07/28/2016 07:39 PM, dale wrote: On 07/28/2016 04:10 PM, Grant Edwards wrote: On 2016-07-28, dale <d...@dalekelly.org> wrote: I get a reply from my ISP when I try to directly send, no message when I use SMTP How do you "directly send" without using SMTP? with the

Re: mutt smtp/pop

On 07/28/2016 04:10 PM, Grant Edwards wrote: On 2016-07-28, dale <d...@dalekelly.org> wrote: I get a reply from my ISP when I try to directly send, no message when I use SMTP How do you "directly send" without using SMTP? with the default sending mechanism that came

Re: mutt smtp/pop

On 2016-07-28, dale <d...@dalekelly.org> wrote: > I get a reply from my ISP when I try to directly send, no message when I > use SMTP How do you "directly send" without using SMTP? -- Grant Edwards grant.b.edwardsY

Re: mutt smtp/pop

On 07/28/2016 01:46 PM, hy...@lactose.homelinux.net wrote: dale writes: my ISP doesn't allow direct email set smtp_url="smtp://d...@dalekelly.org@smtpout.secureserver.net:25" I get the following messages Connecting to smtpout.secureserver.net... Could n

Re: mutt smtp/pop

dale writes: >my ISP doesn't allow direct email >set smtp_url="smtp://d...@dalekelly.org@smtpout.secureserver.net:25" >I get the following messages >Connecting to smtpout.secureserver.net... >Could not connect to smtpout.secureserver.net (Interrupted system call). It's

mutt smtp/pop

I used to use Mutt on Ubuntu from the repository and got it to work except for smtp TLS, my ISP doesn't allow direct email, still doesn't I get a reply mail saying so I am now using Debian GNU/Linux 8 (jessie) 64-bit and Mutt 1.5.23-3 which came installed as I saw in the package manager I

Re: Send mail in background with built-in SMTP client?

El día Saturday, April 16, 2016 a las 03:25:31PM -0400, Xu Wang escribió: > > I understand this config value for the $sendmail proc, as the man page > > also explains. Does this really also affect the built-in SMTP client > > functionality? > > Yes I unders

Re: Send mail in background with built-in SMTP client?

On Fri, Apr 15, 2016 at 1:25 AM, Matthias Apitz <g...@unixarea.de> wrote: > El día Thursday, April 14, 2016 a las 07:59:56PM -0700, Claus Assmann > escribió: > >> On Thu, Apr 14, 2016, Xu Wang wrote: >> >> > I use mutt's built-in SMTP client. I would like to pr

Re: Send mail in background with built-in SMTP client?

El día Thursday, April 14, 2016 a las 07:59:56PM -0700, Claus Assmann escribió: > On Thu, Apr 14, 2016, Xu Wang wrote: > > > I use mutt's built-in SMTP client. I would like to press 'y' and > > immediately be able to move on to my next email without waiting. I > > Did y

Re: Send mail in background with built-in SMTP client?

On Thu, Apr 14, 2016 at 10:59 PM, Claus Assmann <mutt+us...@esmtp.org> wrote: > On Thu, Apr 14, 2016, Xu Wang wrote: > >> I use mutt's built-in SMTP client. I would like to press 'y' and >> immediately be able to move on to my next email without waiting. I > >

Re: Send mail in background with built-in SMTP client?

On Thu, Apr 14, 2016, Xu Wang wrote: > I use mutt's built-in SMTP client. I would like to press 'y' and > immediately be able to move on to my next email without waiting. I Did you check the fine manual? 3.234. sendmail_wait Type: number Default: 0 Specifies the number of seconds t

Send mail in background with built-in SMTP client?

Dear all, I use mutt's built-in SMTP client. I would like to press 'y' and immediately be able to move on to my next email without waiting. I understand why it is important to wait---if the email send failed, then it is important for you to know that. But is it possible to be notified of a failed

Re: How to send a pre-written full email with mutt's built-in smtp

On Sun, Apr 3, 2016 at 9:12 PM, Kevin J. McCarthy wrote: > On Sun, Apr 03, 2016 at 07:38:41PM -0400, Xu Wang wrote: >> Unfortunately, >> mutt -H - < email_file >> does not work when email_file has embedded attachments. To see this >> use mutt to write an email, attach two PDF files,

Re: How to send a pre-written full email with mutt's built-in smtp

On Sun, Apr 3, 2016 at 8:48 PM, Christian Ebert wrote: > * Xu Wang on Sunday, April 03, 2016 at 19:38:41 -0400 >> Unfortunately, >> mutt -H - < email_file >> does not work when email_file has embedded attachments. To see this >> use mutt to write an email, attach two PDF

Re: How to send a pre-written full email with mutt's built-in smtp

* Xu Wang on Sunday, April 03, 2016 at 19:38:41 -0400 > Unfortunately, > mutt -H - < email_file > does not work when email_file has embedded attachments. To see this > use mutt to write an email, attach two PDF files, and then use the > above command on that email file. > > Send the email to

Re: How to send a pre-written full email with mutt's built-in smtp

On Sun, Apr 03, 2016 at 07:38:41PM -0400, Xu Wang wrote: > Unfortunately, > mutt -H - < email_file > does not work when email_file has embedded attachments. To see this > use mutt to write an email, attach two PDF files, and then use the > above command on that email file. > > Send the email to

Re: How to send a pre-written full email with mutt's built-in smtp

Unfortunately, mutt -H - < email_file does not work when email_file has embedded attachments. To see this use mutt to write an email, attach two PDF files, and then use the above command on that email file. Send the email to yourself. You should see that the attachments were not sent correctly.

Re: How to send a pre-written full email with mutt's built-in smtp

2016 at 01:19:12AM -0400, Xu Wang wrote: > >> > > > > > Suppose that I have a full email (i.e. with headers and >> > > > > > everything). >> > > > > > e.g. I want to keep the message ID the same. How can I used mutt's >> >

Re: How to send a pre-written full email with mutt's built-in smtp

ers and everything). > > > > > > e.g. I want to keep the message ID the same. How can I used mutt's > > > > > > build-in smtp to send the email? Basically i want mutt to just send > > > > > > the email that is already written and not change any h

  1   2   3   4   5   6   >