Return-Path: eudora_m@qualcomm.com Received: from rohan.qualcomm.com (rohan.qualcomm.com [192.35.156.5]) by silcon.silcon.com (8.8.6/8.6.9) with ESMTP id JAA09035 for ; Tue, 9 Dec 1997 09:59:37 -0800 (PST) Received: (from eudora_m@localhost) by rohan.qualcomm.com id KAA25481 for herbr@silcon.com; Tue, 9 Dec 1997 10:01:54 -0800 (PST) Date: Tue, 9 Dec 1997 10:01:54 -0800 (PST) Message-Id: <199712091801.KAA25481@rohan.qualcomm.com> Mime-Version: 1.0 To: Herbert Rubin From: qpopper@eudora.com Subject: Your message to qpopper@eudora.com Content-Type: multipart/mixed; boundary="============_-881690514==_============" X-UIDL: 2a84549fe9a35b96f4e81dcd7e9c6fcf X-PMFLAGS: 570949760 0 --============_-881690514==_============ Content-Type: text/plain; charset="us-ascii" Automated response from qpopper@eudora.com. Thanks for your message. You should receive a reply from us shortly. We are aware of the recent CERT advisory (CA-97.09) regarding vulnerabilities in certain implementations of POP3 and IMAP. Our engineers have examined the QPopper source code, which is based on source from UC Berkeley. They determined that QPopper is *NOT* vulnerable to a buffer overflow attack as described in CA-97.09. It strictly checks the size of messages before copying them into its buffer. If you have any further questions regarding QPopper and CA-97.09, please feel free to write us at . Thanks for your support! The QPopper Team Eudora Division of QUALCOMM Incorporated --============_-881690514==_============ Content-Type: text/plain; charset="us-ascii" ____________________________________________________________________________ Here's your original message: >from herbr@pfinders.com Tue Dec 9 10:01:50 1997 Received: from echo.qualcomm.com (echo.qualcomm.com [129.46.136.20]) by rohan.qualcomm.com with SMTP id KAA25474 for ; Tue, 9 Dec 1997 10:01:49 -0800 (PST) Received: from warlock.qualcomm.com by echo.qualcomm.com (SMI-8.6/SMI-SVR4) id JAA28040; Tue, 9 Dec 1997 09:57:30 -0800 Received: from moria.qualcomm.com (qualcomm.com [192.35.156.11]) by warlock.qualcomm.com (8.8.5/1.4/8.7.2/1.13) with ESMTP id JAA20047 for ; Tue, 9 Dec 1997 09:58:44 -0800 (PST) Received: (from daemon@localhost) by moria.qualcomm.com id JAA26267 for ; Tue, 9 Dec 1997 09:59:37 -0800 (PST) Received: from silcon.silcon.com(206.99.109.10) via SMTP by moria.qualcomm.com, id smtpdAAA0IaxAB; Tue Dec 9 09:59:26 1997 Received: from herbrubi (ts1-20.silcon.com [206.99.109.20]) by silcon.silcon.com (8.8.6/8.6.9) with ESMTP id JAA08945 for ; Tue, 9 Dec 1997 09:56:18 -0800 (PST) Message-ID: <348D85DE.47E1810F@pfinders.com> Date: Tue, 09 Dec 1997 09:54:39 -0800 From: Herbert Rubin X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 Subject: NOOP supported for Qpopper? X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii My ISP uses Qpopper and my POP3 gateway times out on large messages. I am sending NOOP to keep the mailbox open but QPopper times out and closes it. So, I never get a chance to delete the large message. Is there something I should know about QPopper and its time out behavior or NOOP support? Thanks ahead of time, Herb Rubin --============_-881690514==_============-- -- End --