On Thu, Apr 29, 2021 at 01:27:07PM +0100, Eric S Fraga wrote:
> On Thursday, 29 Apr 2021 at 14:21, to...@tuxteam.de wrote:
> > That means you've to carry a funny dongle with you all the time?
> > Or is the "second factor" that oh-so-secure "smart" phone?
>
> Three choices for second factor:
>
>
but also need to relay
authentication to the company's server.
I would like to use IMAP to access email in order to
circumvent Outlook, but AFAIK there is no way for fetchmail
or other command line tools to authenticate via web page and
use the IMAP Server then (Thunderbird is able to do this but
I
On Thu, Apr 29, 2021 at 01:11:08PM +0100, Eric S Fraga wrote:
> Dystopian is right. Our organization, using O365, has moved to
> "multi-factor authentication" without consultation and I can no longer
> use gnus, for instance. Absolutely horrible.
That means you've to carry a funny dongle with
Dystopian is right. Our organization, using O365, has moved to
"multi-factor authentication" without consultation and I can no longer
use gnus, for instance. Absolutely horrible.
--
Eric S Fraga via Emacs 28.0.50 & org 9.4.5 on Debian bullseye/sid
es. Especially this
> 3D authentication is not likely to be implemented in the opensource
> software and non of it works for me.
Yes. Half-a-life ago, while in dystopian Bigcorp environment, I had
to bribe Windows admins to keep up Outlook's IMAP with... NTLM auth.
Fetchmail worked fine [1] with
Kushal Kumaran wrote:
> I think IMAP should work regardless. My workplace uses federated
> authentication, and davmail works fine for me.
I think it depends how it is setup and what policy applies. Especially this
3D authentication is not likely to be implemented in the opensource
software and
s server.
>
> I would like to use IMAP to access email in order to
> circumvent Outlook, but AFAIK there is no way for fetchmail
> or other command line tools to authenticate via web page and
> use the IMAP Server then (Thunderbird is able to do this but
> I don't want to use Th
for fetchmail
or other command line tools to authenticate via web page and
use the IMAP Server then (Thunderbird is able to do this but
I don't want to use Thunderbird).
I hoped davmail would be able to do that but I have no clue
how to tell davmail to authenticate in this way. AFAIK the
only way
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
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
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.
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"
On Sun, 5 Apr 2020, songbird wrote:
Celejar wrote:
...
https://marc.info/?l=getmail=157365887605305=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 support
Celejar wrote:
...
> https://marc.info/?l=getmail=157365887605305=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 nobody
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,
&g
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/
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
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
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
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
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=SimpleIMAPSS
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
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
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
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
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: starting fetchmail 6.4.0.beta4 daemon
fetchmail: 6.4.0.beta4 querying imap.gmail.com (protocol IMAP) at Sun 29 Mar
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.
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
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 da
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/lo
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 "/data/home/frenkiel/.fetchmail.pid"
set postmaster "f
;> 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
> >>>
that moment, fetchmail has failed to collect emails. I/we are
relatively inexperienced with diagnosing & fixing such problems
and are looking for any advice people here may be able to give us
to overcome this problem. When fetchmail polls the email server,
we get the following error message:
Ju
om 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 diagnosing & fixing such problems
> > >> and are looking for any advice people here may be a
>> 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 colle
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
>
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 diagnosing & fixing such problems and are looking
for any ad
* 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 ha
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
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 fight
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 2018 20:2
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
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
> 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
experi
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
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?
Anybody know: am I wrong somehow; why fetchmail went away; if Buster'd
Bonsoir,
Je ne comprends pas fetchmail voit un message de mon dossier spam mais ne le
rapatrie pas
1 message (1 seen) for.
(folder INBOX.Spam).
Le fichier .fetchmailrc contient pourtant l'option ''nokeep''.
Merci pour vos explications
Bonjour,
Fetchmail semble se connecter au smtp local avant de rapatrier les email.
Visiblement sur ma machine, il n'y arrive pas, cela est du à quoi, je pensais
tout d'abord que le problème était distant
mais je crois que c'est local:
voila ce qu'indique fetchmail:
fetchmail: Erreur de
Hi
Independent of our recent issues, we've had a longstanding problem with
fetchmail.
from /var/log/syslog:
"Warning: the connection is insecure, continuing anyways. (Better use
--sslcertck!)"
It's something we've tried to resolve from time to time but gave up in
frustrati
bonjour,
je suis confronté à un problème de backscatter (rétrodiffusion) : j'ai
un fetchmail qui tourne sur un serveur secondaire, délivre les messages
à un exim local qui les route vers un serveur principal où se trouve
l'antispam, je précise que le port 25 de ce serveur secondaire n'est
pas
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
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 remove
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 and
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 remove
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
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 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 specifying a
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.
The
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
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 the
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/mailname?
On 2015-07-11, Martin G. McCormick mar...@server1.shellworld.net 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?
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? What's
from their instructions for
using pop:
Incoming Mail Server: pop.suddenlink.net
Incoming mail port: 110
Incoming mail port (SSL): 995
end of snippet
It all starts out OK:
fetchmail: 6.3.18 querying pop.suddenlink.net (protocol POP3) at Wed Jul 8
21:23:25 2015: poll
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_smarthost:
.
which I ignore as it appears to have no effect both at home and
in motels etc.
mail sent by smarthost; received via SMTP or fetchmail (sets
dc_eximconfig_configtype)
foo (my hostname, sets /etc/mailname)
smtp.xxx.xxx.xxx::25025;smtp.yyy.yyy (smarthosts, sets dc_smarthost)
yes (hide local mailname
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
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
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
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
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
a fly in the ointment:
tal% less ../.fetchmailrc
poll pop3.slingshot.co.nz with protocol pop3
user cbannister
password
which I call with an alias 'fm':
alias fm='fetchmail -e 50 -m /usr/bin/maildrop'
Maybe the clue is in the phrase '... *most* POP3 mailhosts ...' shrug
anyway, just
squawks. I don't know whether to feel stupid
or joyful.
Just to throw a fly in the ointment:
tal% less ../.fetchmailrc
poll pop3.slingshot.co.nz with protocol pop3
user cbannister
password
which I call with an alias 'fm':
alias fm='fetchmail -e 50 -m /usr/bin/maildrop
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
is the password.
#./fetchmailrc for martin
# This file must be chmod 0600, owner fetchmail
# set polling time (10 minutes)
#
set daemon 600
set no bouncemail
defaults:
mda '/usr/bin/procmail'
antispam -1
batchlimit 0
#server settings
#poll suddenlink.net with protocol pop3
poll pop.suddenlink.net
is the slightly obfuscated .fetchmailrc file. The
only obscured part is the password.
#./fetchmailrc for martin
# This file must be chmod 0600, owner fetchmail
# set polling time (10 minutes)
#
set daemon 600
set no bouncemail
defaults:
mda '/usr/bin/procmail'
antispam -1
batchlimit 0
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
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
Mail Server: pop.suddenlink.net
Incoming mail port: 110
Incoming mail port (SSL): 995
end of snippet
It all starts out OK:
fetchmail: 6.3.18 querying pop.suddenlink.net (protocol POP3) at Wed Jul 8
21:23:25 2015: poll started
Trying to connect to 208.180.40.196/110...connected
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
/EmailandNewsServerNames.aspx :
Note:Username: your full email address, including the @domain.net at
the end (i.e. @suddenlink.net)
fetchmail: 6.3.18 querying pop.suddenlink.net (protocol POP3) at Wed Jul 8
21:23:25 2015: poll started
Trying to connect to 208.180.40.196/110...connected
On 26/11/2014 07:50, Frédéric Marchal wrote:
Fetchmail certainly uses the system ssl library and SSLv3 was recently
disabled system wide for security reasons (see the poodle attack).
[snip]
You'll have to investigate a bit but my theory is that fetchmail is
requesting SSLv3. As it is disabled
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
2014-11-25 21:34 GMT+01:00 Ron Leach ronle...@tesco.net:
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
List, good evening,
We use Fetchmail to collect email from various addresses and
providers. The incoming mail is passed to Exim for delivery to
mailboxes, and served to local MUAs on the network using IMAP provided
by Dovecot. We've had this architecture in place since Debian Etch
(D4
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
necesito que el fetchmail no me verifique el dns al descargar los correos.
me da este error:
fallo en la resolución de nombres buscando «citma.fica.inf.cu» durante
la consulta de 169.158.143.227.
donde 169.158.143.227 es mi ISP, correo y dns a la vez.
gracias de ante mano.
--
To UNSUBSCRIBE
El Thu, 06 Nov 2014 07:57:29 -0500, José Betancourt Mondeja escribió:
necesito que el fetchmail no me verifique el dns al descargar los
correos.
me da este error:
fallo en la resolución de nombres buscando «citma.fica.inf.cu» durante
la consulta de 169.158.143.227.
donde 169.158.143.227
no dns
yo uso ese parametro en mi config de fecthmail
El 06/11/2014 9:38, Camaleón escribió:
El Thu, 06 Nov 2014 07:57:29 -0500, José Betancourt Mondeja escribió:
necesito que el fetchmail no me verifique el dns al descargar los
correos.
me da este error:
fallo en la resolución de nombres
El Thu, 06 Nov 2014 13:36:22 -0500, Ariel Alvarez escribió:
(corrijo el top-posting)
El 06/11/2014 9:38, Camaleón escribió:
El Thu, 06 Nov 2014 07:57:29 -0500, José Betancourt Mondeja escribió:
necesito que el fetchmail no me verifique el dns al descargar los
correos.
me da este error
101 - 200 of 4612 matches
Mail list logo
