[contribteam] [Bug 9107] trouble fetching mails when one of the list is infected

bugzilla-daemon Tue, 27 Oct 2015 02:45:13 -0700

==================================================================
  Please DO NOT REPLY to this mail or send email to the developers
  about this bug. Please follow-up to Bugzilla using this link:
    http://bugs.contribs.org/show_bug.cgi?id=9107


  Have you checked the Frequently Asked Questions (FAQ)?
    http://wiki.contribs.org/SME_Server:Documentation:FAQ

  Please also take the time to read the following useful guide:
    http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================

            Bug ID: 9107
           Summary: trouble fetching mails when one of the list is
                    infected
    Classification: Contribs
           Product: SME Contribs
           Version: 9.0
          Hardware: ---
                OS: ---
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: smeserver-fetchmail
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]

if one mail of the list, trying to be fetched, is infected, the process can't
proceed mails lastings up to the end of the list, causing an endless loop.
This, i've observed on different servers, and pulling out the incrimined mail,
unlock the endless loop.

this is an extract of maillog, concerning the account, in debug mode

Oct 27 09:45:13 mels fetchmail[27266]: 6.3.17 interroge pop.xxxxxxx.fr
(protocole POP3) Ã  mar. 27 oct. 2015 09:45:13 CETÃ : 

rÃÂ©cupÃÂ©ration en cours
Oct 27 09:45:13 mels fetchmail[27266]: Essai de connexion avec
172.17.2.27/110...connectÃÂ©.
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK mtareg2.xx-xxxxx.org Zimbra
POP3 server ready
Oct 27 09:45:13 mels fetchmail[27266]: POP3> CAPA
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK Capability list follows
Oct 27 09:45:13 mels fetchmail[27266]: POP3< TOP
Oct 27 09:45:13 mels fetchmail[27266]: POP3< USER
Oct 27 09:45:13 mels fetchmail[27266]: POP3< UIDL
Oct 27 09:45:13 mels fetchmail[27266]: POP3< STLS
Oct 27 09:45:13 mels fetchmail[27266]: POP3< SASL PLAIN X-ZIMBRA
Oct 27 09:45:13 mels fetchmail[27266]: POP3< EXPIRE 31 USER
Oct 27 09:45:13 mels fetchmail[27266]: POP3< XOIP
Oct 27 09:45:13 mels fetchmail[27266]: POP3< IMPLEMENTATION ZimbraInc
Oct 27 09:45:13 mels fetchmail[27266]: POP3< .
Oct 27 09:45:13 mels fetchmail[27266]: POP3> STLS
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK Begin TLS negotiation
Oct 27 09:45:13 mels fetchmail[27266]: Certificat du serveur:
Oct 27 09:45:13 mels fetchmail[27266]: Organisation de l'expÃÂ©diteur: Zimbra
Collaboration Server
Oct 27 09:45:13 mels fetchmail[27266]: Nom commun de l'ÃÂ©metteur :
mtareg2.xx-xxxxx.org
Oct 27 09:45:13 mels fetchmail[27266]: Nom commun du sujet:
mtareg2.xx-xxxxx.org
Oct 27 09:45:13 mels fetchmail[27266]: Pas de concordance du nom commun du
serveur: mtareg2.xx-xxxxx.org != pop.xxxxxxx.fr
Oct 27 09:45:13 mels fetchmail[27266]: signature de la clÃÂ© pop.xxxxxxx.frÃ :
C6:5E:E7:BE:46:43:B0:5E:49:F5:A6:0F:9D:64:A5:27
Oct 27 09:45:13 mels fetchmail[27266]: Erreur de vÃÂ©rification du certificat 
du
serveur : unable to get local issuer 

certificate
Oct 27 09:45:13 mels fetchmail[27266]: Cela signifie que le certificat racine
(fourni pour /C=US/ST=N/A/O=Zimbra 

Collaboration Server/OU=Zimbra Collaboration Server/CN=mtareg2.xx-xxxxx.org)
n'est pas dans la liste des certificats des CA 

de confiance ou que c_rehash doit ÃÂªtre exÃÂ©cutÃÂ© sur le rÃÂ©pertoire des
certificats. Pour plus de dÃÂ©tails, consultez la 

documentation de --sslcertpath et --sslcertfile dans la page de manuel.
Oct 27 09:45:13 mels fetchmail[27266]: Certificat du serveur:
Oct 27 09:45:13 mels fetchmail[27266]: Organisation de l'expÃÂ©diteur: Zimbra
Collaboration Server
Oct 27 09:45:13 mels fetchmail[27266]: Nom commun de l'ÃÂ©metteur :
mtareg2.xx-xxxxx.org
Oct 27 09:45:13 mels fetchmail[27266]: Nom commun du sujet:
mtareg2.xx-xxxxx.org
Oct 27 09:45:13 mels fetchmail[27266]: Pas de concordance du nom commun du
serveur: mtareg2.xx-xxxxx.org != pop.xxxxxxx.fr
Oct 27 09:45:13 mels fetchmail[27266]: Erreur de vÃÂ©rification du certificat 
du
serveur : certificate not trusted
Oct 27 09:45:13 mels fetchmail[27266]: Certificat du serveur:
Oct 27 09:45:13 mels fetchmail[27266]: Organisation de l'expÃÂ©diteur: Zimbra
Collaboration Server
Oct 27 09:45:13 mels fetchmail[27266]: Nom commun de l'ÃÂ©metteur :
mtareg2.xx-xxxxx.org
Oct 27 09:45:13 mels fetchmail[27266]: Nom commun du sujet:
mtareg2.xx-xxxxx.org
Oct 27 09:45:13 mels fetchmail[27266]: Pas de concordance du nom commun du
serveur: mtareg2.xx-xxxxx.org != pop.xxxxxxx.fr
Oct 27 09:45:13 mels fetchmail[27266]: Erreur de vÃÂ©rification du certificat 
du
serveur : unable to verify the first 

certificate
Oct 27 09:45:13 mels fetchmail[27266]: Attention: la connexion n'est pas sÃÂ»re
mais on continue quand mÃÂªme (il vaut mieux 

utiliser --sslcertck !).
Oct 27 09:45:13 mels fetchmail[27266]: POP3> CAPA
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK Capability list follows
Oct 27 09:45:13 mels fetchmail[27266]: POP3< TOP
Oct 27 09:45:13 mels fetchmail[27266]: POP3< USER
Oct 27 09:45:13 mels fetchmail[27266]: POP3< UIDL
Oct 27 09:45:13 mels fetchmail[27266]: POP3< STLS
Oct 27 09:45:13 mels fetchmail[27266]: POP3< SASL PLAIN X-ZIMBRA
Oct 27 09:45:13 mels fetchmail[27266]: POP3< EXPIRE 31 USER
Oct 27 09:45:13 mels fetchmail[27266]: POP3< XOIP
Oct 27 09:45:13 mels fetchmail[27266]: POP3< IMPLEMENTATION ZimbraInc
Oct 27 09:45:13 mels fetchmail[27266]: POP3< .
Oct 27 09:45:13 mels fetchmail[27266]: pop.xxxxxxx.fr: passage au TLS rÃÂ©ussi.
Oct 27 09:45:13 mels fetchmail[27266]: POP3> USER [email protected]
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK hello
[email protected], please enter your password
Oct 27 09:45:13 mels fetchmail[27266]: POP3> PASS *
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK server ready
Oct 27 09:45:13 mels fetchmail[27266]: POP3> STAT
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK 14 508839
Oct 27 09:45:13 mels fetchmail[27266]: POP3> UIDL
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK 14 messages
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 1
1263.KbqcOr+v9XYMzvWQXxUtlkxu2UvufB6uE,DszkYaOno=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 2
1264.F1Zk3wUsTAD1+OBsRX2DAiNcDhvzteYoC94drfzxw,M=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 3
1265.zO,Xr6oUyEjcpFPqO1Bhuzee8ANqkFHCg2hHVfi3zYk=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 4
1267.F1DnZoniwovzj7u6c3eOc44zH,OsOzfUBcTB1G2UTUo=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 5
1268.6ZXQal,QNvkpsgbfaveKvDJgYpx2P5PVG+9ScYA0y8k=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 6
1270.rrhEF2NMywf4JPGYjySL4SCZwwsR6Q4ZmDe,7tmwyc8=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 7
1271.fei1tLJEmuxqH67IT9ED57ZIqNqjb,qgKfRAKmw2Q6Q=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 8
1272.pUNUeTlF27eaQyo6Kr8YNWvlPmcPR2MPhD4ikf7fLCE=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 9
1273.9T+XVPUXCPfLL+S1FB9sZcFJrqpsj8Ifj,9g121dqck=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 10
1280.nt27CadPW8cOQ4dNTCPMcV+Sn7kD911ZTK86dY3ofII=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 11
1281.NQpaM69RZnY2dj8ZLkJCnpUKANoy0oY1W53wVwrad7g=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 12
1282.2MMh65hdmzafSDkemo262CGD179Ng74x+YVjUVnVIOU=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 13
1283.HfVTYY6Vge08xXfK7B+x4hfpGesYpdBN83h++M2Z5iE=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< 14
1284.GkEXc+ozsqUFU2olrq1C7yEab0E9IMrJ92reM438lEY=
Oct 27 09:45:13 mels fetchmail[27266]: POP3< .
Oct 27 09:45:13 mels fetchmail[27266]: 14 messages (1 dÃÂ©jÃ  vu) pour
[email protected] dans pop.xxxxxxx.fr (508839 

octets).
Oct 27 09:45:13 mels fetchmail[27266]: POP3> LIST 1
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK 1 46492
Oct 27 09:45:13 mels fetchmail[27266]: POP3> RETR 1
Oct 27 09:45:13 mels fetchmail[27266]: POP3< +OK message follows
Oct 27 09:45:13 mels fetchmail[27266]: lecture du message
[email protected]@pop.xxxxxxx.fr:1 parmi 14 (46492 

octets)Essai de connexion avec 127.0.0.200/25...connectÃÂ©.
Oct 27 09:45:14 mels fetchmail[27266]: SMTP< 220 mels.xxxxxxxxxxxxxx.fr ESMTP
Oct 27 09:45:14 mels fetchmail[27266]: SMTP> EHLO mels.xxxxxxxxxxxxxx.fr
Oct 27 09:45:14 mels fetchmail[27266]: SMTP< 250-xxxxxxxxxxxxxx.fr Hi Unknown
[127.0.0.200]
Oct 27 09:45:14 mels fetchmail[27266]: SMTP< 250-PIPELINING
Oct 27 09:45:14 mels fetchmail[27266]: SMTP< 250-8BITMIME
Oct 27 09:45:14 mels fetchmail[27266]: SMTP< 250-SIZE 30000000
Oct 27 09:45:14 mels fetchmail[27266]: SMTP< 250 STARTTLS
Oct 27 09:45:14 mels fetchmail[27266]: SMTP> MAIL
FROM:<[email protected]> SIZE=46492
Oct 27 09:46:47 mels fetchmail[27266]: SMTP< 250 <[email protected]>,
sender OK - how exciting to get mail from you!
Oct 27 09:46:47 mels fetchmail[27266]: SMTP> RCPT
TO:<[email protected]>
Oct 27 09:46:47 mels fetchmail[27266]: SMTP< 250 <[email protected]>,
recipient ok
Oct 27 09:46:47 mels fetchmail[27266]: SMTP> DATA
Oct 27 09:46:47 mels fetchmail[27266]: SMTP< 354 go ahead
Oct 27 09:46:47 mels fetchmail[27266]: SMTP>. (EOM)
Oct 27 09:46:52 mels fetchmail[27266]: SMTP< 250 Queued! 1445935612 qp 27501
<95043.3050401@>
Oct 27 09:46:52 mels fetchmail[27266]:  ÃÂ©liminÃÂ©
Oct 27 09:46:52 mels fetchmail[27266]: POP3> DELE 1
Oct 27 09:46:52 mels fetchmail[27266]: erreur socket durant la rÃÂ©ception de
[email protected]@pop.xxxxxxx.fr
Oct 27 09:46:52 mels fetchmail[27266]: 6.3.17 interroge pop.xxxxxxx.fr
(protocole POP3) Ã  mar. 27 oct. 2015 09:46:52 CETÃ : 

interrogation finie
Oct 27 09:46:52 mels fetchmail[27266]: Ãâ°tat de la requÃÂªte=2 (SOCKET)
Oct 27 09:46:52 mels fetchmail[27266]: fin normale, ÃÂ©tat 2

Sorry for the inconvenience, i can't give evidences of the role of clamav
anti-virus in this problem, but i remember having made the link between the
fetchmail trouble, the presence of an infected file in the queue, and the
clamav systematic scan of incomming messages. I tried to disable clamav
automatic scan of incoming mails, without succes ( however, i can understand
that...in a security point of view )

Again, Thank you for your support.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/

[contribteam] [Bug 9107] trouble fetching mails when one of the list is infected

Reply via email to