Fetchmail continues to retrieve my email successfully. Could your clock
possibly be skewed enough to affect TLS negotiation?
--Gregory
On Mon, May 08, 2023 at 01:39:14AM -0700, John Conover wrote:
>
> My fetchmail, (from the repository,) has started timing out with a
> SOCKET error on connection
On Mon, 12 Sep 2022 19:50:01 +0200, Gerard ROBIN wrote:
> Le Mon, Sep 12, 2022 at 09:06:08AM -, Bert Riding a écrit :
>> Date: Mon, 12 Sep 2022 09:06:08 - (UTC)
>> From: Bert Riding
>> To: debian-user@lists.debian.org
>> Subject: Re: fetchmail
>>
>
Le Mon, Sep 12, 2022 at 09:06:08AM -, Bert Riding a écrit :
> Date: Mon, 12 Sep 2022 09:06:08 - (UTC)
> From: Bert Riding
> To: debian-user@lists.debian.org
> Subject: Re: fetchmail
>
> On Sat, 10 Sep 2022 22:50:01 +0200, Gerard ROBIN wrote:
>
> > Hel
On Sat, 10 Sep 2022 22:50:01 +0200, Gerard ROBIN wrote:
> Hello,
> in Bullseye (stable) fetchmail works fine, but in Bookworm (testing) I
> get:
>
> fetchmail: can't accept options while a background fetchmail is running.
> argc = 5, arg list:
> arg 1 = "-k"
> arg 2 = "--ssl"
> arg 3 = "--mda"
>
Le Sun, Sep 11, 2022 at 09:24:27AM -0400, Greg Wooledge a écrit :
> Date: Sun, 11 Sep 2022 09:24:27 -0400
> From: Greg Wooledge
> To: debian-user@lists.debian.org
> Subject: Re: fetchmail
> X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on bendel.debian.org
> X-Spa
On Sun, 11 Sept 2022 at 23:25, Greg Wooledge wrote:
> On Sun, Sep 11, 2022 at 12:14:15PM +0200, Gerard ROBIN wrote:
> > My problem is that I don't know what starts it.
> > Debian Bookworm (and Bullseye too) use systemd.
> Guessing the service name is non-trivial. Sometimes it's the same as
> t
On Sun, Sep 11, 2022 at 12:14:15PM +0200, Gerard ROBIN wrote:
> My problem is that I don't know what starts it.
> [...]
> Debian Bookworm (and Bullseye too) use systemd.
It's too late now, because you already "solved" the problem by purging
and reinstalling the package. (Which is not a bad soluti
Le Sun, Sep 11, 2022 at 06:18:07AM +0200, to...@tuxteam.de a écrit :
> Date: Sun, 11 Sep 2022 06:18:07 +0200
> From: to...@tuxteam.de
> To: debian-user@lists.debian.org
> Subject: Re: fetchmail
>
> On Sat, Sep 10, 2022 at 10:45:23PM +0200, Gerard ROBIN wrote:
> > Hello,
On Sat, Sep 10, 2022 at 10:45:23PM +0200, Gerard ROBIN wrote:
> Hello,
> in Bullseye (stable) fetchmail works fine, but in Bookworm (testing) I
> get:
>
> fetchmail: can't accept options while a background fetchmail is running.
> argc = 5, arg list:
> arg 1 = "-k"
> arg 2 = "--ssl"
> arg 3 = "--md
Le Sat, Sep 10, 2022 at 04:37:40PM -0500, Nate Bargmann a écrit :
> Date: Sat, 10 Sep 2022 16:37:40 -0500
> From: Nate Bargmann
> To: debian-user@lists.debian.org
> Subject: Re: fetchmail
> X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on bendel.debian.org
> X-Spa
* On 2022 10 Sep 16:28 -0500, Gerard ROBIN wrote:
> Hello,
> in Bullseye (stable) fetchmail works fine, but in Bookworm (testing) I
> get:
>
> fetchmail: can't accept options while a background fetchmail is running.
> argc = 5, arg list:
> arg 1 = "-k"
> arg 2 = "--ssl"
> arg 3 = "--mda"
> arg 4 =
On Lu, 06 apr 20, 10:33:36, Pierre Frenkiel wrote:
> On Mon, 6 Apr 2020, Andrei POPESCU wrote:
>
> > Long term you might need a hold or pin for that (my preference would be
> > a pin).
>
>hi Andrei,
>I felt that the description of the pinning process is rather
>confusing, either in th
On Mon, 6 Apr 2020, Andrei POPESCU wrote:
Long term you might need a hold or pin for that (my preference would be
a pin).
hi Andrei,
I felt that the description of the pinning process is rather
confusing, either in the apt-get man or the aptitude man.
Can you tell me what whould be
On Du, 05 apr 20, 19:21:31, Pierre Frenkiel wrote:
> On Sun, 5 Apr 2020, Pierre Frenkiel wrote:
>
> > let them remove getmail if thay are not able to support it.
> > As I'm perfectly happy with the present Debian version,
> > I'll just keep it, disabling my upgrade process, until getmail support
>
On 2020-04-04 21:46, Andrei POPESCU wrote:
On Sb, 04 apr 20, 19:30:05, Pierre Frenkiel wrote:
On Sat, 4 Apr 2020, Andrei POPESCU wrote:
> You have to keep also a Python 2 interpreter for it.
same question: why would it disapear ?
Because it's not supported upstream anymore.
https://legacy
On Sun, 5 Apr 2020, Pierre Frenkiel wrote:
let them remove getmail if thay are not able to support it.
As I'm perfectly happy with the present Debian version,
I'll just keep it, disabling my upgrade process, until getmail support
reappears.
actually, I was too drastic: as "apt-get upgrade" g
On Sun, 5 Apr 2020, songbird wrote:
Celejar wrote:
...
https://marc.info/?l=getmail&m=157365887605305&w=2
let them remove getmail if thay are not able to support it.
As I'm perfectly happy with the present Debian version,
I'll just keep it, disabling my upgrade process, until getmail supp
Celejar wrote:
...
> https://marc.info/?l=getmail&m=157365887605305&w=2
well that didn't happen and as soon as anyone
expressed any interest in carrying patches Osamu
pretty much just said take over the package because
he wasn't interested in it any more. and then the
topic dropped because nobo
On Sat, 4 Apr 2020 06:34:41 -0400
songbird wrote:
> Pierre Frenkiel wrote:
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server
> imap.gmail.com.
> >
> >hi,
> >the fix I found was to abandon fetchmail. I'm using now ge
On Sb, 04 apr 20, 19:30:05, Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, Andrei POPESCU wrote:
>
> > You have to keep also a Python 2 interpreter for it.
>
> same question: why would it disapear ?
Because it's not supported upstream anymore.
https://legacy.python.org/dev/peps/pep-0373/
Debia
songbird wrote:
...
> in my nosing around i've found this:
>
> https://gitlab.com/dkg/getmail/commits/python3
i meant that to be:
https://gitlab.com/dkg/getmail
songbird
Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, Andrei POPESCU wrote:
>
>> You have to keep also a Python 2 interpreter for it.
>
>same question: why would it disapear ?
>
> best regards,
because eventually it stops being packaged or kept up
and gets left behind long enough that nobody cares to
On Sat, 4 Apr 2020, Andrei POPESCU wrote:
You have to keep also a Python 2 interpreter for it.
same question: why would it disapear ?
best regards,
--
Pierre Frenkiel
On Sb, 04 apr 20, 12:44:38, Pierre Frenkiel wrote:
> On Sat, 4 Apr 2020, songbird wrote:
>
> > yes, but don't get too complacent as eventually
> > getmail goes away if nobody ports it to python3.
> >
>thank you for the advice, but I imagine it will not disappear from my disk,
>even if it
On Sat, 4 Apr 2020, songbird wrote:
yes, but don't get too complacent as eventually
getmail goes away if nobody ports it to python3.
thank you for the advice, but I imagine it will not disappear from my disk,
even if it is no more supported.
best regards,
--
Pierre Frenkiel
Pierre Frenkiel wrote:
I have the following problem with fetchmail:
fetchmail: timeout after 300 seconds waiting for server
imap.gmail.com.
>
>hi,
>the fix I found was to abandon fetchmail. I'm using now getmail, which
>works perfectly
>
> best regards,
yes, but do
I have the following problem with fetchmail:
fetchmail: timeout after 300 seconds waiting for server
imap.gmail.com.
hi,
the fix I found was to abandon fetchmail. I'm using now getmail, which
works perfectly
best regards,
--
Pierre Frenkiel
On 3/29/20, to...@tuxteam.de wrote:
> On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
>> hi,
>> I have the following problem with fetchmail:
>> fetchmail: timeout after 300 seconds waiting for server
>> imap.gmail.com.
>> here is my .fetchmailrc
>
> If I followed correctly
On 2020-03-29 13:24, Reco wrote:
On Sun, Mar 29, 2020 at 01:46:12PM +0200, Pierre Frenkiel wrote:
Mike fetchmail, getmail gives a Time Out
OP
did you select "allow non-standard email client" or whatever it is at
gmail ?
use SimpleIMAPSSLReciever ?
[retriever]
type=SimpleIMAPSSLRetriever
se
Please CC the list. And please refrain from top posting.
On Sun, Mar 29, 2020 at 01:46:12PM +0200, Pierre Frenkiel wrote:
> Mike fetchmail, getmail gives a Time Out
Two options left.
> >1) Try using POP3 instead of IMAP.
> >
> >3) Make a forward to your gmx mailbox from gmail.
Reco
Hi.
On Sun, Mar 29, 2020 at 10:06:19AM +0200, Pierre Frenkiel wrote:
> as requested, here is the output of fetchmail -v
So, login's good:
> fetchmail: IMAP> A0002 LOGIN "pierre.frenkiel" *
> fetchmail: IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID
> XLIST CHILDREN X-GM-E
Pierre Frenkiel writes:
> as requested, here is the output of fetchmail -v
> you can see at the end "reading message ...", but I can't find it
>
> please reply pierre.frenk...@gmx.com
>
[...]
> fetchmail: IMAP> A0004 EXPUNGE
> fetchmail: IMAP< A0004 OK Success
> fetchmail: 211 messages for p
On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc
If I followed correctly, you're trying to access gmail at
the "tradition
On 2020-03-29 09:06, Pierre Frenkiel wrote:
as requested, here is the output of fetchmail -v
you can see at the end "reading message ...", but I can't find it
with gmail you have to select "allow non-conforming clients" or
something.
I had problems with fetchmail and gmail ( forget what exactl
Pierre Frenkiel writes:
> poll imap.gmail.com with proto IMAP auth password
It is just side comments. There is alternative software. The name is
getmail[*]. The getmail supports Gmail's label. It is available to
downloading messages from each Gmail's label. Personaly i use getmail
with Gnus. Alw
Cindy Sue Causey writes:
> ..
> While checking trending one more time to see if there were any current
> references, a new trending topic is that Twitter direct messages are
> taking a hit right now. It all seems an understandable, predictable
> social networking side effect in light of our W
On 3/28/20, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server
> imap.gmail.com.
> here is my .fetchmailrc
Poking my nose in to say that Gmail AND Youtube were down in last
couple days. I only know this
Hi.
On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc
fetchmail -v
Reco
On Sat, Mar 28, 2020 at 06:35:04PM +0100, Pierre Frenkiel wrote:
> hi,
> I have the following problem with fetchmail:
> fetchmail: timeout after 300 seconds waiting for server imap.gmail.com.
> here is my .fetchmailrc
>
>
> set logfile "/data/home/frenkiel/log/fetchmail"
> set pidfile "/d
On Sunday 16 June 2019 09:44:02 pm Joe Aquilina wrote:
> On 14/6/19 5:09 pm, Gene Heskett wrote:
> > On Friday 14 June 2019 01:06:16 am Joe Aquilina wrote:
> > On Thursday 13 June 2019 09:58:39 pm Joe Aquilina wrote:
> >
> > Hello all.
> > A colleague has very recently upgraded his
On 14/6/19 5:09 pm, Gene Heskett wrote:
On Friday 14 June 2019 01:06:16 am Joe Aquilina wrote:
On Thursday 13 June 2019 09:58:39 pm Joe Aquilina wrote:
Hello all.
A colleague has very recently upgraded his Debian system at home
from Jessie (not sure which version) to Stretch (9.9) and from
tha
On Friday 14 June 2019 01:06:16 am Joe Aquilina wrote:
> > >> On Thursday 13 June 2019 09:58:39 pm Joe Aquilina wrote:
> > >>
> > >> Hello all.
> > >> A colleague has very recently upgraded his Debian system at home
> > >> from Jessie (not sure which version) to Stretch (9.9) and from
> > >> that
>> On Thursday 13 June 2019 09:58:39 pm Joe Aquilina wrote:
>> Hello all.
>> A colleague has very recently upgraded his Debian system at home from
>> Jessie (not sure which version) to Stretch (9.9) and from that moment,
>> fetchmail has failed to collect emails. I/we are relatively
>> inexperien
On Thursday 13 June 2019 09:58:39 pm Joe Aquilina wrote:
> Hello all.
> A colleague has very recently upgraded his Debian system at home from
> Jessie (not sure which version) to Stretch (9.9) and from that moment,
> fetchmail has failed to collect emails. I/we are relatively
> inexperienced with
* On 2018 19 Nov 02:10 -0600, mick crane wrote:
> fetchmail for me had a problem with the ssl certificate of gmail which keeps
> changing seemingly depending on which server connect to. Probably is fixable
> but was easier to use getmail.
I don't have a gmail account so I haven't run into that. I
On 2018-11-19 00:33, Nate Bargmann wrote:
I installed the Sid version on this Buster installation and it works
just fine. I simply downloaded it and installed it manually. Aptitude
puts it in the Obsolete and Locally Created Packages section. Shrug.
- Nate
fetchmail for me had a problem wit
I installed the Sid version on this Buster installation and it works
just fine. I simply downloaded it and installed it manually. Aptitude
puts it in the Obsolete and Locally Created Packages section. Shrug.
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds.
On Sun, Nov 18, 2018 at 8:43 PM Brian wrote:
> How does Dovecot get into a thread about fetchmail?
Well, a little confusion, a little impatience, and a little panic.
I was using Thunderbird, and I did something to the DCot config, and
email quit working. I'd spent a couple days fighting with th
spool could be quarrantined and if you haven't read most of
that mail you could end up loosing all of it.
On Sun, 18 Nov 2018, Glenn English wrote:
> Date: Sun, 18 Nov 2018 15:27:55
> From: Glenn English
> To: debianUsers
> Subject: Re: fetchmail
> Resent-Date: Sun, 18 Nov
On Sun 18 Nov 2018 at 20:27:55 +, Glenn English wrote:
> Thanks much, all.
>
> Dovecot's config was bent. Working version recovered from backup. Not
> at all sure what was wrong.
How does Dovecot get into a thread about fetchmail? The mind boggles.
> Dovecot, IMHO, is a mixed blessing...
T
Thanks much, all.
Dovecot's config was bent. Working version recovered from backup. Not
at all sure what was wrong.
Dovecot, IMHO, is a mixed blessing...
But I'm going to look into getmail and isync. I didn't know they
existed. Mutt rules, I think.
--
Glenn English
On Sun 18 Nov 2018 at 19:05:48 +, Glenn English wrote:
> It seems that fetchmail doesn't exist in Buster (Buster's apt and
> aptitude say it doesn't exist -- aptitude in Stretch shows a package).
>
> This means I can't use Mutt if my email is in a box on the other side
> of the LAN?
>
> Anyb
> Anybody know: am I wrong somehow; why fetchmail went away; if Buster'd
> be upset with the Stretch package?
Yup - see this bug for details:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768843
You might consider an alternative such as getmail, or isync.
Steve
--
https://steve.fi/
Hi.
On Sun, Nov 18, 2018 at 07:05:48PM +, Glenn English wrote:
> It seems that fetchmail doesn't exist in Buster (Buster's apt and
> aptitude say it doesn't exist -- aptitude in Stretch shows a package).
True. The reason for the removal was #768843, currently fixed in
experimental onl
On Sun, Nov 18, 2018 at 07:05:48PM +, Glenn English wrote:
> It seems that fetchmail doesn't exist in Buster (Buster's apt and
> aptitude say it doesn't exist -- aptitude in Stretch shows a package).
>
According to the package tracker [0], the migration has been held up
about two years becaus
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
2014-11-25 21:34 GMT+01:00 Ron Leach :
> Did the trick. Logs show that fetchmail is
> 1. using opportunistic TLS on pop3, but
> 2. Sometimes times out after receiving a certificate, and then
> 3. Fetchmail declines to use TLS with the *next* user, but
> 4. gmx complains about not using ssl, and fa
On 24/11/2014 21:02, Frédéric Marchal wrote:
The best thing to do when debugging that kind of problem is to have a look at
the content of /etc/init.d/fetchmail, find the actual fetchmail command started
by the script and run the command manually from the shell.
Don't forget to remove the option
Le Monday 24 November 2014 20:27:25, Ron Leach a écrit :
> List, good evening,
>
> I've looked through the man fetchmail pages and I'd like to get some
> extra logging but I can't seem to pass the -vv parameter to fetchmail.
> Fetchmail starts as a daemon, and I can stop it and start it again, b
On Thu, 05 Jun 2014 17:19:17 +0200
basti wrote:
Except if it's a production svr, you should consider
upgrade the branch; Lenny is quite outdated (2k9).
> # fetch mails
>
Post the whole conf, nobody can guess what you wrote
until TCP/IP/BRAIN-2-BRAIN isn't stable.
…
> Some mails with a siz
Hi,
The problem is the password in .fecthmailrc is not the passeword of your
GMAIL messaging.
For GMAIL, fetchmail is an external application, you must generate another
password that used only by fetchmail!
Now, when fetchmail run, after I can't see my email with my client email
(mutt), what I ca
On Tue, Dec 20, 2011 at 10:05:57PM +, Walter Hurry wrote:
> On Tue, 20 Dec 2011 23:26:38 +0200, Andrei Popescu wrote:
>
> > On Ma, 20 dec 11, 17:51:10, Brian wrote:
> >> On Tue 20 Dec 2011 at 18:24:19 +0100, Alex Padoly wrote:
> >>
> >> > How do you do to run fecthmail with gmail with POP3 pr
On Tue, 20 Dec 2011 18:24:19 +0100, Alex Padoly wrote:
> How do you do to run fecthmail with gmail with POP3 protocol, I can't
> it! How do you do to write the file .fetcmailrc. Thanks!
> Regards.
http://en.lmgtfy.com/?q=fetchmail+gmail
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to deb
On 21 December 2011 07:26, Andrei Popescu wrote:
>
> Just something that might not be obvious in Brian's example: the
> username must always be your complete e-mail address.
I have a feeling the fully-qualified address is only required if it's
a Google Apps (Gmail for your domain) account. I cou
On Tue 20 Dec 2011 at 23:26:38 +0200, Andrei Popescu wrote:
> Just something that might not be obvious in Brian's example: the
> username must always be your complete e-mail address.
I just have the username. Tried it with justfo...@gmail.com and that
worked too.
--
To UNSUBSCRIBE, email to d
On Tue, 20 Dec 2011 23:26:38 +0200, Andrei Popescu wrote:
> On Ma, 20 dec 11, 17:51:10, Brian wrote:
>> On Tue 20 Dec 2011 at 18:24:19 +0100, Alex Padoly wrote:
>>
>> > How do you do to run fecthmail with gmail with POP3 protocol, I can't
>> > it!
>> > How do you do to write the file .fetcmailrc.
On Ma, 20 dec 11, 17:51:10, Brian wrote:
> On Tue 20 Dec 2011 at 18:24:19 +0100, Alex Padoly wrote:
>
> > How do you do to run fecthmail with gmail with POP3 protocol, I can't it!
> > How do you do to write the file .fetcmailrc.
>
> This what I have as part of my ~/.fetchmailrc
>
> poll pop.
On Tue 20 Dec 2011 at 18:24:19 +0100, Alex Padoly wrote:
> How do you do to run fecthmail with gmail with POP3 protocol, I can't it!
> How do you do to write the file .fetcmailrc.
This what I have as part of my ~/.fetchmailrc
poll pop.googlemail.com
protopop3
service 995
user justfo
On Fri, 28 Oct 2011 08:19:46 +0200, Johann Spies wrote:
> With the following fetchmail config:
>
> poll protocol imap:
>no dns
> # port 993
>user johann.sp...@alterit.co.za js here password "xxx"
> # ssl
> # sslcertck# Check the certificates #
> From: jsp...@sun.ac.za
[..]
> fetchmail: Server certificate verification error: self signed certificate
> fetchmail: This means that the root signing certificate (issued for
> /C=US/ST=Someprovince/L=Sometown/O=none/OU=none/CN=localhost/emailAddress=webaster@localhost)
> is not in the trusted
Johann Spies wrote:
> I get this error message:
> fetchmail: Server certificate verification error: self signed certificate
> fetchmail: This means that the root signing certificate (issued for
> /C=US/ST=Someprovince/L=Sometown/O=none/OU=none/CN=localhost/emailAddress=webaster@localhost)
> is n
1 - 100 of 1077 matches
Mail list logo
