Menu
▾
▴
fetchmail-users — User questions and discussion
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(16) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(2) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(8) |
Aug
(21) |
Sep
(17) |
Oct
(35) |
Nov
(39) |
Dec
(55) |
| 2006 |
Jan
(70) |
Feb
(11) |
Mar
(55) |
Apr
(27) |
May
(73) |
Jun
(47) |
Jul
(63) |
Aug
(27) |
Sep
(52) |
Oct
(39) |
Nov
(87) |
Dec
(15) |
| 2007 |
Jan
(23) |
Feb
(46) |
Mar
(108) |
Apr
(63) |
May
(54) |
Jun
(34) |
Jul
(29) |
Aug
(103) |
Sep
(46) |
Oct
(69) |
Nov
(29) |
Dec
(17) |
| 2008 |
Jan
(45) |
Feb
(32) |
Mar
(25) |
Apr
(17) |
May
(39) |
Jun
(20) |
Jul
(64) |
Aug
(31) |
Sep
(38) |
Oct
(20) |
Nov
(42) |
Dec
(50) |
| 2009 |
Jan
(10) |
Feb
(38) |
Mar
(3) |
Apr
(29) |
May
(41) |
Jun
(31) |
Jul
(21) |
Aug
(53) |
Sep
(49) |
Oct
(26) |
Nov
(28) |
Dec
(15) |
| 2010 |
Jan
(83) |
Feb
(38) |
Mar
(33) |
Apr
(44) |
May
(9) |
Jun
(16) |
Jul
(35) |
Aug
(38) |
Sep
(11) |
Oct
(35) |
Nov
(68) |
Dec
(19) |
| 2011 |
Jan
(16) |
Feb
(69) |
Mar
(42) |
Apr
(54) |
May
(56) |
Jun
(29) |
Jul
|
Aug
(65) |
Sep
(3) |
Oct
(39) |
Nov
(33) |
Dec
(4) |
| 2012 |
Jan
(31) |
Feb
(21) |
Mar
(26) |
Apr
(13) |
May
(38) |
Jun
(39) |
Jul
(14) |
Aug
(31) |
Sep
(8) |
Oct
(32) |
Nov
(12) |
Dec
(16) |
| 2013 |
Jan
(40) |
Feb
(22) |
Mar
(21) |
Apr
(15) |
May
(13) |
Jun
(9) |
Jul
(34) |
Aug
(10) |
Sep
(10) |
Oct
|
Nov
(7) |
Dec
(1) |
| 2014 |
Jan
(25) |
Feb
(9) |
Mar
(8) |
Apr
(12) |
May
(7) |
Jun
|
Jul
(7) |
Aug
(4) |
Sep
(27) |
Oct
(25) |
Nov
(18) |
Dec
(3) |
| 2015 |
Jan
(18) |
Feb
(13) |
Mar
(4) |
Apr
(19) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(7) |
Sep
(6) |
Oct
(4) |
Nov
(19) |
Dec
(6) |
| 2016 |
Jan
|
Feb
(8) |
Mar
(14) |
Apr
|
May
(11) |
Jun
|
Jul
(2) |
Aug
(3) |
Sep
(10) |
Oct
|
Nov
(11) |
Dec
(17) |
| 2017 |
Jan
(17) |
Feb
(35) |
Mar
|
Apr
(4) |
May
(8) |
Jun
(2) |
Jul
(16) |
Aug
|
Sep
(5) |
Oct
(11) |
Nov
(15) |
Dec
(10) |
| 2018 |
Jan
|
Feb
(3) |
Mar
|
Apr
(3) |
May
(2) |
Jun
(8) |
Jul
|
Aug
(10) |
Sep
(17) |
Oct
(15) |
Nov
(12) |
Dec
(10) |
| 2019 |
Jan
(4) |
Feb
(14) |
Mar
(33) |
Apr
(17) |
May
(7) |
Jun
(6) |
Jul
(2) |
Aug
(4) |
Sep
(22) |
Oct
(13) |
Nov
|
Dec
|
| 2020 |
Jan
(36) |
Feb
(19) |
Mar
(31) |
Apr
(2) |
May
(22) |
Jun
(7) |
Jul
(25) |
Aug
(9) |
Sep
(17) |
Oct
(52) |
Nov
(13) |
Dec
(9) |
| 2021 |
Jan
(23) |
Feb
(13) |
Mar
(9) |
Apr
(15) |
May
(3) |
Jun
(7) |
Jul
(4) |
Aug
(23) |
Sep
(3) |
Oct
(8) |
Nov
(28) |
Dec
(9) |
| 2022 |
Jan
(38) |
Feb
(2) |
Mar
(56) |
Apr
(24) |
May
(29) |
Jun
(22) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(13) |
Nov
(2) |
Dec
|
| 2023 |
Jan
(6) |
Feb
(1) |
Mar
(1) |
Apr
(4) |
May
|
Jun
|
Jul
(21) |
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2024 |
Jan
(15) |
Feb
(4) |
Mar
|
Apr
(4) |
May
(11) |
Jun
(9) |
Jul
(1) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(1) |
Dec
(1) |
| 2025 |
Jan
(7) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
(10) |
Jul
|
Aug
(1) |
Sep
(12) |
Oct
|
Nov
|
Dec
|
|
From: Jakob H. <jh...@pl...> - 2005-10-27 10:11:35
|
Karel Kulhavy wrote: > reading message cl...@tw...:1 of 162 (765 header octets) > fetchmail: SMTP error: 501 <agrode@%%DOMAIN%>: domain missing or malformed > gethostbyname failed for kestrel Fetchmail should go on retrieving the next message after a 501 from the smtp server, but it seems to consider the failed gethostbyname() a fatal error. Looks more like a misconfiguration on your side. "kestrel" is your hostname, right? I personally would always recommend using fetchmail with the mda option (for the usual pop/imap retrieval), so you won't have all these smtp problems. At least as long as you are not using multidrop, but that is not recommended anyway. |
|
From: Rob M. <rob...@gm...> - 2005-10-26 20:06:56
|
On 26/10/05, Karel Kulhavy <cl...@tw...> wrote:
> I got some malformed spam which causes fetchmail to stop on this spam
> and I am unable to download 162 waiting messages behind this spam.
>
> This seems to be some kind of fetchmail DoS vulnerability - if someone
> sends this mail to all fetchmail users in the world, they will be pretty
> pissed off to have to log in to remote machine and erase the e-mail by
> hand. And if he sends every hour, they will have to change to a
> different program than fetchmail ;-)
I've seen a similar problem before, but usually fetchmail will skip
the offending mail and carry on. One option may be to set 501 as one
of the anti-spam codes.
> don't know how to get IMAP server greeting line
telnet IMAPHOST 143
More useful than the config dump would be the contents of .fetchmailrc
and output of "fetchmail -v -v" for the problem email (along with the
matching log entries from your MTA).
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Karel K. <cl...@tw...> - 2005-10-26 11:06:04
|
Here is the poison: >From agrode@%%DOMAIN% Tue Oct 25 17:34:28 2005 Return-Path: <agrode@%%DOMAIN%> Received: from EXTREME-07 (200-102-91-6.smace701.dsl.brasiltelecom.net.br [200.102.91.6] (may be forged)) by twin.jikos.cz (8.11.6p2/8.11.6) with SMTP id j9PFYRb05150 for <cl...@tw...>; Tue, 25 Oct 2005 17:34:27 +0200 Message-ID: <001401c5d979$885ff56c$0501010a@EXTREME-07> From: "Floris" <agrode@%%DOMAIN%> To: cl...@tw... Subject: You know how it? to work with stable software! ==Ref:515== Date: Tue, 25 Oct 2005 13:34:05 -0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0011_01C5D968.C4D24D30" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-IMAPbase: 1130271542 170 X-Keywords: X-UID: 9 Status: RO Content-Length: 2489 Lines: 61 This is a multi-part message in MIME format. ------=_NextPart_000_0011_01C5D968.C4D24D30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 0ffice XP - $6o other world famous software from name-branded corporations at same prices! INTERESTING ? then visit the BEST ever OEM store on internet! --- Why so cheap? All the software is OEM- Meaning that you don't get the box and the manual with your software. All you will receive is the actual software and your unique registration code. All the software is in the English language for PC. Our offers are unbeatable and we always update our prices to make sure we provide you with the best possible offers. Hurry up and place your order, because our supplies are limited. To unsubscribe click here! ------=_NextPart_000_0011_01C5D968.C4D24D30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR> <STYLE></STYLE> </HEAD><BODY bgcolor="#FFFFFF"> <p align="center"><font size="+4"><b><a href="http://VLfI9nf4fgwmx1em2rr5w9rne99r.answerik.com/?mpaMv">0ffice XP - $6o</a></b></font></p> <p align="center"><b><font color="#FF0000">other world famous software from name-branded corporations at same prices! INTERESTING ?</font></b></p> <p align="center"><a href="http://fcF9nf4fgwmx1em2rr5w9rne99r.answerik.com/?IMk">then visit the BEST ever OEM store on internet!</a><br> ---<br> <font size="-2">Why so cheap?</font></p> <p align="center"><font size="-2">All the software is OEM- Meaning that you don't get the box and the<br> manual with your software. All you will receive is the actual<br> software and your unique registration code.</font></p> <p align="center"><font size="-2">All the software is in the English language for PC. Our offers<br> are unbeatable and we always update our prices to make sure we<br> provide you with the best possible offers. Hurry up and place<br> your order, because our supplies are limited.</font></p> <p align="center"> </p> <DIV align="center"><FONT face=Arial size=2>To unsubscribe <A href="http://SfHH9nf4fgwmx1em2rr5w9rne99r.answerik.com/dGk?nXd">click here!</FONT></DIV> </BODY></HTML> ------=_NextPart_000_0011_01C5D968.C4D24D30-- |
|
From: Karel K. <cl...@tw...> - 2005-10-26 10:59:31
|
I got some malformed spam which causes fetchmail to stop on this spam and I am unable to download 162 waiting messages behind this spam. This seems to be some kind of fetchmail DoS vulnerability - if someone sends this mail to all fetchmail users in the world, they will be pretty pissed off to have to log in to remote machine and erase the e-mail by hand. And if he sends every hour, they will have to change to a different program than fetchmail ;-) clock@kestrel:~$ fetchmail 162 messages for clock at twin.jikos.cz. reading message cl...@tw...:1 of 162 (765 header octets) fetchmail: SMTP error: 501 <agrode@%%DOMAIN%>: domain missing or malformed gethostbyname failed for kestrel Operating system gentoo linux GCC 3.3.6 don't know how to get IMAP server greeting line MDA: ESMTP Exim 4.50 This is fetchmail release 6.2.5.2+RPA+NTLM+SDPS+SSL+INET6+NLS Fallback MDA: (none) Linux kestrel 2.6.12-gentoo-r10 #2 Tue Oct 4 10:27:59 CEST 2005 i686 Intel(R) Pentium(R) M processor 1.50GHz GenuineIntel GNU/Linux Taking options from command line and /home/clock/.fetchmailrc Idfile is /home/clock/.fetchids Fetchmail will forward misaddressed multidrop messages to clock. Options for retrieving from cl...@tw...: True name of server is twin.jikos.cz. Protocol is IMAP. All available authentication methods will be tried. SSL encrypted sessions enabled. Server nonresponse timeout is 300 seconds (default). Default mailbox selected. Only new messages will be retrieved (--all off). Fetched messages will not be kept on the server (--keep off). Old messages will not be flushed before message retrieval (--flush off). Rewrite of server-local addresses is enabled (--norewrite off). Carriage-return stripping is disabled (stripcr off). Carriage-return forcing is disabled (forcecr off). Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). MIME decoding is disabled (mimedecode off). Idle after poll is disabled (idle off). Nonempty Status lines will be kept (dropstatus off) Delivered-To lines will be kept (dropdelivered off) Fetch message size limit is 100 (--fetchsizelimit 100). Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10). Messages will be SMTP-forwarded to: localhost (default) Single-drop mode: 1 local name(s) recognized. No UIDs saved from this host. Options for retrieving from cl...@at...: True name of server is atrey.karlin.mff.cuni.cz. Protocol is IMAP. All available authentication methods will be tried. SSL encrypted sessions enabled. Server nonresponse timeout is 300 seconds (default). Default mailbox selected. Only new messages will be retrieved (--all off). Fetched messages will not be kept on the server (--keep off). Old messages will not be flushed before message retrieval (--flush off). Rewrite of server-local addresses is enabled (--norewrite off). Carriage-return stripping is disabled (stripcr off). Carriage-return forcing is disabled (forcecr off). Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). MIME decoding is disabled (mimedecode off). Idle after poll is disabled (idle off). Nonempty Status lines will be kept (dropstatus off) Delivered-To lines will be kept (dropdelivered off) Fetch message size limit is 100 (--fetchsizelimit 100). Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10). Messages will be SMTP-forwarded to: localhost (default) Single-drop mode: 1 local name(s) recognized. No UIDs saved from this host. Options for retrieving from di...@po...: True name of server is pop.centrum.cz. Protocol is POP3. All available authentication methods will be tried. Server nonresponse timeout is 300 seconds (default). Default mailbox selected. Only new messages will be retrieved (--all off). Fetched messages will not be kept on the server (--keep off). Old messages will not be flushed before message retrieval (--flush off). Rewrite of server-local addresses is enabled (--norewrite off). Carriage-return stripping is disabled (stripcr off). Carriage-return forcing is disabled (forcecr off). Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). MIME decoding is disabled (mimedecode off). Idle after poll is disabled (idle off). Nonempty Status lines will be kept (dropstatus off) Delivered-To lines will be kept (dropdelivered off) Fetch message size limit is 100 (--fetchsizelimit 100). Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10). Messages will be SMTP-forwarded to: localhost (default) Single-drop mode: 1 local name(s) recognized. No UIDs saved from this host. Options for retrieving from yc...@po...: True name of server is pop.centrum.cz. Protocol is POP3. All available authentication methods will be tried. Server nonresponse timeout is 300 seconds (default). Default mailbox selected. Only new messages will be retrieved (--all off). Fetched messages will not be kept on the server (--keep off). Old messages will not be flushed before message retrieval (--flush off). Rewrite of server-local addresses is enabled (--norewrite off). Carriage-return stripping is disabled (stripcr off). Carriage-return forcing is disabled (forcecr off). Interpretation of Content-Transfer-Encoding is enabled (pass8bits off). MIME decoding is disabled (mimedecode off). Idle after poll is disabled (idle off). Nonempty Status lines will be kept (dropstatus off) Delivered-To lines will be kept (dropdelivered off) Fetch message size limit is 100 (--fetchsizelimit 100). Do binary search of UIDs during 9 out of 10 polls (--fastuidl 10). Messages will be SMTP-forwarded to: localhost (default) Single-drop mode: 1 local name(s) recognized. No UIDs saved from this host. |
|
From: Matthias A. <mat...@gm...> - 2005-10-21 16:10:13
|
On Fri, 21 Oct 2005, Thomas Wolff wrote: > Hello, > > > * fetchmailconf now changes the output file to mode 0600 BEFORE writing to it, > > so there is no window where passwords could be read by the world. > > Matthias Andree. > This doesn't sound quite right. The only safe way is to CREATE the > file in 600 mode right away. If you just CHANGE to 600 even before writing > to it, there IS an unsafe window. > Try the following: > touch x > tail -f x > > Then in another shell: > chmod -r x > echo bla >> x > > "bla" will show up in the first window, read by "tail". Right you are, and thanks for reporting the problem. (Thanks also to Miloslav Trmac, who also reported the problem.) Actually, the new script also sets the umask to 077 before opening the file, so we're doing the right thing, only the NEWS file is off track. I have uploaded a new version of a security announcement, now at http://fetchmail.berlios.de/fetchmail-SA-2005-02.txt and will ship it to pertinent lists shortly. I have also withdrawn fetchmailconf-1.43.1 and the corresponding patch from distribution and uploaded fetchmailconf-1.43.2 for users of fetchmail-6.2.5.2. Please, further discussion only on fet...@li.... Warning: reply-to is set - take care should you desire to mail me directly - some mailers require you to manually pick "To Sender Only" or "Ignore Reply-To." -- Matthias Andree |
|
From: Thomas W. <to...@to...> - 2005-10-21 15:04:07
|
Hello, > * fetchmailconf now changes the output file to mode 0600 BEFORE writing to it, > so there is no window where passwords could be read by the world. > Matthias Andree. This doesn't sound quite right. The only safe way is to CREATE the file in 600 mode right away. If you just CHANGE to 600 even before writing to it, there IS an unsafe window. Try the following: touch x tail -f x Then in another shell: chmod -r x echo bla >> x "bla" will show up in the first window, read by "tail". Kind regards, Thomas Wolff |
|
From: Matthias A. <mat...@gm...> - 2005-10-21 14:38:03
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I have just released fetchmail 6.2.9-rc6, yet another release candidate before 6.3.0, after further fixes to -rc5, became necessary. - ----------------------------------------------------------------------- Fetchmail needs your support - please consider a donation via: <https://developer.berlios.de/developer/make_donation.php?user_id=2007> - ----------------------------------------------------------------------- Changes since -rc5 are: * fetchmailconf now changes the output file to mode 0600 BEFORE writing to it, so there is no window where passwords could be read by the world. Matthias Andree. * Missed --port/--service/--ssl cleanups in the manual. Reminder from Thomas Wolff. (MA) * Complain in POP3 if NTLM/MSN auth is requested but had not been enabled at compile time. This configuration mismatch now causes an error message and authentication failure. Found by Yves Boisjoly. Matthias Andree * fetchmailconf now allows expert users to choose the authorization type and also offers MSN and NTLM, suggested by Yves Boisjoly. Matthias Andree * fetchmailconf now (as of 1.49) writes its version to the comment of the saved run control file. Matthias Andree * Properly shut down SSL connections. Berlios Patch #647 by Arkadiusz Miśkiewicz. (MA) * Global variable cleanup, to fix daemon mode reinitialization problems. Patch by Sunil Shetye. (MA) I seek everyone to test it out, report remaining bugs, update outdated translations (send your translated .po files to the translation project's robot, it'll forward your translation to the -devel list) or send patches for documentation or report inconsistencies (including formatting!) in the documentation. The software is available from: <https://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=7672> <http://home.pages.de/~mandree/fetchmail/> Regards, - -- Matthias Andree -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFDWOElvmGDOQUufZURAnEHAKCLG0lXreSui5fw1nqfYGRDihCsHgCfTh0Y ZGUGQHcBElLVaHfsUNurPOw= =PejO -----END PGP SIGNATURE----- |
|
From: Barsalou <ba...@at...> - 2005-10-18 07:55:12
|
I recently had a similar problem. One thing to try is to turn off dns in the fetchmail config. Also, there might be an issue with ipv6 if you used the rpms instead of compiling it yourself. Give it a shot! Mike B. -- Barsalou <ba...@at...> |
|
From: Rob M. <rob...@gm...> - 2005-10-13 18:38:52
|
On 13/10/05, deven barhate <red...@gm...> wrote: > Dear Friends, > > I'm using fetchmail-6.2.0-3 and sendmail-8.12 on redhat linux 9. Please upgrade fetchmail, there are known security problems with versions before 6.2.5.2. > fetchmail: socket error while fetching from mail.server.com > fetchmail: 6.2.5 querying mail.server.com ( protocol POP3) at <date and > time>: poll completed > fetchmail Query status=2 (SOCKET) > fetchmail: sleeping at < date and time> > > and fetchmail die. > > once again i try to fetch mails it again dies at the same mail. I have to > delete that mail and then only I can fetch mails untill next socket error > message comes. > > I have to monitor all the time for this error. and delete that perticular > mail. > > Please help me regarding this matter. I searched lot but i only get is the > posts asking for same problems but not solutions. The problem relates to comms either with your remote POP server or your local SMTP server. You need to check your local mail log to tell whether it's a problem with your local setup or the remote POP server. Details on the problem email would be helpful! -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |
|
From: deven b. <red...@gm...> - 2005-10-13 11:17:54
|
Dear Friends, I'm using fetchmail-6.2.0-3 and sendmail-8.12 on redhat linux 9. I can fetch some mails thoroly without any problem but at some point i'm geting fillowing message- fetchmail: socket error while fetching from mail.server.com<http://mail.server.com/> fetchmail: 6.2.5 querying mail.server.com <http://mail.server.com/> ( protocol POP3) at <date and time>: poll completed fetchmail Query status=2 (SOCKET) fetchmail: sleeping at < date and time> and fetchmail die. once again i try to fetch mails it again dies at the same mail. I have to delete that mail and then only I can fetch mails untill next socket error message comes. I have to monitor all the time for this error. and delete that perticular mail. Please help me regarding this matter. I searched lot but i only get is the posts asking for same problems but not solutions. Thanks and Regards, Deven. |
|
From: Rob M. <rob...@gm...> - 2005-10-11 17:11:21
|
On 11/10/05, Rouven Sacha <rs...@bl...> wrote:
> I have to keep the messages on the server, due to the fact that other
> clients have to have access to these messages as well. And if i do
> understand things right, "fetchall" conflicts with "keep".
Certainly a Bad Idea :-)
> The Debian manpage of fetchmail calls the UIDL code "flaky". Since the
> manpage seems to be outdated (it is pointing to esr's homepage, for
> example): is UIDL still flaky in 6.2.5.2?
I've been running one mail server that polls half a dozen remote
mailboxes (about to jump to a couple of dozen) using UIDL for nearly 3
years now. I've never had a problem with UIDL support.
Alternatively, put it this way - you have no choice. You can either
enable UIDL support or try to find another solution that doesn't use
fetchmail :)
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Rob F. <rf...@fu...> - 2005-10-11 14:56:34
|
Please keep list mail on the list..... Rouven Sacha wrote: > Am Montag, den 10.10.2005, 14:43 -0400 schrieb Rob Funk: > > I've never even heard of Merak Mail Server myself.... > > http://www.icewarp.com/ > > > Are you normally checking the mailbox with other clients also? > > You could try the fetchall option, or the uidl option. Read about > > those in the man page. > > I have to keep the messages on the server, due to the fact that other > clients have to have access to these messages as well. And if i do > understand things right, "fetchall" conflicts with "keep". > > The Debian manpage of fetchmail calls the UIDL code "flaky". Since the > manpage seems to be outdated (it is pointing to esr's homepage, for > example): is UIDL still flaky in 6.2.5.2? > > > We can't see what's wrong from a successful log. We can only see > > what's going wrong from an unsuccessful log. > > I'm running fetchmail in Debian's debug-run mode right now. I'm going > to post updates as soon as i get them. |
|
From: Rouven S. <rs...@bl...> - 2005-10-11 10:10:20
|
Am Montag, den 10.10.2005, 14:43 -0400 schrieb Rob Funk: > I've never even heard of Merak Mail Server myself.... http://www.icewarp.com/ > Are you normally checking the mailbox with other clients also? > You could try the fetchall option, or the uidl option. Read about > those in the man page. I have to keep the messages on the server, due to the fact that other clients have to have access to these messages as well. And if i do understand things right, "fetchall" conflicts with "keep". The Debian manpage of fetchmail calls the UIDL code "flaky". Since the manpage seems to be outdated (it is pointing to esr's homepage, for example): is UIDL still flaky in 6.2.5.2? > We can't see what's wrong from a successful log. We can only see > what's going wrong from an unsuccessful log. I'm running fetchmail in Debian's debug-run mode right now. I'm going to post updates as soon as i get them. -- Rouven Sacha | Blinkenlichten GbR | 0174/4220127 | fax: 030/13896249 |
|
From: Rob F. <rf...@fu...> - 2005-10-10 20:43:56
|
Rouven Sacha wrote: > Are there any known issues that affect using fetchmail 6.2.5.2 to pop a > Merak Mail Server (7.4.5)? I've never even heard of Merak Mail Server myself.... > I am experiencing problems with fetchmail > not recognizing and fetching new messages on that mail server which > other MUA have no problem at all to see and fetch. Are you normally checking the mailbox with other clients also? You could try the fetchall option, or the uidl option. Read about those in the man page. > I haven't logged a session that fails, yet, and i am hesitating to do > so since fetchmail outputs quite a lot in verbose mode and the errors > appear in unpredictable ways. We can't see what's wrong from a successful log. We can only see what's going wrong from an unsuccessful log. -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |
|
From: Rob M. <rob...@gm...> - 2005-10-10 20:40:27
|
On 10/10/05, Rouven Sacha <rs...@bl...> wrote:
> Hello List!
>
> Are there any known issues that affect using fetchmail 6.2.5.2 to pop a
> Merak Mail Server (7.4.5)? I am experiencing problems with fetchmail not
> recognizing and fetching new messages on that mail server which other
> MUA have no problem at all to see and fetch.
If you are sharing the mailbox with other mail clients then you MUST
use UIDL support.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche
|
|
From: Rouven S. <rs...@bl...> - 2005-10-10 19:55:32
|
Hello List! Are there any known issues that affect using fetchmail 6.2.5.2 to pop a Merak Mail Server (7.4.5)? I am experiencing problems with fetchmail not recognizing and fetching new messages on that mail server which other MUA have no problem at all to see and fetch. fetchmail (debian sarge binary) runs in daemon mode on my site, using the following config: set postmaster "postmaster" set bouncemail set properties "" poll mail.domain.tld uidl with proto POP3 user "us...@do...d" there with password "password" is user here options keep Fetchmails "blindness" disappears when new messages hit that mailbox. A successfull dialog looks as follows: fetchmail: POP3> CAPA fetchmail: POP3< +OK Capability list follows fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< APOP fetchmail: POP3< EXPIRE NEVER fetchmail: POP3< UIDL fetchmail: POP3< SASL CRAM-MD5 DIGEST-MD5 LOGIN PLAIN fetchmail: POP3< . fetchmail: POP3> AUTH CRAM-MD5 fetchmail: POP3< + PDIwMDUxMDEwMTk0NzM5QG1haWwucm91dGluZy5uZXQ+ fetchmail: POP3> YW5kcmVhcy5lZ25lckBsb2N6b25lLmRlIDYxMDBmY2MyMjZiNmVmMDM5YjIxYzRiNDNkNDhmYjk1 fetchmail: POP3< +OK 1 messages 10918 octets I haven't logged a session that fails, yet, and i am hesitating to do so since fetchmail outputs quite a lot in verbose mode and the errors appear in unpredictable ways. Thanks in advance, Rouven Sacha |
|
From: pongthep <pkr...@eg...> - 2005-10-01 19:41:47
|
> However, some ISPs require you to login with your email address as the > username, so you might try putting "user my...@is..." in your > fetchmailrc instead of "user myname". > > But this is all questions between you and your ISP. I've tried "user my...@is..." resulting in: fetchmail: 6.2.2 querying mail.isp.com (protocol POP3) at Sun Oct 2 00:32:28 2005: poll started fetchmail: POP3< +OK Hello there. fetchmail: POP3> CAPA fetchmail: POP3< +OK Here's what I can do: fetchmail: POP3< STLS fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< LOGIN-DELAY 10 fetchmail: POP3< PIPELINING fetchmail: POP3< UIDL fetchmail: POP3< IMPLEMENTATION Courier Mail Server fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin SSL/TLS negotiation now. fetchmail: POP3> CAPA fetchmail: POP3> USER my...@is... fetchmail: POP3> PASS fetchmail: Unknown login or authentication error on my...@is...@mail.isp.com fetchmail: POP3> QUIT fetchmail: 6.2.2 querying mail.isp.com (protocol POP3) at Sun Oct 2 00:32:29 2005: poll completed fetchmail: Query status=15 fetchmail: normal termination, status 15 "my...@is...@mail.isp.com" does not make any sense. i'm sure that my config i.e. username and password are correct. perhaps i have to be away from fetchmail, telnet can do it also. anyway, thank you very much. |
|
From: Rob F. <rf...@fu...> - 2005-09-29 15:23:51
|
pongthep wrote: > fetchmail: POP3> USER myname > fetchmail: POP3> PASS > fetchmail: Unknown login or authentication error on my...@ma... OK so either your username or password is wrong. > so it's polling my...@ma..., which is wrong. > my e-mail address is actually my...@is.... As I said, your email address doesn't matter as far as telling fetchmail the server. However, some ISPs require you to login with your email address as the username, so you might try putting "user my...@is..." in your fetchmailrc instead of "user myname". But this is all questions between you and your ISP. -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |
|
From: pongthep <pkr...@eg...> - 2005-09-29 14:40:07
|
Hello, thx for your response > Failed how? What error message do you get? % fetchmail -akv fetchmail: 6.2.2 querying mail.isp.com (protocol POP3) at Thu Sep 29 19:31:36 2005: poll started fetchmail: POP3< +OK Hello there. fetchmail: POP3> CAPA fetchmail: POP3< +OK Here's what I can do: fetchmail: POP3< STLS fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< LOGIN-DELAY 10 fetchmail: POP3< PIPELINING fetchmail: POP3< UIDL fetchmail: POP3< IMPLEMENTATION Courier Mail Server fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin SSL/TLS negotiation now. fetchmail: POP3> CAPA fetchmail: POP3> USER myname fetchmail: POP3> PASS fetchmail: Unknown login or authentication error on my...@ma... fetchmail: POP3> QUIT fetchmail: 6.2.2 querying mail.isp.com (protocol POP3) at Thu Sep 29 19:31:39 2005: poll completed fetchmail: Query status=15 fetchmail: normal termination, status 15 so it's polling my...@ma..., which is wrong. my e-mail address is actually my...@is.... |
|
From: Matthias A. <mat...@gm...> - 2005-09-28 10:20:46
|
Greetings,
if you are successfully using fetchmail with NTLM authentication against
an Exchange server, please send me, off-list (Reply-To and
Mail-Followup-To are set), the edited NTLM verbose output of "fetchmail
--nosyslog -vv" and your fetchmail version (env LC_ALL=C fetchmail -V |
head -3), and if you know it and it's not visible from the greeting
banner, the Exchange server software version.
IMPORTANT: Be sure to omit the long POP3 replies (appear in three
places, I used "..." below) and the LmResp and NTResp (each appears
once, I used "XXX LEAVE THIS OUT XXX" below), these are both sensitive
and irrelevant to me, don't take risks and edit these out.
This is the version:
This is fetchmail release 6.2.9-rc6+IMAP-GSS+RPA+NTLM+SDPS+SSL+NLS
Fallback MDA: (none)
Linux merlin 2.6.11.4-21.9-default #1 Fri Aug 19 11:58:59 UTC 2005 i686 athlon i386 GNU/Linux
And now follows is the rest I'm interested in, only the part from the
POP3 greeting until the first +OK after NTLM chat. Thanks for your
help,
Matthias
fetchmail: POP3< +OK unimail Cyrus POP3 v2.2.12 server ready <1415259226.1127895161@unimail>
fetchmail: POP3> AUTH NTLM
fetchmail: POP3< +
NTLM Request:
Ident = NTLMSSP
mType = 1
Flags = 0000b207
User = ma
Domain =
fetchmail: POP3> TlRM...
fetchmail: POP3< + TlRM...
NTLM Challenge:
Ident = NTLMSSP
mType = 2
Domain = UNIMAIL
Flags = 0002b205
Challenge = 73 fb 60 44 f9 4d c8 f4
NTLM Response:
Ident = NTLMSSP
mType = 3
LmResp = XXX LEAVE THIS OUT XXX
NTResp = XXX LEAVE THIS OUT XXX
Domain = UNIMAIL
User = ma
Wks = ma
sKey =
Flags = 0002b205
fetchmail: POP3> TlRM...
fetchmail: POP3< +OK Mailbox locked and ready
--
Matthias Andree
|
|
From: Rob F. <rf...@fu...> - 2005-09-27 17:05:43
|
pongthep wrote: > Assuming my e-mail address is my...@is... > pop3 server is mail.isp.com (notice! ``mail'' prefix) > What shall i put in ~/.fetchmailrc? What matters to fetchmail is the server name and your username there, not your email address. > poll mail.isp.com proto pop3: > user "myname" there has password "mypassword" is "mylocalname" here > mda "procmail -f %F -d %T" That looks basically correct at a glance, unless you actually used the words "myname", "mypassword", and "mylocalname". :-) > but both of them (with or without ``mail.'' prefix) failed > the command i used to invoke fetchmail is > > % fetchmail -akv Failed how? What error message do you get? -- ==============================| "A microscope locked in on one point Rob Funk <rf...@fu...> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" |
|
From: pongthep <pkr...@eg...> - 2005-09-27 16:06:10
|
Dear all, Previously i used kmail as my e-mail client, i had no problem with that. But now i only want to deal with console, and want to retrieve pop3 mails using fetchmail 6.2.2+SSL+NSL But i don't know how to configure fetchmail with pop3. Assuming my e-mail address is my...@is... pop3 server is mail.isp.com (notice! ``mail'' prefix) What shall i put in ~/.fetchmailrc? I tried both % cat ~/.fetchmailrc poll mail.isp.com proto pop3: user "myname" there has password "mypassword" is "mylocalname" here mda "procmail -f %F -d %T" and % cat ~/.fetchmailrc poll isp.com proto pop3: user "myname" there has password "mypassword" is "mylocalname" here mda "procmail -f %F -d %T" but both of them (with or without ``mail.'' prefix) failed the command i used to invoke fetchmail is % fetchmail -akv (of course, i have another ~/.procmail, which should not relate to the topic) what is the correct configuration looks like? any help would much appreciated. thx in advance, |
|
From: Matthias A. <mat...@gm...> - 2005-09-26 11:16:36
|
Greetings, The fetchmail project needs YOU - as translator. If you know your language well, spell safely, please consider helping with translating fetchmail. Translations are coordinated by the translation project, http://translation.sourceforge.net/ The procedure is simple: 1. join your language team (see above link) - it usually means subscribing to the language team's mailing list and mentioning there that you'd wish to translate fetchmail message catalogs 2. download the -rc5 tarball to get an up-to-date .pot file 3. perhaps download the .po file from the repository (ask on the fetchmail-devel list for the exact address) 4. translate -- there are powerful tools to make this easy: There is a "po-mode" for the emacs editor, and there is "kbabel", a standalone KDE application. 5. mail the translation to the translation project's robot 6. the robot will archive the translation, check it, and if complete, send a copy to the fetchmail-devel list. For the languages marked with an asterisk below, except French, we have translators. I have been updating the French translation for the nonce, but I'd rather wish that a native or very experienced (several years in a Francophone area, with some courses) speaker handled this. We have outdated translations (that means less work than a new translation) for Albanian, Danish, Galician, Greek, Japanese, Brazilian Portuguese, Slovak, Turkish. These are our current statistics, languages shipping are marked with an asterisk or plus. Those with asterisk have a translator. I will not ship the translations without asterisk unless they are updated soon. * Language ca.po: 595 translated, 9 fuzzy, 2 untranslated. * Language cs.po: 580 translated, 16 fuzzy, 10 untranslated. Language da.po: 536 translated, 57 fuzzy, 13 untranslated. * Language de.po: 606 translated. Language el.po: 536 translated, 57 fuzzy, 13 untranslated. * Language es.po: 589 translated, 13 fuzzy, 4 untranslated. + Language fr.po: 603 translated, 3 untranslated. Language gl.po: 401 translated, 94 fuzzy, 101 untranslated. Language ja.po: 515 translated, 72 fuzzy, 19 untranslated. * Language pl.po: 595 translated, 9 fuzzy, 2 untranslated. Language pt_BR.po: 401 translated, 96 fuzzy, 99 untranslated. * Language ru.po: 595 translated, 9 fuzzy, 2 untranslated. Language sk.po: 400 translated, 18 fuzzy, 178 untranslated. Language sq.po: 525 translated, 51 fuzzy, 30 untranslated. Language tr.po: 538 translated, 56 fuzzy, 12 untranslated. Regards, -- Matthias Andree |
|
From: Matthias A. <mat...@gm...> - 2005-09-26 01:10:06
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, I have just released fetchmail 6.2.9-rc5, the hopefully final release candidate before 6.3.0, after further fixes to -rc4, mainly with the build breaking but also some minor bug fixes, became necessary. - ----------------------------------------------------------------------- Fetchmail needs your support - please consider a donation via: <https://developer.berlios.de/developer/make_donation.php?user_id=2007> - ----------------------------------------------------------------------- Changes since -rc4 are: * Add full support for --service option. Matthias Andree * Fix Japanese translation of "no other fetchmail is running". Debian Bug#329342, Takeshi Hamasaki. (MA) * When getaddrinfo() fails resolving a service, log getaddrinfo() error. (MA) * Fix bogus "cannot resolve service * to port number" error. Simon Barner. (MA) * Failure to set up SSL connections now results in PS_SOCKET. Suggested by Thomas Wolff. Matthias Andree. * Kerberos IV detection fix for FreeBSD 4. Simon Barner. (MA) * Fix display and documentation of --envelope option. Matthias Andree * Make "envelope 'Delivered-To'" work with dropdelivered. Timothy Lee. (MA) * Add -DBIND_8_COMPAT to Darwin (MacOS X) compiles, to fix build problems on newer Darwin versions. Matthias Andree. * fetchmail should now automatically detect if OpenSSL requires -ldl. Matthias Andree. * Fix Solaris build with --disable-nls (blastwave.org). Matthias Andree. I seek everyone to test it out, report remaining bugs, update outdated translations (send your translated .po files to the translation project's robot, it'll forward your translation to the -devel list) or send patches for documentation or report inconsistencies (including formatting!) in the documentation. The software is available from: <https://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=7373> <http://home.pages.de/~mandree/fetchmail/> Regards, - -- Matthias Andree -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFDNy5LvmGDOQUufZURAtUnAKCSPWUaeh5MikENnzNf925HeDBjkwCfZ4xm 0he4bws7kMg+19T7y64GH1c= =X6Qr -----END PGP SIGNATURE----- |
|
From: Jakob H. <jh...@pl...> - 2005-09-21 19:04:14
|
Thomas Wolff wrote: > Also, as I had noted before, fetchmail --ssl apparently depends on > IMAPS being known to the system as a service - probably by listing it > in /etc/services. If this is not the case, getaddrinfo will fail. That's how Unix systems work and how people expect them work. > Now fetchmail seems to be the only tool that enables command line users > to set up a working mail environment on a system which is not > otherwise administrated for handling mail (together with ssmtp). There's also at least getmail and retchmail (did anybody try it?). |
18 messages has been excluded from this view by a project administrator.
