fetchmail-users — User questions and discussion

Re: [Fetchmail-users] IMAP IDLE works only somtiemes

[Matthias A. <mat...@gm...>]

Am 28.11.2016 um 14:18 schrieb Volker Wysk:
> Hello!
>
> I've set up fetchmail to fetch my mail via IMAP IDLE. This had worked.
>
> But since a fews days, this works only sometimes. Sometimes, mail, which I can 
> see in the webmail interface of my webhoster, stays there, and doesn't get 
> collected. When I restart the fetchmail service, the mail does get fetched.
>
> I have set the "fetchall" parameter, that's not the reason.
>
> Anyone with similar problems? Should I abstain from IMAP IDLE?
<http://www.fetchmail.info/fetchmail-FAQ.html#G3>

Re: [Fetchmail-users] IMAP IDLE works only somtiemes

[Volker W. <po...@vo...>]

This is my fetchmailrc:

set postmaster "v"
set bouncemail
set no spambounce
set properties ""
#set syslog
set daemon 300
set logfile "/var/log/fetchmail-post.log"

poll volker-wysk.de with proto IMAP
       user 'xxx' there with password 'xxx' is 'v' here 
       ssl sslfingerprint 'xxx'
       smtphost /var/run/dovecot/lmtp lmtp idle
       fetchall

[Fetchmail-users] IMAP IDLE works only somtiemes

[Volker W. <po...@vo...>]

Hello!

I've set up fetchmail to fetch my mail via IMAP IDLE. This had worked.

But since a fews days, this works only sometimes. Sometimes, mail, which I can 
see in the webmail interface of my webhoster, stays there, and doesn't get 
collected. When I restart the fetchmail service, the mail does get fetched.

I have set the "fetchall" parameter, that's not the reason.

Anyone with similar problems? Should I abstain from IMAP IDLE?

Bye
V.W.

Re: [Fetchmail-users] How to install and configure on centos server

[Matthias A. <mat...@gm...>]

Am 04.11.2016 um 10:09 schrieb Chandran Manikandan:
> Dear Friends,
> I have installed qmailtoaster in remote and local server with the same
> domain.
> I have configured the users in both server.
> How do i install fetchmail in local server and how to configure it.
> I want to fetch all the emails from remote server to local server.
> We want to keep all email accounts and email messages in both server.
> Could anyone help me.
>
Fetchmail is a one-way downloader, and if the server you are fetching
from supports POP3 and stable UIDL, you're set, please ask more precise
questions.

[Fetchmail-users] How to install and configure on centos server

[Chandran M. <tec...@gm...>]

Dear Friends,
I have installed qmailtoaster in remote and local server with the same
domain.
I have configured the users in both server.
How do i install fetchmail in local server and how to configure it.
I want to fetch all the emails from remote server to local server.
We want to keep all email accounts and email messages in both server.
Could anyone help me.

-- 
*Thanks,*
*Manikandan.C*
*System Administrator*

[Fetchmail-users] Fetchmail Install and configure on centos server

[Chandran M. <tec...@gm...>]

Hi Friends,

I have running Qmailtoaster on my centos 6.6..
I would like to install and configure fetchmail on other machine.
I want to copy all the email accounts and emails in both server.
Could anyone help me.
Is it work for fetch email.
Why should i need this feature because some of the users removed email from
current server and management required all their transaction. It's like
mirror.
Or please guide me is there any option available.


-- 
*Thanks,*
*Manikandan.C*
*System Administrator*

Re: [Fetchmail-users] using logrotate to rotate the fetchmail log

[Chris <cpo...@em...>]

On Sun, 2016-09-25 at 11:32 +0200, Carlos E. R. wrote:
> On 2016-09-25 04:08, Chris wrote:
> > 
> > On Sun, 2016-09-25 at 03:24 +0200, Carlos E. R. wrote:
> 
> > 
> > I can just have procmail log to syslog also. I was attempting to
> > use
> > webmins logrotate setup yesterday but couldn't get it to where it
> > would
> > kill the fetchmail process, rotate and recreate the log then
> > restart
> > fetchmail.
> If you use "logrotate" it is quite simple, actually. It is a
> directory
> "/etc/logrotate.d" with config files. Take the one for apache, it
> contains entries for each file it handles:
> 
> var/log/apache2/access_log {
>     compress
>     dateext
>     maxage 365
>     rotate 99
>     size=+4096k
>     notifempty
>     missingok
>     create 644 root root
>     postrotate
>      /usr/bin/systemctl reload apache2.service
>     endscript
> }
> 
> The "postrotate" is what it does with the process. I see one file for
> fetchmail, too:
> 
> var/log/fetchmail {
>     compress
>     dateext
>     maxage 365
>     rotate 99
>     size=+1024k
>     notifempty
>     missingok
>     copytruncate
>     create 0600 fetchmail root
> }
> 
> It doesn't kill the service. Instead it copies and trunctates the
> log.
> 
> This is in openSUSE, other distros may vary.
> 
Thanks for that Carlos, I'll put that in my /etc/logrotate.d folder and
see if it works.

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
07:45:05 up 1 day, 9:39, 1 user, load average: 1.75, 1.61, 1.03
Ubuntu 16.04.1 LTS, kernel 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016

Re: [Fetchmail-users] using logrotate to rotate the fetchmail log

[Carlos E. R. <rob...@te...>]

On 2016-09-25 04:08, Chris wrote:
> On Sun, 2016-09-25 at 03:24 +0200, Carlos E. R. wrote:


> I can just have procmail log to syslog also. I was attempting to use
> webmins logrotate setup yesterday but couldn't get it to where it would
> kill the fetchmail process, rotate and recreate the log then restart
> fetchmail.

If you use "logrotate" it is quite simple, actually. It is a directory
"/etc/logrotate.d" with config files. Take the one for apache, it
contains entries for each file it handles:

var/log/apache2/access_log {
    compress
    dateext
    maxage 365
    rotate 99
    size=+4096k
    notifempty
    missingok
    create 644 root root
    postrotate
     /usr/bin/systemctl reload apache2.service
    endscript
}

The "postrotate" is what it does with the process. I see one file for
fetchmail, too:

var/log/fetchmail {
    compress
    dateext
    maxage 365
    rotate 99
    size=+1024k
    notifempty
    missingok
    copytruncate
    create 0600 fetchmail root
}

It doesn't kill the service. Instead it copies and trunctates the log.

This is in openSUSE, other distros may vary.

-- 
Cheers / Saludos,

		Carlos E. R.
		(from 13.1 x86_64 "Bottle" at Telcontar)

Re: [Fetchmail-users] using logrotate to rotate the fetchmail log

[Chris <cpo...@em...>]

On Sun, 2016-09-25 at 03:24 +0200, Carlos E. R. wrote:
> On 2016-09-25 03:19, Chris wrote:
> > 
> > On Sun, 2016-09-25 at 02:53 +0200, Carlos E. R. wrote:
> > > 
> > > On 2016-09-25 02:28, Chris wrote:
> > > > 
> > > > 
> > > > Is there a way that this can be done somehow? 
> > > I have fetchmail log into syslog, and then handle rotation in the
> > > usual manner.
> > > 
> > That makes sense, I hadn't thought of doing it that way, thanks.
> Welcome.
> 
> It goes into the same file as "mail entries", so that I can track a
> single mail coming from fetchmail, into postfix, then procmail,
> dovecot... it is not trivial but can be done.
> 
I can just have procmail log to syslog also. I was attempting to use
webmins logrotate setup yesterday but couldn't get it to where it would
kill the fetchmail process, rotate and recreate the log then restart
fetchmail.
-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
21:03:01 up 22:57, 1 user, load average: 0.18, 0.32, 0.32
Ubuntu 16.04.1 LTS, kernel 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016

Re: [Fetchmail-users] using logrotate to rotate the fetchmail log

[Carlos E. R. <rob...@te...>]

On 2016-09-25 03:19, Chris wrote:
> On Sun, 2016-09-25 at 02:53 +0200, Carlos E. R. wrote:
>> On 2016-09-25 02:28, Chris wrote:
>>>
>>> Is there a way that this can be done somehow? 
>> I have fetchmail log into syslog, and then handle rotation in the
>> usual manner.
>>
> That makes sense, I hadn't thought of doing it that way, thanks.

Welcome.

It goes into the same file as "mail entries", so that I can track a
single mail coming from fetchmail, into postfix, then procmail,
dovecot... it is not trivial but can be done.

-- 
Cheers / Saludos,

		Carlos E. R.
		(from 13.1 x86_64 "Bottle" at Telcontar)

Re: [Fetchmail-users] using logrotate to rotate the fetchmail log

[Chris <cpo...@em...>]

On Sun, 2016-09-25 at 02:53 +0200, Carlos E. R. wrote:
> On 2016-09-25 02:28, Chris wrote:
> > 
> > Is there a way that this can be done somehow? 
> I have fetchmail log into syslog, and then handle rotation in the
> usual
> manner.
> 
That makes sense, I hadn't thought of doing it that way, thanks.

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
20:14:01 up 22:08, 1 user, load average: 0.41, 0.25, 0.27
Ubuntu 16.04.1 LTS, kernel 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016

Re: [Fetchmail-users] using logrotate to rotate the fetchmail log

[Carlos E. R. <rob...@te...>]

On 2016-09-25 02:28, Chris wrote:
> Is there a way that this can be done somehow? 

I have fetchmail log into syslog, and then handle rotation in the usual
manner.

-- 
Cheers / Saludos,

		Carlos E. R.
		(from 13.1 x86_64 "Bottle" at Telcontar)

[Fetchmail-users] using logrotate to rotate the fetchmail log

[Chris <cpo...@em...>]

Is there a way that this can be done somehow? 

Thanks
Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
19:25:03 up 21:19, 1 user, load average: 0.68, 0.34, 0.22
Ubuntu 16.04.1 LTS, kernel 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016

Re: [Fetchmail-users] Yahoo and "Allow apps that use less secure sign in"

[Matthias A. <mat...@gm...>]

Am 22.09.2016 um 16:27 schrieb Jerry:
> I recently activated the "Allow apps that use less secure sign in"
> option on my Yahoo account. Fetchmail immediately was unable to access
> my Yahoo account from that point on. I was forced to turn the option
> off.
>
> Is this supposed to happen and is there a way to get Fetchmail to play
> nice with Yahoo mail if this option is enabled? I would like to enable
> the option if possible.
>
> I am using IMAP with Yahoo if that matters.
>
I don't know what Yahoo considers less secure apps and have not found
any relevant developer information yet - and I do consider this FUD
(fear, uncertainty, doubt) that, by a detour through convenience, try to
make users use their app so they can offload more advertising other
other crap (which is in itself probably more dangerous than a plain login).

If they're forcing clients to bring a web browser for XOAUTH2 like
Google do, I won't implement such things and insist that users permit
traditional POP/IMAP clients to log in.

I have ENABLED the "allow less secure" switch and fetchmail can download
messages for me.

Re: [Fetchmail-users] Yahoo and "Allow apps that use less secure sign in"

[Carlos E. R. <rob...@te...>]

On 2016-09-22 16:27, Jerry wrote:
> I recently activated the "Allow apps that use less secure sign in"
> option on my Yahoo account. Fetchmail immediately was unable to access
> my Yahoo account from that point on. I was forced to turn the option
> off.
> 
> Is this supposed to happen and is there a way to get Fetchmail to play
> nice with Yahoo mail if this option is enabled? I would like to enable
> the option if possible.
> 
> I am using IMAP with Yahoo if that matters.

Seeing no answers, I'll comment that gmail has a similar feature. If we
do not allow apps that use less secure sign in, then fetchmail fails.
The auth method is called "OAuth2", it is supported in Linux by clients
such as Thunderbird, and uses javascript. Fetchmail can't and the
feature is impossible to support.

We talked about that in the thread "Is Oauth supported?" last November.

https://sourceforge.net/p/fetchmail/mailman/message/34628292/


-- 
Cheers / Saludos,

		Carlos E. R.
		(from 13.1 x86_64 "Bottle" at Telcontar)

[Fetchmail-users] Yahoo and "Allow apps that use less secure sign in"

[Jerry <je...@se...>]

I recently activated the "Allow apps that use less secure sign in"
option on my Yahoo account. Fetchmail immediately was unable to access
my Yahoo account from that point on. I was forced to turn the option
off.

Is this supposed to happen and is there a way to get Fetchmail to play
nice with Yahoo mail if this option is enabled? I would like to enable
the option if possible.

I am using IMAP with Yahoo if that matters.

-- 
Jerry

Re: [Fetchmail-users] preconnect syntax error

[Chris <cpo...@em...>]

On Tue, 2016-08-09 at 00:18 -0400, grarpamp wrote:
> On 8/8/16, Chris <cpo...@em...> wrote:
> > 
> > compress the fetchmail log and procmail log on a monthly basis. I
> > keep
> > getting this error when starting fetchmail:
> Compare with any working backup you might have.

No backup, I didn't add this until yesterday
> > 
> > fetchmail:/home/chris/.fetchmailrc:10: syntax error at preconnect
> Check line 10 of fetchmail rc, and any logical nesting
> and termination structures, quoting, etc in that file,
> and in the one below.
> 
> > 
> > Here's the logrotate.conf file I'm using:
> The base64 decode your mailer sent of this file
> indicates that it's full of uncommented linewraps...
> if true, that will break things.
> 
Ah, that's probably the problem then. I C/P'd config file from a
webpage. I should have typed it in manually. 

Thanks for the reply

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
06:53:50 up 11:45, 1 user, load average: 0.21, 0.12, 0.10
Ubuntu 16.04.1 LTS, kernel 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016

Re: [Fetchmail-users] preconnect syntax error

[grarpamp <gra...@gm...>]

On 8/8/16, Chris <cpo...@em...> wrote:
> compress the fetchmail log and procmail log on a monthly basis. I keep
> getting this error when starting fetchmail:

Compare with any working backup you might have.

> fetchmail:/home/chris/.fetchmailrc:10: syntax error at preconnect

Check line 10 of fetchmail rc, and any logical nesting
and termination structures, quoting, etc in that file,
and in the one below.

> Here's the logrotate.conf file I'm using:

The base64 decode your mailer sent of this file
indicates that it's full of uncommented linewraps...
if true, that will break things.

[Fetchmail-users] preconnect syntax error

[Chris <cpo...@em...>]

I have this line in my .fetchmailrc:

preconnect "/usr/sbin/logrotate -s /home/chris/.logrotate.status
/home/chris/.logrotate.conf"

It just calls logrotate which uses the logrotate.conf file  in /home to
compress the fetchmail log and procmail log on a monthly basis. I keep
getting this error when starting fetchmail:

fetchmail --nokeep --nosyslog --logfile /home/chris/fetchmaillog --uidl 
-m procmail
fetchmail:/home/chris/.fetchmailrc:10: syntax error at preconnect

Here's the logrotate.conf file I'm using:

# Global options
# Old versions of log files are compressed with gzip by default.
compress
# Log files are rotated the first time logrotate is run in a month
monthly
# Log files are rotated 12 times before being removed (just keep one
year of history)
rotate=12
# Archive old versions of log files adding a daily extension like
YYYYMMDD instead of simply adding a number.
dateext
# If the log file is missing, go on to the next one without issuing an
error message.
missingok

# Log files to rotate
/home/chris/fetchmaillog { }
/home/chris/procmaillog { }

I'm sure it's something I'm easily overlooking but can't figure it out.

Version info - release 6.3.26+GSS+NTLM+SDPS+SSL-SSLv3+NLS+KRB5.

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
19:42:05 up 33 min, 1 user, load average: 0.48, 0.32, 0.40
Ubuntu 16.04.1 LTS, kernel 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016

Re: [Fetchmail-users] Fetchmail TLS POP connection timeout after Mail Service upgrade

[Brian B. <br...@pi...>]

I am top-posting a response to my own message because I have resolved my 
problem. My fetchmail daemon is successfully collecting queued mail via 
TLS1.2 and POP3.

I resolved my problem by installing and running fetchmailconf in novice 
mode (not a pleasant program, but useful in my case) on my ubuntu 16.04 
development system:-

1. I then hacked "keep" into the generated ~/.fetchmailrc file to make 
sure it didn't lose any queued emails during my tests.

2. I then used fetchmailconf to run in debug mode. It seemed to hang 
again, but when I came back with a coffee to collect the entire timeout 
log, I was amazed to discover it had fetched all the mail (good job I 
used "keep", because nothing could be delivered!)

3. I tidied this .fetchmailrc and moved it to my server as /etc/fetchmailrc.

4. I then hacked my multi-drop configuration into this fetchmailrc and 
ran it through "-V" repeatedly until there were no syntax errors (there 
were quite a few!).

5. When I started the daemon it immediately connected and started 
transferring queued mail - and delivering it to my users. I had a 
tcpdump running, which showed the empty client hello was sent quickly by 
fetchmail and the server certificate was accepted. The session was 
conducted under TLS1.2.

It looks like I suffered from a bug associated with an "apparently 
valid" fetchmailrc configuration which contained unreported errors. The 
fetchmail bug was exposed when my mail provider did the server 
certificate upgrade.

I will analyse the difference between the two fetchmailrc files and 
report my findings once I have a proper explanation.

Brian

On 29/07/16 18:35, fet...@li... wrote:
> Date: Fri, 29 Jul 2016 17:59:57 +1000
> From: Brian Burch <br...@pi...>
> Subject: [Fetchmail-users] Fetchmail TLS POP connection timeout after
> 	Mail	Service upgrade
> To: Fetchmail Users <fet...@li...>
> Message-ID: <da2...@pi...>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> I have been using fetchmail successfully for many years and haven't
> needed to change /etc/fetchmainrc for a very long time.
>
> My mail service provider implemented new SHA-256 certificates this week
> and (except for one "lucky" poll cycle) my fetchmail daemon has timed
> out after the successful 3-way handshake - because it never sends a
> client hello.
>
> My server runs ubuntu 32-bit 14.04 LTS and the ubuntu distribution of
> fetchmail 6.3.26. It also has both openssl 0.9.8 and 1.0.0 installed,
> but an strace of fetchmail shows it is loading libssl.so.1.0.0, which I
> believe is "a good thing". (I have set up an ubuntu 16.04 64-bit system
> on another machine with only openssl 1.0.2, but it behaves the same way.)
>
> I have tinkered with the sslproto, sslcertck and service options, but
> here is the output for the configuration which seems best to me:
>
> brian@shiraz:/etc$ sudo fetchmail -V -vvv --nodetach --nosyslog
> --fetchmailrc /etc/fetchmailrc | tee
> ~/scratch/shiraz-fetchmail-tls-configcheck
> fetchmail: WARNING: Running as root is discouraged.
> This is fetchmail release 6.3.26+GSS+NTLM+SDPS+SSL+NLS+KRB5.
>
> Copyright (C) 2002, 2003 Eric S. Raymond
> Copyright (C) 2004 Matthias Andree, Eric S. Raymond,
>                     Robert M. Funk, Graham Wilson
> Copyright (C) 2005 - 2012 Sunil Shetye
> Copyright (C) 2005 - 2013 Matthias Andree
> Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you
> are welcome to redistribute it under certain conditions. For details,
> please see the file COPYING in the source or documentation directory.
> This product includes software developed by the OpenSSL Project
> for use in the OpenSSL Toolkit. (http://www.openssl.org/)
>
> Fallback MDA: (none)
> Linux shiraz 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:32 UTC
> 2016 i686 i686 i686 GNU/Linux
> Old UID list from yali.mythic-beasts.com: <empty>
> Scratch list of UIDs: <empty>
> Taking options from command line and /etc/fetchmailrc
> Poll interval is 480 seconds
> Idfile is /home/brian/.fetchids
> Fetchmail will forward misaddressed multidrop messages to postmaster.
> Fetchmail will direct error mail to the postmaster.
> Fetchmail will treat permanent errors as temporary (keep messages).
> Options for retrieving from pi...@pi...@yali.mythic-beasts.com:
>    True name of server is yali.mythic-beasts.com.
>    This host will be queried when no host is specified.
>    Password = "xxxxxxxx".
>    Protocol is POP3 (using service pop3s).
>    All available authentication methods will be tried.
>    SSL protocol: TLS1.2+.
>    Server nonresponse timeout is 600 seconds.
>    Default mailbox selected.
>    Only new messages will be retrieved (--all off).
>    Fetched messages will not be kept on the server (--keep off).
>    Old messages will not be flushed before message retrieval (--flush off).
>    Oversized messages will not be flushed before message retrieval
> (--limitflush off).
>    Rewrite of server-local addresses is enabled (--norewrite off).
>    Carriage-return stripping is disabled (stripcr off).
>    Carriage-return forcing is disabled (forcecr off).
>    Interpretation of Content-Transfer-Encoding is enabled (pass8bits off).
>    MIME decoding is disabled (mimedecode off).
>    Idle after poll is disabled (idle off).
>    Nonempty Status lines will be kept (dropstatus off)
>    Delivered-To lines will be kept (dropdelivered off)
>    Message size limit is 16777216 octets (--limit 16777216).
>    Message size warning interval is 864000 seconds (--warnings 864000).
>    Received-message limit is 15 (--fetchlimit 15).
>    Fetch message size limit is 100 (--fetchsizelimit 100).
>    Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4).
>    No SMTP message batch limit (--batchlimit 0).
>    Deletion interval between expunges forced to 15 (--expunge 15).
>    Messages will be SMTP-forwarded to: mail-untrusted
>    Host part of MAIL FROM line will be pingtoo.com
>    Spam-blocking disabled
>    No pre-connection command.
>    No post-connection command.
>    Multi-drop mode: 1 local name recognized.
> 	root
> 	*
>    DNS lookup for multidrop addresses is enabled.
>    Server aliases will be compared with multidrop addresses by name.
>    Envelope header is assumed to be: X-BlackCat-To
>    Number of envelope headers to be skipped over: 0
>    Prefix toopin0296- will be removed from user id
>    Predeclared mailserver aliases: pingtoo.com
>    No interface requirement specified.
>    No monitor interface specified.
>    No plugin command specified.
>    No plugout command specified.
>    No UIDs saved from this host.
>    No poll trace information will be added to the Received header.
>    Messages with bad headers will be rejected.
>
>
> When I run it from a command prompt, the output is very short:
>
> brian@shiraz:/etc$ sudo env LC_ALL=C fetchmail -vvv --nodetach
> --nosyslog --fetchmailrc /etc/fetchmailrc | tee
> ~/scratch/shiraz-fetchmail-tls-test
> fetchmail: WARNING: Running as root is discouraged.
> Old UID list from yali.mythic-beasts.com: <empty>
> Scratch list of UIDs: <empty>
> fetchmail: starting fetchmail 6.3.26 daemon
> fetchmail: 6.3.26 querying yali.mythic-beasts.com (protocol POP3) at Fri
> Jul 29 17:42:56 2016: poll started
> Trying to connect to 93.93.131.127/995...connected.
> fetchmail: timeout after 600 seconds waiting for server
> yali.mythic-beasts.com.
> fetchmail: socket error while fetching from
> pi...@pi...@yali.mythic-beasts.com
> fetchmail: 6.3.26 querying yali.mythic-beasts.com (protocol POP3) at Fri
> Jul 29 17:53:00 2016: poll completed
> Merged UID list from yali.mythic-beasts.com: <empty>
> fetchmail: Query status=2 (SOCKET)
> fetchmail: sleeping at Fri Jul 29 17:53:00 2016 for 480 seconds
>
>
> Wireshark shows me that my fetchmail simply does not send a client
> hello! (Just once, inexplicably, it DID send a hello and then the
> session worked perfectly. However, when it tried the next poll, that
> hung until it timed out.)
>
> Nothing seems to kick it into sending an "empty" client hello... which
> has been redefined from "should" to "must" in RFC5246 (TLS Version 1.2).
> I don't have a client certificate for my server to send, but that
> shouldn't inhibit an "empty" client hello.
>
> To baffle me further, when I run openssl s_client against the server, an
> empty client hello is sent within a few milliseconds. The TLS 1.2
> handshake completes successfully and I can manually connect to the POP3
> server!
>
> I do not believe this problem is related to the server certificate
> change, because until client hello is sent by fetchmail, the server
> certificate is legitimately unknown.
>
> Do you have any words of wisdom for me? I'm feeling pretty lonely at the
> moment!
>
> Thanks,
>
> Brian

[Fetchmail-users] Fetchmail TLS POP connection timeout after Mail Service upgrade

[Brian B. <br...@pi...>]

I have been using fetchmail successfully for many years and haven't 
needed to change /etc/fetchmainrc for a very long time.

My mail service provider implemented new SHA-256 certificates this week 
and (except for one "lucky" poll cycle) my fetchmail daemon has timed 
out after the successful 3-way handshake - because it never sends a 
client hello.

My server runs ubuntu 32-bit 14.04 LTS and the ubuntu distribution of 
fetchmail 6.3.26. It also has both openssl 0.9.8 and 1.0.0 installed, 
but an strace of fetchmail shows it is loading libssl.so.1.0.0, which I 
believe is "a good thing". (I have set up an ubuntu 16.04 64-bit system 
on another machine with only openssl 1.0.2, but it behaves the same way.)

I have tinkered with the sslproto, sslcertck and service options, but 
here is the output for the configuration which seems best to me:

brian@shiraz:/etc$ sudo fetchmail -V -vvv --nodetach --nosyslog 
--fetchmailrc /etc/fetchmailrc | tee 
~/scratch/shiraz-fetchmail-tls-configcheck
fetchmail: WARNING: Running as root is discouraged.
This is fetchmail release 6.3.26+GSS+NTLM+SDPS+SSL+NLS+KRB5.

Copyright (C) 2002, 2003 Eric S. Raymond
Copyright (C) 2004 Matthias Andree, Eric S. Raymond,
                    Robert M. Funk, Graham Wilson
Copyright (C) 2005 - 2012 Sunil Shetye
Copyright (C) 2005 - 2013 Matthias Andree
Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. For details,
please see the file COPYING in the source or documentation directory.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)

Fallback MDA: (none)
Linux shiraz 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:32 UTC 
2016 i686 i686 i686 GNU/Linux
Old UID list from yali.mythic-beasts.com: <empty>
Scratch list of UIDs: <empty>
Taking options from command line and /etc/fetchmailrc
Poll interval is 480 seconds
Idfile is /home/brian/.fetchids
Fetchmail will forward misaddressed multidrop messages to postmaster.
Fetchmail will direct error mail to the postmaster.
Fetchmail will treat permanent errors as temporary (keep messages).
Options for retrieving from pi...@pi...@yali.mythic-beasts.com:
   True name of server is yali.mythic-beasts.com.
   This host will be queried when no host is specified.
   Password = "xxxxxxxx".
   Protocol is POP3 (using service pop3s).
   All available authentication methods will be tried.
   SSL protocol: TLS1.2+.
   Server nonresponse timeout is 600 seconds.
   Default mailbox selected.
   Only new messages will be retrieved (--all off).
   Fetched messages will not be kept on the server (--keep off).
   Old messages will not be flushed before message retrieval (--flush off).
   Oversized messages will not be flushed before message retrieval 
(--limitflush off).
   Rewrite of server-local addresses is enabled (--norewrite off).
   Carriage-return stripping is disabled (stripcr off).
   Carriage-return forcing is disabled (forcecr off).
   Interpretation of Content-Transfer-Encoding is enabled (pass8bits off).
   MIME decoding is disabled (mimedecode off).
   Idle after poll is disabled (idle off).
   Nonempty Status lines will be kept (dropstatus off)
   Delivered-To lines will be kept (dropdelivered off)
   Message size limit is 16777216 octets (--limit 16777216).
   Message size warning interval is 864000 seconds (--warnings 864000).
   Received-message limit is 15 (--fetchlimit 15).
   Fetch message size limit is 100 (--fetchsizelimit 100).
   Do binary search of UIDs during 3 out of 4 polls (--fastuidl 4).
   No SMTP message batch limit (--batchlimit 0).
   Deletion interval between expunges forced to 15 (--expunge 15).
   Messages will be SMTP-forwarded to: mail-untrusted
   Host part of MAIL FROM line will be pingtoo.com
   Spam-blocking disabled
   No pre-connection command.
   No post-connection command.
   Multi-drop mode: 1 local name recognized.
	root
	*
   DNS lookup for multidrop addresses is enabled.
   Server aliases will be compared with multidrop addresses by name.
   Envelope header is assumed to be: X-BlackCat-To
   Number of envelope headers to be skipped over: 0
   Prefix toopin0296- will be removed from user id
   Predeclared mailserver aliases: pingtoo.com
   No interface requirement specified.
   No monitor interface specified.
   No plugin command specified.
   No plugout command specified.
   No UIDs saved from this host.
   No poll trace information will be added to the Received header.
   Messages with bad headers will be rejected.


When I run it from a command prompt, the output is very short:

brian@shiraz:/etc$ sudo env LC_ALL=C fetchmail -vvv --nodetach 
--nosyslog --fetchmailrc /etc/fetchmailrc | tee 
~/scratch/shiraz-fetchmail-tls-test
fetchmail: WARNING: Running as root is discouraged.
Old UID list from yali.mythic-beasts.com: <empty>
Scratch list of UIDs: <empty>
fetchmail: starting fetchmail 6.3.26 daemon
fetchmail: 6.3.26 querying yali.mythic-beasts.com (protocol POP3) at Fri 
Jul 29 17:42:56 2016: poll started
Trying to connect to 93.93.131.127/995...connected.
fetchmail: timeout after 600 seconds waiting for server 
yali.mythic-beasts.com.
fetchmail: socket error while fetching from 
pi...@pi...@yali.mythic-beasts.com
fetchmail: 6.3.26 querying yali.mythic-beasts.com (protocol POP3) at Fri 
Jul 29 17:53:00 2016: poll completed
Merged UID list from yali.mythic-beasts.com: <empty>
fetchmail: Query status=2 (SOCKET)
fetchmail: sleeping at Fri Jul 29 17:53:00 2016 for 480 seconds


Wireshark shows me that my fetchmail simply does not send a client 
hello! (Just once, inexplicably, it DID send a hello and then the 
session worked perfectly. However, when it tried the next poll, that 
hung until it timed out.)

Nothing seems to kick it into sending an "empty" client hello... which 
has been redefined from "should" to "must" in RFC5246 (TLS Version 1.2). 
I don't have a client certificate for my server to send, but that 
shouldn't inhibit an "empty" client hello.

To baffle me further, when I run openssl s_client against the server, an 
empty client hello is sent within a few milliseconds. The TLS 1.2 
handshake completes successfully and I can manually connect to the POP3 
server!

I do not believe this problem is related to the server certificate 
change, because until client hello is sent by fetchmail, the server 
certificate is legitimately unknown.

Do you have any words of wisdom for me? I'm feeling pretty lonely at the 
moment!

Thanks,

Brian

Re: [Fetchmail-users] Unable to search user mails

[Gene H. <ghe...@wd...>]

On Thursday 26 May 2016 00:39:12 grarpamp wrote:

> Also, if you are new, try not to use procmail, use maildrop.
>
I would tend to agree with that although I do use it, the learning curve 
is about an 89 degree angle.  Maildrop?  I'll have to google that.  When 
I'm awake again.

> ----------------------------------------------------------------------
>-------- Mobile security can be enabling, not merely restricting.
> Employees who bring their own devices (BYOD) to work are irked by the
> imposition of MDM restrictions. Mobile Device Manager Plus allows you
> to control only the apps on BYO-devices by containerizing them,
> leaving personal data untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
> _______________________________________________
> Fetchmail-users mailing list
> Fet...@li...
> https://lists.sourceforge.net/lists/listinfo/fetchmail-users


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

Re: [Fetchmail-users] Unable to search user mails

[grarpamp <gra...@gm...>]

Also, if you are new, try not to use procmail, use maildrop.

Re: [Fetchmail-users] Unable to search user mails

[grarpamp <gra...@gm...>]

google
site:sourceforge.net inurl:/mailman/fetchmail-users/ <query>

Also, maintainer could put updated copy of full raw text email
archive in download section like msmtp and cpunks do to
seed mirrors and subscriber mua's.

Fetchmail is good and wish to see next major version.
You may test it from the site.

Re: [Fetchmail-users] Unable to search user mails

[Matthias A. <mat...@gm...>]

Am 25.05.2016 um 20:53 schrieb Carlos E. R.:
> On 2016-05-25 17:52, Gene Heskett wrote:
>> On Wednesday 25 May 2016 08:06:20 Michael Davidson wrote:
>>
>>> Hi,
>>> I'm a new user to Fetchmail and its user lists.   I have problem and
>>> would like to search the list but the search function does not seem to
>>> work for me.  Is this intended because it's a deprecated project
>>> perhaps.
>>>
>>> Regards,
>>> Mike D.
>>> This email is confidential and subject to the
>>> disclaimer<http://www.bbd.co.za/disclaimer> on the BBD website.
>>>
>>>
>> Better not be deprecated, I've been using it for a nearly 2 decades now, 
>> and it I live long enough to reach 91 I'll run it another decade yet.  
>> Most of the odd things have been fixed by now, so it just runs, every 3 
>> minutes here.
>>
>> 99% of the problems can be fixed by a phone call to your ISP to see what 
>> they need to allow you "pop3" access, and the proper use of an MTA, Mail 
>> Transfer Agent, something like procmail to take the fetchmail output and 
>> put it in the systems /var/spool/mail/username file which nearly all 
>> other reader programs will pull and will and sort that mail to their own 
>> directory tree.
> 
> 
> He refers to the search on this mail list archive at
> 
> https://sourceforge.net/p/fetchmail/mailman/fetchmail-users/
> 
> It is true that it does not work. I searched for your name and it finds
> just this post. You have to scroll down to see it. But mine is not found
> at all, and I know I posted a few times.

I see it, too, for several search terms I've tried, and have filed a
support request with sourceforge.net at
<https://sourceforge.net/p/forge/site-support/12855/> - let's see what
they find and if they can fix it.  If not, I'll pull up another plan.

Until then thanks to Nerijunas for the link to the gmane.org search
interface (the sf.net mailing list archive interface is pretty awkward
anyways.)