On Sat, 18 Jul 2015, Martin G. McCormick wrote:
Just the same, you caught me on one thing. the full
user name is the full email address and I was just
using martin.m.
Full disclosure: that wasn't me. It seems an admirable
young fellow name of Curt brought that to your
attention.
--
I am
On Sunday 19 July 2015 00:45:02 David Wright wrote:
> Quoting Lisi Reisz (lisi.re...@gmail.com):
> > On Saturday 18 July 2015 13:13:56 Martin G. McCormick wrote:
> > > domain = localhost
> >
> > I'm sleepy and probably not following very well, but should this really
> > be localhost?
>
> This was p
Quoting Lisi Reisz (lisi.re...@gmail.com):
> On Saturday 18 July 2015 13:13:56 Martin G. McCormick wrote:
> > domain = localhost
>
> I'm sleepy and probably not following very well, but should this really be
> localhost?
This was passed to the ehlo command where it passed muster:
<-- 220 txofep
On Saturday 18 July 2015 13:13:56 Martin G. McCormick wrote:
> domain = localhost
I'm sleepy and probably not following very well, but should this really be
localhost?
Lisi
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
Quoting Martin G. McCormick (mar...@server1.shellworld.net):
> David Wright writes:
> > > Supported authentication methods:
> > > PLAIN LOGIN
> >
> > I see no encryption here. I think this is why it is telling you that
> > it "cannot use a secure authentication method". I wrote "Yo
David Wright writes:
> > Supported authentication methods:
> > PLAIN LOGIN
>
> I see no encryption here. I think this is why it is telling you that
> it "cannot use a secure authentication method". I wrote "You might
> want to check out port 587 but I think you'll be disappointed"
Curt writes:
> You don't seem to be following the instructions here:
After a good night's sleep, I notice that too. I fixed
it and now there are only moving parts, one of which is
broken instead of 1.:-)
Unfortunately, authentication is loaded with these
series-connected
Bob Bernstein writes:
> At some point in this process try using your POP credentials (username
> martin, password martin's pop password) when trying to send. Y'know, when
> suddenlink told you that 'martin' had been already taken as a username for
> smtp, of course it had, by YOU, for your POP acco
On 2015-07-18, Martin G. McCormick wrote:
> The fun never ends. I installed msmtp and as near as I can tell
> it works as advertised. My SMTP smarthost at
> Suddenlink.net presents the following banner which nicely
> explains what one needs to do to get real work done. I've had a
> little trouble
On Sat, 18 Jul 2015, Bob Bernstein wrote:
Then, if you have success you will at least know you
are using the correct credentials (username,
password) for your smtp server, which assurance you,
and the rest of us, are currently lacking.
At some point in this process try using your POP
creden
I almost forgot:
http://manpages.ubuntu.com/manpages/precise/en/man1/msmtp.1.html
--
I am not a loony. Why should I be tarred with the epithet
'loony' merely because I have a pet halibut? I've heard
tell that Sir Gerald Nabarro has a pet prawn called Simon
- you wouldn't call him a loony!
-
On Fri, 17 Jul 2015, Martin G. McCormick wrote:
# Set a default account
account default
auth on
from marti...@suddenlink.net
protocol smtp
port 587
Believe it or not, this is the closest I have
gotten to making anything work.
Above, where it says 'auth on' make that say
auth off
Then fir
Quoting Martin G. McCormick (mar...@server1.shellworld.net):
> The fun never ends. I installed msmtp and as near as I can tell
> it works as advertised. My SMTP smarthost at
> Suddenlink.net presents the following banner which nicely
> explains what one needs to do to get real work done. I've had
13 matches
Mail list logo
