[pkg-fetchmail-maint] fetchmail: bad-headers accept breaks correct lmtp behavior

Sun Jun 30 10:04:47 UTC 2013

Matthias,

thank you very much for your reply.

At first, I'll provide you the original fetchmailrc (but with changed passwords and user names, of course). There is only /etc/fetchmailrc, and there are no other configuration files (e.g. in user home directories).

Original /etc/fetchmailrc:
--------------------------

set daemon 60
set syslog

poll pop-ssl.omeganet.de proto pop3 user "user1" ssl pass "secret1" is "user1" here smtphost "/var/run/cyrus/socket/lmtp"
poll pop-ssl.omeganet.de proto pop3 user "user2" ssl pass "secret2" is "user2" here smtphost "/var/run/cyrus/socket/lmtp"

poll
pop-ssl.omeganet.de
proto pop3
#bad-header accept
user user3
pass secret3
is user3
smtphost /var/run/cyrus/socket/lmtp
ssl

poll pop.gmx.net proto pop3 user "user4 at gmx.de" ssl pass "secret4" is "user4" here smtphost "/var/run/cyrus/socket/lmtp"
poll pop-ssl.omeganet.de proto pop3 user "user5" ssl pass "secret5" is "user5" here smtphost "/var/run/cyrus/socket/lmtp"
poll secure-pop.t-online.de proto pop3 user "user6 at t-online.de" ssl pass "secret6" is "user6" here smtphost "/var/run/cyrus/socket/lmtp"

------------

By running /etc/init.d/fetchmail debug-run (thanks for the tip!) it gets clear what is going on, thus confirming my theory. I have attached two files: One contains the results when running with /etc/fetchmailrc as shown above (fetchmail-no-bad-headers.txt), and the other one contains the results when running with the same /etc/fetchmailrc, but with bad-header accept activated (i.e. uncommented). From looking at the first file, I can't see something exciting, but at least fetchmail says clearly that it had encountered a message with a bad header and that it won't download it (see line 138 of fetchmail-no-bad-headers.txt).

Looking into fetchmail-with-bad-headers.txt is more interesting. Please have a look at the following excerpt showing the file from line 157:

-----------------------------

reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 2 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: LMTP< 220 spock Cyrus LMTP v2.4.16-Debian-2.4.16-4+deb7u1 server ready
fetchmail: LMTP> LHLO spock.home.omeganet.de
fetchmail: LMTP< 250-spock
fetchmail: LMTP< 250-8BITMIME
fetchmail: LMTP< 250-ENHANCEDSTATUSCODES
fetchmail: LMTP< 250-PIPELINING
fetchmail: LMTP< 250-SIZE
fetchmail: LMTP< 250-AUTH EXTERNAL
fetchmail: LMTP< 250 IGNOREQUOTA
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<stephan.baerwolf at tu-ilmenau.de> SIZE=7975
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 554 5.6.0 Message contains invalid header
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
name 1: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
  not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK

--------------------------------------

Here fetchmail says that it wants to deliver via lmtp, then encounters the message with the bad header, and then suddenly tries to deliver via SMTP. Did I get this right? Is there a great misunderstanding at my side?

With the details given, I hope you can now reproduce the situation.

One last question: Did you try to give --bad-header accept on the COMMAND LINE (e.g. by modifying /etc/default/fetchmailrc or by directly changing the init script)? In my case, that makes fetchmail try to deliver EVERY message for EVERY account via SMTP (if no bad-header reject is given in /etc/fetchmailrc).

Thank you very much for dealing with the problem.

Best regards,

Peter Pfannenschmid

On 29.06.2013 11:30, Matthias Andree wrote:
> Am 27.06.2013 11:04, schrieb Pfannenschmid, P. (Binarus):
>
>> Jun 27 01:11:17 spock fetchmail[8484]: Connection errors for this
>> poll:#012name 0: connection to localhost:smtp [127.0.0.1/25] failed:
>> Connection refused.#012name 1: connection to localhost:smtp
>> [127.0.0.1/25] failed: Connection refused.
>>
>> I am unsure if I get this right, but it seems that fetchmail wants to
>> deliver via localhost:smtp instead of lmtp as soon as bad-header accept
>> is used. The behavior is identical if --bad-headers is given on the
>> command line. Since I am a noob, I am not sure if this is a bug or if I
>> did something wrong.
>>
>> So what do the experts think about that?
>
> Peter,
>
> I can't reproduce this.  I also cannot reproduce the exact situation
> (because I am on Ubuntu 12.04 LTS and installing cyrus-imapd would nuke
> my required dovecot-imapd), but I do not see any attempts to connect to
> the SMTP port, fetchmail consistently connects to the LMTP UNIX socket.
>
> Try
>
> /etc/init.d/fetchmail debug-run
>
> to dig out more information.  You may want to wait for and check the
> second run (after one daemon interval has elapsed and fetchmail is
> restarting).
>
> I also suppose you are not providing the original fetchmailrc, but have
> made up some data; and chances are that the original fetchmailrc is
> being misparsed, while the one you show in this report are not.
>
> Best regards
> Matthias Andree
>
-------------- next part --------------
Pidfile not found! Is fetchmail running? ... failed!
/etc/init.d/fetchmail: exit status of service stop was: 0
/etc/init.d/fetchmail: RUNUSER is fetchmail
/etc/init.d/fetchmail: OPTIONS would be  -f /etc/fetchmailrc --pidfile /var/run/fetchmail/fetchmail.pid --syslog
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from pop.gmx.net: <empty>
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from secure-pop.t-online.de: <empty>
Scratch list of UIDs: <empty>
fetchmail: starting fetchmail 6.3.21 daemon
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:22 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user1
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user1 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:23 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:23 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user2
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user2 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:23 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:23 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user3
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 2 15481
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unknown command: LAST
fetchmail: Unknown command: LAST
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 0000000151a9d1ce
fetchmail: 1 is unseen
fetchmail: POP3< 2 0000000251a9d1ce
fetchmail: 2 is unseen
fetchmail: POP3< .
2 messages for user3 at pop-ssl.omeganet.de (15481 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 7975
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 2 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:2 of 2 (7506 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:24 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: 0000000151a9d1ce = UNSEEN, 0000000251a9d1ce = UNSEEN
fetchmail: swapping UID lists
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:25:24 AM CEST: poll started
Trying to connect to 212.227.17.185/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: Thawte Premium Server CA
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: thawte Primary Root CA
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: thawte, Inc.
fetchmail: Issuer CommonName: thawte Primary Root CA
fetchmail: Subject CommonName: Thawte SSL CA
fetchmail: Server certificate:
fetchmail: Issuer Organization: Thawte, Inc.
fetchmail: Issuer CommonName: Thawte SSL CA
fetchmail: Subject CommonName: pop.gmx.net
fetchmail: Subject Alternative Name: pop.gmx.net
fetchmail: pop.gmx.net key fingerprint: 3D:0C:9A:45:53:86:0B:5B:C8:65:0A:63:9D:EF:F3:C9
fetchmail: POP3< +OK POP server ready H migmx005 0LmFR1-1UJL8X31u6-00ZoDu
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< IMPLEMENTATION trinity
fetchmail: POP3< .
fetchmail: POP3> USER user4 at gmx.de
fetchmail: POP3< +OK password required for user "user4 at gmx.de"
fetchmail: POP3> PASS *
fetchmail: POP3< +OK mailbox "user4 at gmx.de" has 0 messages (0 octets) H migmx005
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user4 at gmx.de at pop.gmx.net
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP server signing off
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:25:24 AM CEST: poll completed
New UID list from pop.gmx.net: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:24 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user5
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user5 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:25:24 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:25:24 AM CEST: poll started
Trying to connect to 194.25.134.46/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Subject CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Subject CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Server certificate:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Subject CommonName: securepop.t-online.de
fetchmail: Subject Alternative Name: securepop.t-online.de
fetchmail: Server CommonName mismatch: securepop.t-online.de != secure-pop.t-online.de
fetchmail: secure-pop.t-online.de key fingerprint: 6B:55:A0:0F:F1:E9:A4:F5:47:07:AA:63:79:8A:F8:D6
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK T-Online POP3 Server fpopd securepop.t-online.de ready 
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Ok
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< USER
fetchmail: POP3< .
fetchmail: POP3> USER user6 at t-online.de
fetchmail: POP3< +OK Ok
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user6 at t-online.de at secure-pop.t-online.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:25:25 AM CEST: poll completed
New UID list from secure-pop.t-online.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: sleeping at Sun 30 Jun 2013 11:25:25 AM CEST for 60 seconds
fetchmail: awakened at Sun 30 Jun 2013 11:26:25 AM CEST
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:25 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user1
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user1 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:25 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:25 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user2
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user2 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:26 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:26 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user3
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 2 15481
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unknown command: LAST
fetchmail: Unknown command: LAST
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 0000000151a9d1ce
fetchmail: 1 is unseen
fetchmail: POP3< 2 0000000251a9d1ce
fetchmail: 2 is unseen
fetchmail: POP3< .
2 messages for user3 at pop-ssl.omeganet.de (15481 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 7975
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 2 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:2 of 2 (7506 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:26 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: 0000000151a9d1ce = UNSEEN, 0000000251a9d1ce = UNSEEN
fetchmail: swapping UID lists
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:26:26 AM CEST: poll started
Trying to connect to 212.227.17.169/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: Thawte Premium Server CA
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: thawte Primary Root CA
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: thawte, Inc.
fetchmail: Issuer CommonName: thawte Primary Root CA
fetchmail: Subject CommonName: Thawte SSL CA
fetchmail: Server certificate:
fetchmail: Issuer Organization: Thawte, Inc.
fetchmail: Issuer CommonName: Thawte SSL CA
fetchmail: Subject CommonName: pop.gmx.net
fetchmail: Subject Alternative Name: pop.gmx.net
fetchmail: pop.gmx.net key fingerprint: 3D:0C:9A:45:53:86:0B:5B:C8:65:0A:63:9D:EF:F3:C9
fetchmail: POP3< +OK POP server ready H migmx114 0LsH7Z-1U8mEN3alE-011uJO
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< IMPLEMENTATION trinity
fetchmail: POP3< .
fetchmail: POP3> USER user4 at gmx.de
fetchmail: POP3< +OK password required for user "user4 at gmx.de"
fetchmail: POP3> PASS *
fetchmail: POP3< +OK mailbox "user4 at gmx.de" has 0 messages (0 octets) H migmx114
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user4 at gmx.de at pop.gmx.net
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP server signing off
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:26:27 AM CEST: poll completed
New UID list from pop.gmx.net: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:27 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user5
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user5 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:26:27 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:26:27 AM CEST: poll started
Trying to connect to 194.25.134.110/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Subject CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Subject CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Server certificate:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Subject CommonName: securepop.t-online.de
fetchmail: Subject Alternative Name: securepop.t-online.de
fetchmail: Server CommonName mismatch: securepop.t-online.de != secure-pop.t-online.de
fetchmail: secure-pop.t-online.de key fingerprint: 6B:55:A0:0F:F1:E9:A4:F5:47:07:AA:63:79:8A:F8:D6
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK T-Online POP3 Server fpopd securepop.t-online.de ready 
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Ok
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< USER
fetchmail: POP3< .
fetchmail: POP3> USER user6 at t-online.de
fetchmail: POP3< +OK Ok
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user6 at t-online.de at secure-pop.t-online.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:26:28 AM CEST: poll completed
New UID list from secure-pop.t-online.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: sleeping at Sun 30 Jun 2013 11:26:28 AM CEST for 60 seconds
fetchmail: awakened at Sun 30 Jun 2013 11:27:28 AM CEST
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:28 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user1
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user1 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:28 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:28 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user2
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user2 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:28 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:28 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user3
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 2 15481
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unknown command: LAST
fetchmail: Unknown command: LAST
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 0000000151a9d1ce
fetchmail: 1 is unseen
fetchmail: POP3< 2 0000000251a9d1ce
fetchmail: 2 is unseen
fetchmail: POP3< .
2 messages for user3 at pop-ssl.omeganet.de (15481 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 7975
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 2 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:2 of 2 (7506 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:29 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: 0000000151a9d1ce = UNSEEN, 0000000251a9d1ce = UNSEEN
fetchmail: swapping UID lists
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:27:29 AM CEST: poll started
Trying to connect to 212.227.17.185/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: Thawte Premium Server CA
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: thawte Primary Root CA
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: thawte, Inc.
fetchmail: Issuer CommonName: thawte Primary Root CA
fetchmail: Subject CommonName: Thawte SSL CA
fetchmail: Server certificate:
fetchmail: Issuer Organization: Thawte, Inc.
fetchmail: Issuer CommonName: Thawte SSL CA
fetchmail: Subject CommonName: pop.gmx.net
fetchmail: Subject Alternative Name: pop.gmx.net
fetchmail: pop.gmx.net key fingerprint: 3D:0C:9A:45:53:86:0B:5B:C8:65:0A:63:9D:EF:F3:C9
fetchmail: POP3< +OK POP server ready H migmx010 0MDNSD-1V34C02OWi-00H2sj
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< IMPLEMENTATION trinity
fetchmail: POP3< .
fetchmail: POP3> USER user4 at gmx.de
fetchmail: POP3< +OK password required for user "user4 at gmx.de"
fetchmail: POP3> PASS *
fetchmail: POP3< +OK mailbox "user4 at gmx.de" has 0 messages (0 octets) H migmx010
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user4 at gmx.de at pop.gmx.net
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP server signing off
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:27:30 AM CEST: poll completed
New UID list from pop.gmx.net: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:30 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user5
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user5 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:27:30 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:27:30 AM CEST: poll started
Trying to connect to 194.25.134.46/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Subject CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Subject CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Server certificate:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Subject CommonName: securepop.t-online.de
fetchmail: Subject Alternative Name: securepop.t-online.de
fetchmail: Server CommonName mismatch: securepop.t-online.de != secure-pop.t-online.de
fetchmail: secure-pop.t-online.de key fingerprint: 6B:55:A0:0F:F1:E9:A4:F5:47:07:AA:63:79:8A:F8:D6
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK T-Online POP3 Server fpopd securepop.t-online.de ready 
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Ok
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< USER
fetchmail: POP3< .
fetchmail: POP3> USER user6 at t-online.de
fetchmail: POP3< +OK Ok
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user6 at t-online.de at secure-pop.t-online.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:27:30 AM CEST: poll completed
New UID list from secure-pop.t-online.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: sleeping at Sun 30 Jun 2013 11:27:30 AM CEST for 60 seconds

Session terminated, terminating shell... ...killed.
fetchmail: awakened at Sun 30 Jun 2013 11:28:30 AM CEST
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:30 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user1
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user1 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:31 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:31 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user2
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user2 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:31 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:31 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user3
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 2 15481
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unknown command: LAST
fetchmail: Unknown command: LAST
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 0000000151a9d1ce
fetchmail: 1 is unseen
fetchmail: POP3< 2 0000000251a9d1ce
fetchmail: 2 is unseen
fetchmail: POP3< .
2 messages for user3 at pop-ssl.omeganet.de (15481 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 7975
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 2 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:2 of 2 (7506 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: incorrect header line found - see manpage for bad-header option
fetchmail: line: protected modes
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:32 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: 0000000151a9d1ce = UNSEEN, 0000000251a9d1ce = UNSEEN
fetchmail: swapping UID lists
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:28:32 AM CEST: poll started
Trying to connect to 212.227.17.169/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: Thawte Premium Server CA
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: thawte Primary Root CA
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: thawte, Inc.
fetchmail: Issuer CommonName: thawte Primary Root CA
fetchmail: Subject CommonName: Thawte SSL CA
fetchmail: Server certificate:
fetchmail: Issuer Organization: Thawte, Inc.
fetchmail: Issuer CommonName: Thawte SSL CA
fetchmail: Subject CommonName: pop.gmx.net
fetchmail: Subject Alternative Name: pop.gmx.net
fetchmail: pop.gmx.net key fingerprint: 3D:0C:9A:45:53:86:0B:5B:C8:65:0A:63:9D:EF:F3:C9
fetchmail: POP3< +OK POP server ready H migmx103 0MatjP-1UYnbk0tcw-00Jw3u
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< IMPLEMENTATION trinity
fetchmail: POP3< .
fetchmail: POP3> USER user4 at gmx.de
fetchmail: POP3< +OK password required for user "user4 at gmx.de"
fetchmail: POP3> PASS *
fetchmail: POP3< +OK mailbox "user4 at gmx.de" has 0 messages (0 octets) H migmx103
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user4 at gmx.de at pop.gmx.net
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP server signing off
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:28:32 AM CEST: poll completed
New UID list from pop.gmx.net: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:32 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user5
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user5 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:28:33 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:28:33 AM CEST: poll started
Trying to connect to 194.25.134.110/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Subject CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Subject CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Server certificate:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Subject CommonName: securepop.t-online.de
fetchmail: Subject Alternative Name: securepop.t-online.de
fetchmail: Server CommonName mismatch: securepop.t-online.de != secure-pop.t-online.de
fetchmail: secure-pop.t-online.de key fingerprint: 6B:55:A0:0F:F1:E9:A4:F5:47:07:AA:63:79:8A:F8:D6
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK T-Online POP3 Server fpopd securepop.t-online.de ready 
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Ok
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< USER
fetchmail: POP3< .
fetchmail: POP3> USER user6 at t-online.de
fetchmail: POP3< +OK Ok
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user6 at t-online.de at secure-pop.t-online.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:28:33 AM CEST: poll completed
New UID list from secure-pop.t-online.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: sleeping at Sun 30 Jun 2013 11:28:33 AM CEST for 60 seconds
fetchmail: terminated with signal 15
-------------- next part --------------
Pidfile not found! Is fetchmail running? ... failed!
/etc/init.d/fetchmail: exit status of service stop was: 0
/etc/init.d/fetchmail: RUNUSER is fetchmail
/etc/init.d/fetchmail: OPTIONS would be  -f /etc/fetchmailrc --pidfile /var/run/fetchmail/fetchmail.pid --syslog
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from pop.gmx.net: <empty>
Old UID list from pop-ssl.omeganet.de: <empty>
Old UID list from secure-pop.t-online.de: <empty>
Scratch list of UIDs: <empty>
fetchmail: starting fetchmail 6.3.21 daemon
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:50 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user1
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user1 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:50 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:50 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user2
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user2 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:51 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:51 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user3
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 2 15481
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unknown command: LAST
fetchmail: Unknown command: LAST
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 0000000151a9d1ce
fetchmail: 1 is unseen
fetchmail: POP3< 2 0000000251a9d1ce
fetchmail: 2 is unseen
fetchmail: POP3< .
2 messages for user3 at pop-ssl.omeganet.de (15481 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 7975
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 2 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: LMTP< 220 spock Cyrus LMTP v2.4.16-Debian-2.4.16-4+deb7u1 server ready
fetchmail: LMTP> LHLO spock.home.omeganet.de
fetchmail: LMTP< 250-spock
fetchmail: LMTP< 250-8BITMIME
fetchmail: LMTP< 250-ENHANCEDSTATUSCODES
fetchmail: LMTP< 250-PIPELINING
fetchmail: LMTP< 250-SIZE
fetchmail: LMTP< 250-AUTH EXTERNAL
fetchmail: LMTP< 250 IGNOREQUOTA
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<stephan.baerwolf at tu-ilmenau.de> SIZE=7975
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 554 5.6.0 Message contains invalid header
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
name 1: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:2 of 2 (7506 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<stephan.baerwolf at tu-ilmenau.de> SIZE=7506
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 554 5.6.0 Message contains invalid header
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
name 1: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: LMTP> QUIT
fetchmail: LMTP< 221 2.0.0 bye
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:51 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: 0000000151a9d1ce = UNSEEN, 0000000251a9d1ce = UNSEEN
fetchmail: swapping UID lists
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:30:51 AM CEST: poll started
Trying to connect to 212.227.17.169/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: Thawte Premium Server CA
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: thawte Primary Root CA
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: thawte, Inc.
fetchmail: Issuer CommonName: thawte Primary Root CA
fetchmail: Subject CommonName: Thawte SSL CA
fetchmail: Server certificate:
fetchmail: Issuer Organization: Thawte, Inc.
fetchmail: Issuer CommonName: Thawte SSL CA
fetchmail: Subject CommonName: pop.gmx.net
fetchmail: Subject Alternative Name: pop.gmx.net
fetchmail: pop.gmx.net key fingerprint: 3D:0C:9A:45:53:86:0B:5B:C8:65:0A:63:9D:EF:F3:C9
fetchmail: POP3< +OK POP server ready H migmx112 0M1JWq-1TzjsO1EEr-00tWid
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< IMPLEMENTATION trinity
fetchmail: POP3< .
fetchmail: POP3> USER user4 at gmx.de
fetchmail: POP3< +OK password required for user "user4 at gmx.de"
fetchmail: POP3> PASS *
fetchmail: POP3< +OK mailbox "user4 at gmx.de" has 0 messages (0 octets) H migmx112
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user4 at gmx.de at pop.gmx.net
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP server signing off
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:30:52 AM CEST: poll completed
New UID list from pop.gmx.net: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:52 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user5
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user5 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:30:52 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:30:52 AM CEST: poll started
Trying to connect to 194.25.134.110/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Subject CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Subject CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Server certificate:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Subject CommonName: securepop.t-online.de
fetchmail: Subject Alternative Name: securepop.t-online.de
fetchmail: Server CommonName mismatch: securepop.t-online.de != secure-pop.t-online.de
fetchmail: secure-pop.t-online.de key fingerprint: 6B:55:A0:0F:F1:E9:A4:F5:47:07:AA:63:79:8A:F8:D6
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK T-Online POP3 Server fpopd securepop.t-online.de ready 
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Ok
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< USER
fetchmail: POP3< .
fetchmail: POP3> USER user6 at t-online.de
fetchmail: POP3< +OK Ok
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user6 at t-online.de at secure-pop.t-online.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:30:52 AM CEST: poll completed
New UID list from secure-pop.t-online.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: sleeping at Sun 30 Jun 2013 11:30:52 AM CEST for 60 seconds
fetchmail: awakened at Sun 30 Jun 2013 11:31:53 AM CEST
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:53 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user1
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user1 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:53 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:53 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user2
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user2 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:53 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:53 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user3
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 3 17746
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unknown command: LAST
fetchmail: Unknown command: LAST
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 0000000151a9d1ce
fetchmail: 1 is unseen
fetchmail: POP3< 2 0000000251a9d1ce
fetchmail: 2 is unseen
fetchmail: POP3< 3 0000063e51a9d1ce
fetchmail: 3 is unseen
fetchmail: POP3< .
3 messages for user3 at pop-ssl.omeganet.de (17746 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 7975
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 3 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: LMTP< 220 spock Cyrus LMTP v2.4.16-Debian-2.4.16-4+deb7u1 server ready
fetchmail: LMTP> LHLO spock.home.omeganet.de
fetchmail: LMTP< 250-spock
fetchmail: LMTP< 250-8BITMIME
fetchmail: LMTP< 250-ENHANCEDSTATUSCODES
fetchmail: LMTP< 250-PIPELINING
fetchmail: LMTP< 250-SIZE
fetchmail: LMTP< 250-AUTH EXTERNAL
fetchmail: LMTP< 250 IGNOREQUOTA
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<stephan.baerwolf at tu-ilmenau.de> SIZE=7975
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 554 5.6.0 Message contains invalid header
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
name 1: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:2 of 3 (7506 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<stephan.baerwolf at tu-ilmenau.de> SIZE=7506
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 554 5.6.0 Message contains invalid header
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
name 1: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
 not flushed
fetchmail: POP3> LIST 3
fetchmail: POP3< +OK 3 2265
fetchmail: POP3> TOP 3 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:3 of 3 (2265 octets)About to rewrite Return-Path: <kwadwoafari at ymail.com>...
...rewritten version is Return-Path: <kwadwoafari at ymail.com>.
About to rewrite Reply-To: <kwadwoafari54 at yahoo.com.hk>...
...rewritten version is Reply-To: <kwadwoafari54 at yahoo.com.hk>.
About to rewrite From: "Dr.Kwadwo Afari-Gyan"<kwadwoafari at ymail.com>...
...rewritten version is From: "Dr.Kwadwo Afari-Gyan"<kwadwoafari at ymail.com>.
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<kwadwoafari at ymail.com> BODY=7BIT SIZE=2265
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 250 2.1.5 Ok SESSIONID=<cyrus-14271-1372584714-1>
 flushed
fetchmail: POP3> DELE 3
fetchmail: POP3< +OK Marked to be deleted.
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out, messages deleted.
fetchmail: LMTP> QUIT
fetchmail: LMTP< 221 2.0.0 bye
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:54 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: 0000000151a9d1ce = UNSEEN, 0000000251a9d1ce = UNSEEN, 0000063e51a9d1ce = EXPUNGED
fetchmail: swapping UID lists
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:31:54 AM CEST: poll started
Trying to connect to 212.227.17.185/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: Thawte Premium Server CA
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: Thawte Consulting cc
fetchmail: Issuer CommonName: Thawte Premium Server CA
fetchmail: Subject CommonName: thawte Primary Root CA
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: thawte, Inc.
fetchmail: Issuer CommonName: thawte Primary Root CA
fetchmail: Subject CommonName: Thawte SSL CA
fetchmail: Server certificate:
fetchmail: Issuer Organization: Thawte, Inc.
fetchmail: Issuer CommonName: Thawte SSL CA
fetchmail: Subject CommonName: pop.gmx.net
fetchmail: Subject Alternative Name: pop.gmx.net
fetchmail: pop.gmx.net key fingerprint: 3D:0C:9A:45:53:86:0B:5B:C8:65:0A:63:9D:EF:F3:C9
fetchmail: POP3< +OK POP server ready H migmx008 0LuztX-1UAQyR0gPi-00zrt2
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Capability list follows
fetchmail: POP3< TOP
fetchmail: POP3< USER
fetchmail: POP3< UIDL
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< IMPLEMENTATION trinity
fetchmail: POP3< .
fetchmail: POP3> USER user4 at gmx.de
fetchmail: POP3< +OK password required for user "user4 at gmx.de"
fetchmail: POP3> PASS *
fetchmail: POP3< +OK mailbox "user4 at gmx.de" has 0 messages (0 octets) H migmx008
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user4 at gmx.de at pop.gmx.net
fetchmail: POP3> QUIT
fetchmail: POP3< +OK POP server signing off
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:31:54 AM CEST: poll completed
New UID list from pop.gmx.net: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:54 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user5
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user5 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:31:55 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:31:55 AM CEST: poll started
Trying to connect to 194.25.134.46/995...connected.
fetchmail: Certificate chain, from root to peer, starting at depth 3:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Certificate at depth 2:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Unknown Issuer CommonName
fetchmail: Subject CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Certificate at depth 1:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 Public Primary Certification Authority - G5
fetchmail: Subject CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Server certificate:
fetchmail: Issuer Organization: VeriSign, Inc.
fetchmail: Issuer CommonName: VeriSign Class 3 International Server CA - G3
fetchmail: Subject CommonName: securepop.t-online.de
fetchmail: Subject Alternative Name: securepop.t-online.de
fetchmail: Server CommonName mismatch: securepop.t-online.de != secure-pop.t-online.de
fetchmail: secure-pop.t-online.de key fingerprint: 6B:55:A0:0F:F1:E9:A4:F5:47:07:AA:63:79:8A:F8:D6
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK T-Online POP3 Server fpopd securepop.t-online.de ready 
fetchmail: POP3> CAPA
fetchmail: POP3< +OK Ok
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< USER
fetchmail: POP3< .
fetchmail: POP3> USER user6 at t-online.de
fetchmail: POP3< +OK Ok
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user6 at t-online.de at secure-pop.t-online.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying secure-pop.t-online.de (protocol POP3) at Sun 30 Jun 2013 11:31:55 AM CEST: poll completed
New UID list from secure-pop.t-online.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: sleeping at Sun 30 Jun 2013 11:31:55 AM CEST for 60 seconds

Session terminated, terminating shell...fetchmail: awakened at Sun 30 Jun 2013 11:32:55 AM CEST
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:32:55 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user1
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user1 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
 ...killed.
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:32:56 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:32:56 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user2
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 0 0
fetchmail: No mail for user2 at pop-ssl.omeganet.de
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:32:56 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: <empty>
fetchmail: not swapping UID lists, no UIDs seen this query
fetchmail: Query status=1 (NOMAIL)
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:32:56 AM CEST: poll started
Trying to connect to 88.198.34.253/995...connected.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: pop-ssl.omeganet.de key fingerprint: 83:7A:D7:0B:2F:3B:09:05:ED:A2:EB:B0:24:0F:44:08
fetchmail: Server certificate verification error: self signed certificate
fetchmail: This means that the root signing certificate (issued for /C=DE/ST=Bayern/L=86399 Bobingen/O=Binarus GmbH & Co. KG/OU=IT/CN=pop-ssl.omeganet.de/emailAddress=info at binarus.de) is not in the trusted CA certificate locations, or that c_rehash needs to be run on the certificate directory. For details, please see the documentation of --sslcertpath and --sslcertfile in the manual page.
fetchmail: Server certificate:
fetchmail: Issuer Organization: Binarus GmbH & Co. KG
fetchmail: Issuer CommonName: pop-ssl.omeganet.de
fetchmail: Subject CommonName: pop-ssl.omeganet.de
fetchmail: Warning: the connection is insecure, continuing anyways. (Better use --sslcertck!)
fetchmail: POP3< +OK Dovecot ready.
fetchmail: POP3> CAPA
fetchmail: POP3< +OK
fetchmail: POP3< CAPA
fetchmail: POP3< TOP
fetchmail: POP3< UIDL
fetchmail: POP3< RESP-CODES
fetchmail: POP3< PIPELINING
fetchmail: POP3< USER
fetchmail: POP3< SASL PLAIN
fetchmail: POP3< .
fetchmail: POP3> USER user3
fetchmail: POP3< +OK
fetchmail: POP3> PASS *
fetchmail: POP3< +OK Logged in.
fetchmail: selecting or re-polling default folder
fetchmail: POP3> STAT
fetchmail: POP3< +OK 2 15481
fetchmail: POP3> LAST
fetchmail: POP3< -ERR Unknown command: LAST
fetchmail: Unknown command: LAST
fetchmail: POP3> UIDL
fetchmail: POP3< +OK
fetchmail: POP3< 1 0000000151a9d1ce
fetchmail: 1 is unseen
fetchmail: POP3< 2 0000000251a9d1ce
fetchmail: 2 is unseen
fetchmail: POP3< .
2 messages for user3 at pop-ssl.omeganet.de (15481 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 7975
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:1 of 2 (7975 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: LMTP< 220 spock Cyrus LMTP v2.4.16-Debian-2.4.16-4+deb7u1 server ready
fetchmail: LMTP> LHLO spock.home.omeganet.de
fetchmail: LMTP< 250-spock
fetchmail: LMTP< 250-8BITMIME
fetchmail: LMTP< 250-ENHANCEDSTATUSCODES
fetchmail: LMTP< 250-PIPELINING
fetchmail: LMTP< 250-SIZE
fetchmail: LMTP< 250-AUTH EXTERNAL
fetchmail: LMTP< 250 IGNOREQUOTA
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<stephan.baerwolf at tu-ilmenau.de> SIZE=7975
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 554 5.6.0 Message contains invalid header
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
name 1: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
 not flushed
fetchmail: POP3> LIST 2
fetchmail: POP3< +OK 2 7506
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< +OK
reading message user3 at static.88-198-34-253.clients.your-server.de:2 of 2 (7506 octets)About to rewrite From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>...
...rewritten version is From: Stephan Baerwolf <stephan.baerwolf at tu-ilmenau.de>.
fetchmail: forwarding to /var/run/cyrus/socket/lmtp
fetchmail: LMTP> MAIL FROM:<stephan.baerwolf at tu-ilmenau.de> SIZE=7506
fetchmail: LMTP< 250 2.1.0 ok
fetchmail: LMTP> RCPT TO:<bin_user3 at localhost>
fetchmail: LMTP< 250 2.1.5 ok
fetchmail: LMTP> DATA
fetchmail: LMTP< 354 go ahead
fetchmail: LMTP>. (EOM)
fetchmail: LMTP< 554 5.6.0 Message contains invalid header
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
Trying to connect to 127.0.0.1/25...connection failed.
fetchmail: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
name 1: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
 not flushed
fetchmail: POP3> QUIT
fetchmail: POP3< +OK Logging out.
fetchmail: LMTP> QUIT
fetchmail: LMTP< 221 2.0.0 bye
fetchmail: 6.3.21 querying pop-ssl.omeganet.de (protocol POP3) at Sun 30 Jun 2013 11:32:57 AM CEST: poll completed
New UID list from pop-ssl.omeganet.de: 0000000151a9d1ce = UNSEEN, 0000000251a9d1ce = UNSEEN
fetchmail: swapping UID lists
fetchmail: 6.3.21 querying pop.gmx.net (protocol POP3) at Sun 30 Jun 2013 11:32:57 AM CEST: poll started
Trying to connect to 212.227.17.169/995...fetchmail: terminated with signal 15