Your message dated Thu, 14 May 2009 15:54:57 +0200
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #322683,
regarding fetchmail can't get some "special" messages from pop3 o2.pl
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
322683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322683
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fetchmail
Version: 6.2.5-18
Severity: important
fetchmail can't get some "special" messages from pop3 o2.pl
i have 3 "special" mesages that can't get from this server
other messages: no problem
log from fetchmail -v
[snip]
fetchmail: POP3> STAT
fetchmail: POP3< +OK 1 5193
1 list dla artii at poczta.o2.pl. (5193 octets).
fetchmail: POP3> LIST 1
fetchmail: POP3< +OK 1 5193
fetchmail: POP3> RETR 1
fetchmail: POP3< +OK
fetchmail: SMTP> MAIL
FROM:<[email protected]> BODY=8BITMIME
SIZE=5193
fetchmail: SMTP< 250 Ok
fetchmail: SMTP> RCPT TO:<[email protected]>
fetchmail: SMTP< 250 Ok
fetchmail: SMTP> DATA
fetchmail: SMTP< 354 End data with <CR><LF>.<CR><LF>
#********************fetchmail: message [email protected]:1 was not the
expected length (4411 actual != 5193 expected)
fetchmail: SMTP>. (EOM)
fetchmail: SMTP< 250 Ok: queued as 75E0960E3
skasowany
fetchmail: POP3> DELE 1
fetchmail: POP3< No insecure packages installed would generate no
output and thus no email.
fetchmail: POP3> QUIT
fetchmail: POP3<
fetchmail: błąd protokołu między serwerem i klientem podczas pobierania
listów z poczta.o2.pl
fetchmail: 6.2.5 querying poczta.o2.pl (protocol POP3) at pią 12 sie
2005 09:28:14 CEST: poll completed
fetchmail: Query status=4 (PROTOCOL)
i use telnet to connect and interesting part of mesage :
[start]
One could then run a cronjob (or whatever) for dpkg-secure and it
would report any of the packages that are both installed and have a
security-tagged bug assosiated with it.
The result, of course, would end up in whomever crond emails it's output
to=
.
No insecure packages installed would generate no output and thus no
email.
Maybe there could be two states? "Insecure, unpatched" and "insecure,
patc=
hed"?
[stop]
q: this is fetchmail problem or server o2.pl problem?
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-686-art
Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-2) (ignored: LC_ALL set to pl_PL)
Versions of packages fetchmail depends on:
ii adduser 3.66 Add and remove users and groups
ii base-files 3.1.6-1 Debian base system miscellaneous f
ii debianutils 2.14.2 Miscellaneous utilities specific t
ii libc6 2.3.5-3 GNU C Library: Shared libraries an
ii libssl0.9.7 0.9.7g-2 SSL shared libraries
Versions of packages fetchmail recommends:
ii ca-certificates 20050804 Common CA Certificates PEM files
-- debconf information:
* fetchmail/confwarn:
* fetchmail/systemwide: false
fetchmail/initdefaultswarn:
fetchmail/runasroot: false
fetchmail/fetchidswarn:
--- End Message ---
--- Begin Message ---
not a fetchmail bug, and lack of time for workarounds for non-compliant
servers
--- End Message ---
