To all who have helped me so far, a huge thank you! I
soon realized that the subject line of this message is incorrect
since pop3 covers only the delivery task and I got that working
a couple of weeks or so ago. The indescribably joyful experience
of being able to successfully authenticate
Quoting Martin G. McCormick (mar...@server1.shellworld.net):
> Paul E Condon writes:
> > I use msmtp, not exim, even though exim comes already installed by
> > Debian. Msmtp has its own tiny config file which can be located at
> > ~/.msmtprc You can put there whatever you need to satisfy you ISP a
Paul E Condon writes:
> I use msmtp, not exim, even though exim comes already installed by
> Debian. Msmtp has its own tiny config file which can be located at
> ~/.msmtprc You can put there whatever you need to satisfy you ISP and
> have no fear of exim mucking about with it. Of course, don't rem
David Wright writes:
A number of very good suggestions
> The other thing you could try is a handcrafted email, which takes
> about 5 minutes, by typing the following into a bash prompt:
>
>
> $ echo -e -n '\0marti...@suddenlink.net\0SECRET' | base64
> aBase64stringIsEmitted=
> $ openssl
Paul E Condon writes:
> I use msmtp, not exim, even though exim comes already installed by
> Debian. Msmtp has its own tiny config file which can be located at
> ~/.msmtprc You can put there whatever you need to satisfy you ISP and
> have no fear of exim mucking about with it. Of course, don't rem
I believe in learning by doing, so I posted an example that one can
actually do. However, private emails show that it's caused a little
confusion. To make it as easy as I could, I wrote the example using
the information posted by the OP, and using the OP's own placeholder,
SECRET, as the password.
Quoting David Wright (deb...@lionunicorn.co.uk):
> Quoting Martin G. McCormick (mar...@server1.shellworld.net):
> > The mainlog file displays the error that
> > smtp.suddenlink.net is reporting
> >
> > 2015-07-11 06:29:26 1ZDsyD-0001Rm-PO ** mar...@shellworld.net R=smarthost
> > T=remote_smtp_sma
On 20150708_2203-0500, Martin G. McCormick wrote:
> I am trying to get a debian squeeze system to pull mail
> from my cable provider's pop3 server. It appears they are not
> doing anything really out of the ordinary but I obviously have
> something set wrong.
>
> Here is a short snippe
Quoting Martin G. McCormick (mar...@server1.shellworld.net):
> David Wright writes:
> > I don't see what the issue is. "People" with different usernames
> > send mail from this system.
>
> Correct. After looking at what I posted, it is confusing. Let's
> try again.
>
> > Do you mean /etc/mailname
On 2015-07-11, Martin G. McCormick wrote:
>
>
> The smarthost sees mar...@suddenlink.net and what it should see
> in the From: line is marti...@suddenlink.net
> Here are all the non-comments from update-exim4.conf.conf
>
Cannot this be defined in /etc/email-addresses?
mar...@suddenlink.net: mart
On Sat 11 Jul 2015 at 07:43:49 -0500, Martin G. McCormick wrote:
> David Wright writes:
> > I don't see what the issue is. "People" with different usernames
> > send mail from this system.
>
> Correct. After looking at what I posted, it is confusing. Let's
> try again.
>
> > Do you mean /etc/mai
On Sat, 11 Jul 2015, Martin G. McCormick wrote:
If I hope to send mail through smtp.suddenlink.net,
it must see marti...@suddenlink.net plus the
password also used to retrieve pop3 mail and the
retrieval does work.
Does your MUA set "From:" to marti...@suddenlink.net,
and also set the envel
On Sat, 11 Jul 2015, David Wright wrote:
dc_smarthost='smtp.suddenlink.net::587'
Syntax is correct. I've not tried that port. Must do
so sometime.
I think we're learning here in this thread to avoid
generalizations, but 587 is known as the "submit"
port. I have had good luck with it.
Th
David Wright writes:
> I don't see what the issue is. "People" with different usernames
> send mail from this system.
Correct. After looking at what I posted, it is confusing. Let's
try again.
> Do you mean /etc/mailname? What's actually in there?
wb5agz.swbell.net
That should never show up on
Quoting Bob Bernstein (poo...@ruptured-duck.com):
> Maybe it's me; I'm not as spry as I used to be, but I am having
> difficulty following you.
Ditto
> On Fri, 10 Jul 2015, Martin G. McCormick wrote:
>
> >dc_smarthost='smtp.suddenlink.net::587'
>
> That looks fine to me, if the syntax for speci
Quoting Martin G. McCormick (mar...@server1.shellworld.net):
> Bob Bernstein writes:
> > what do you put in exim's config as the name of your smarthost?
>
> dc_smarthost='smtp.suddenlink.net::587'
>
> I have figured out the first thing that is wrong but am
> not sure how to fix it. When reg
Maybe it's me; I'm not as spry as I used to be, but I
am having difficulty following you.
On Fri, 10 Jul 2015, Martin G. McCormick wrote:
dc_smarthost='smtp.suddenlink.net::587'
That looks fine to me, if the syntax for specifying a
port is correct for exim (I simply don't know one way
or t
Bob Bernstein writes:
> what do you put in exim's config as the name of your smarthost?
dc_smarthost='smtp.suddenlink.net::587'
I have figured out the first thing that is wrong but am
not sure how to fix it. When registering a user ID on
Suddenlink's email gateway, I had to pick a slightl
Quoting Martin G. McCormick (mar...@server1.shellworld.net):
> Are there flags I can send to exim4 to see what the
> message looks like which will probably tell me which headers are
> wrong? This will make it possible to go through exim4-config
> once again to see what I set wrong since the smtp s
On Fri, 10 Jul 2015, Martin G. McCormick wrote:
The job now is to get the out-bound
authentication to work to the smtp server.
what do you put in exim's config as the name of your
smarthost?
--
I am not a loony. Why should I be tarred with the epithet
'loony' merely because I have a pet
The job now is to get the out-bound authentication to
work to the smtp server. One should use dpkg-configure
exim4-config to set exim to use a smarthost for out-bound
messages and rely on fetchmail for the incoming mail. Most of
this is relatively easy and straight-forward except for one
sm
On Thu, 9 Jul 2015, John D. Hendrickson wrote:
but ALL DAMN DAY every day it got IP attacks
purportedly from china.
It's of course still like that out there, ALL DAMN
DAY, the Wild West, Main St., Dodge City, only it's
mostly (I think) SSH brute force attempts. I show
skeptical friends my l
On Thursday 09 July 2015 16:11:21 Chris Bannister wrote:
> On Thu, Jul 09, 2015 at 08:28:36AM -0500, Martin G. McCormick wrote:
> > Lisi Reisz writes:
> > > As someone else has pointed out, it looks as though your username is
> > > wrong.
> > > Most POP3 mailhosts require the full email address, wi
On Thu, Jul 09, 2015 at 08:28:36AM -0500, Martin G. McCormick wrote:
> Lisi Reisz writes:
> > As someone else has pointed out, it looks as though your username is
> > wrong.
> > Most POP3 mailhosts require the full email address, with the @domain bit.
> >
> > Lisi
>
> This one is no exception. T
On Thu, 9 Jul 2015, Martin G. McCormick wrote:
Lisi Reisz writes:
As someone else has pointed out, it looks as though
your username is wrong.
I don't know whether to feel stupid or joyful.
You get to feel both at the same time. Enjoy!
--
"No matter how big the problem is, you can always
Lisi Reisz writes:
> As someone else has pointed out, it looks as though your username is
> wrong.
> Most POP3 mailhosts require the full email address, with the @domain bit.
>
> Lisi
This one is no exception. Thank you!! I don't know how many
times I have read and re-read the lines in that .fet
On Thursday 09 July 2015 12:54:07 Martin G. McCormick wrote:
> Bob Bernstein writes:
> > Is there a special reason you do not post your .fetchmailrc file?
>
> Yes. This is called a senior moment. It's when you forget to
> include all the relevant information for which I apologize.
>
> Here is
Bob Bernstein writes:
> Is there a special reason you do not post your .fetchmailrc file?
Yes. This is called a senior moment. It's when you forget to
include all the relevant information for which I apologize.
Here is the slightly obfuscated .fetchmailrc file. The
only obscured part is t
"Martin G. McCormick" writes:
> Here is a short snippet from their instructions for
> using pop:
>
>Incoming Mail Server: pop.suddenlink.net
>Incoming mail port: 110
>Incoming mail port (SSL): 995
See the note on
http://help.suddenlink.com/Internet/Pages/EmailandNewsServerName
On Wed, 8 Jul 2015, Martin G. McCormick wrote:
I am trying to get a debian squeeze system to
pull mail from my cable provider's pop3 server.
Is there a special reason you do not post your
.fetchmailrc file?
Or, the output of 'fetchmail --version'?
And, you have given one or two looks at t
I am trying to get a debian squeeze system to pull mail
from my cable provider's pop3 server. It appears they are not
doing anything really out of the ordinary but I obviously have
something set wrong.
Here is a short snippet from their instructions for
using pop:
Incoming Mail
31 matches
Mail list logo
