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
(3) |
Nov
|
Dec
|
From: Wade S. <wa...@wa...> - 2007-05-25 23:56:10
|
05252007 1647 GMT-6 DST I emailed recently about fetchmail not getting my gmail. What I finally did was deleting all my mail and then just keeping whatever came into the box for fetchmail to get. Today at 14:45 this happened again. I get this message in my mail log that says May 25 16:48:44 wadesmart fetchmail[25764]: 14 messages (14 seen) for wad...@gm... at pop.gmail.com (67845 octets). Of the fourteen, 12 are new, 2 are old. So it shouldnt be seeing 14. I also added "recent" to my login info as Gerard suggested. It did seem to work but now... Any more ideas? I am looking at sending google a email asking if they have any ideas. To me it seems that the number of emails isnt being counted correctly. I just do not know why. wade |
From: Wade S. <wa...@wa...> - 2007-05-18 20:24:51
|
06182007 1314 GMT-6 DST Well, I have 6.3.6ubuntu2 installed on my system. Its the latest version available through synaptic package manger. But I think your right that its gmail because I did get more of my mail overnight. Im keeping a close watch on it to see if things come through. Thanks. wade On Fri, 2007-05-18 at 07:32 +0100, Rob MacGregor wrote: > On 5/18/07, Wade Smart <wa...@wa...> wrote: > > 05172007 1850 GMT-6 DST > > > > On May 10th for some reason fetchmail stopped fetching most of the > > messages from my gmail account. It fetches some of the mail but not all. > > I dont read my gmail on the gmail server so its not showing as read. > > > > I had about 3400 messages in my gmail account but it said it has seen > > 893 of them and there are none new. So I deleted all but the newest > > ones. That left 416. Now it says it sees 1046 but none are new. > > > > This has only happened since May 10th. I looked in my system log but saw > > nothing that would indicate to me why this is happening. > > Well, it's unlikely to be something related to fetchmail I'm afraid. > > > Below is my rc file. > > > > # setup second email service provider -> Gmail > > poll pop.gmail.com > > uidl > > proto pop3 > > port 995 > > auth password > > user "wad...@gm..." there with password "pass" is "wadesmart" > > here > > keep > > no fetchall > > ssl sslcertpath /etc/ssl/certs > > All that looks fine. Can you confirm that you're on 6.3.8 and then > provide the output of "fetchmail --nosyslog --nodetach -vvv -c". > > I don't expect to find anything, as I suspect the problem is at GMail, > but it's worth a go :) > |
From: Gerard S. <ge...@se...> - 2007-05-18 12:15:23
|
On Thu, 17 May 2007 18:56:52 -0500 Wade Smart <wa...@wa...> wrote: > Below is my rc file. > > # setup second email service provider -> Gmail > poll pop.gmail.com > uidl > proto pop3 > port 995 > auth password > user "wad...@gm..." there with password "pass" is > "wadesmart" here > keep > no fetchall > ssl sslcertpath /etc/ssl/certs > > wade Try prefixing your user with 'recent'; i.e.: user "recent:wad...@gm..." there with password "pass" is "wadesmart" here See if that downloads all of your available mail. -- Gerard Fame is a vapor; popularity an accident; the only earthly certainty is oblivion. Mark Twain |
From: Rob M. <rob...@gm...> - 2007-05-18 08:34:20
|
On 5/18/07, Wade Smart <wa...@wa...> wrote: > 05172007 1850 GMT-6 DST > > On May 10th for some reason fetchmail stopped fetching most of the > messages from my gmail account. It fetches some of the mail but not all. > I dont read my gmail on the gmail server so its not showing as read. > > I had about 3400 messages in my gmail account but it said it has seen > 893 of them and there are none new. So I deleted all but the newest > ones. That left 416. Now it says it sees 1046 but none are new. > > This has only happened since May 10th. I looked in my system log but saw > nothing that would indicate to me why this is happening. Well, it's unlikely to be something related to fetchmail I'm afraid. > Below is my rc file. > > # setup second email service provider -> Gmail > poll pop.gmail.com > uidl > proto pop3 > port 995 > auth password > user "wad...@gm..." there with password "pass" is "wadesmart" > here > keep > no fetchall > ssl sslcertpath /etc/ssl/certs All that looks fine. Can you confirm that you're on 6.3.8 and then provide the output of "fetchmail --nosyslog --nodetach -vvv -c". I don't expect to find anything, as I suspect the problem is at GMail, but it's worth a go :) -- 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: Wade S. <wa...@wa...> - 2007-05-18 02:06:22
|
05172007 1850 GMT-6 DST On May 10th for some reason fetchmail stopped fetching most of the messages from my gmail account. It fetches some of the mail but not all. I dont read my gmail on the gmail server so its not showing as read. I had about 3400 messages in my gmail account but it said it has seen 893 of them and there are none new. So I deleted all but the newest ones. That left 416. Now it says it sees 1046 but none are new. This has only happened since May 10th. I looked in my system log but saw nothing that would indicate to me why this is happening. Below is my rc file. # setup second email service provider -> Gmail poll pop.gmail.com uidl proto pop3 port 995 auth password user "wad...@gm..." there with password "pass" is "wadesmart" here keep no fetchall ssl sslcertpath /etc/ssl/certs wade |
From: Rob M. <rob...@gm...> - 2007-05-16 20:15:08
|
On 5/16/07, Matthias Andree <mat...@gm...> wrote: > As far as I know, ca-roots installs one large .pem file with a gazillion of > certs and installs a softlink. > > I know from own experience that these messages do not appear for gmail.com > if I install fetchmail from an up-to-date FreeBSD ports tree under the most > recent 6.2-RELEASE-p4, but I don't know about 5.4. > > If there's anything about the default paths in 5.4's libssl different from > 6.2, then that might be the problem. It works with the defaults for me on 5.4, which means it should for any default install from ports on 5.x. However, there's nothing to say the somebody's install isn't non-default, hence my covering the bases :) AFAIK there aren't any significant path differences between FreeBSD 5.x and 6.x (or even from 4.x to 7.x) for anything installed from ports. In theory this process should work on any of those versions. -- 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: Pongthep K. <ptk...@gm...> - 2007-05-16 18:40:19
|
> So what I shall do are > - mv /usr/ports/* /somewhere/else/ > - cp /usr/share/examples/cvsup/ports-supfile /root > - vim /root/ports-supfile > - cvsup -g -L 2 /root/ports-supfile > - cd /usr/ports/mail/fetchmail > - make install > - I shall do the same with its dependencies i.e. ca-roots, gettext, gmake, libiconv as ports should not know dependency. It is a ``YES'', it is now working with no errors thanks to Matthias and Rob Pongthep Kulkrisada |
From: Matthias A. <mat...@gm...> - 2007-05-16 16:35:56
|
Rob MacGregor schrieb: > On 5/16/07, Pongthep Kulkrisada <ptk...@gm...> wrote: >> fetchmail: Server certificate verification error: unable to get local issuer certificate >> fetchmail: Server certificate verification error: certificate not trusted >> fetchmail: Server certificate verification error: unable to verify the first certificate > > Take a look at the section on "sslcertpath" in the manual. You either > need to run c_rehash (comes with OpenSSL), or tell fetchmail where to > find the certificates. As far as I know, ca-roots installs one large .pem file with a gazillion of certs and installs a softlink. I know from own experience that these messages do not appear for gmail.com if I install fetchmail from an up-to-date FreeBSD ports tree under the most recent 6.2-RELEASE-p4, but I don't know about 5.4. If there's anything about the default paths in 5.4's libssl different from 6.2, then that might be the problem. |
From: Rob M. <rob...@gm...> - 2007-05-16 16:12:32
|
On 5/16/07, Pongthep Kulkrisada <ptk...@gm...> wrote: > > > Can I skip step 1) and carry on with steps 2), 3) and 4)? > > > I have the binary of /usr/local/bin/cvsup > > > > Yup, that will be fine. > So what I shall do are > - mv /usr/ports/* /somewhere/else/ No, leave it alone. > - cp /usr/share/examples/cvsup/ports-supfile /root > - vim /root/ports-supfile > - cvsup -g -L 2 /root/ports-supfile Yes > - cd /usr/ports/mail/fetchmail > - make install Yes > - I shall do the same with its dependencies i.e. ca-roots, gettext, gmake, libiconv as ports should not know dependency. Actually, the ports *WILL* know the dependencies, though ca-roots isn't a dependency. > Nope, those 3 errors still exist. > > fetchmail: Server certificate verification error: unable to get local issuer certificate > fetchmail: Server certificate verification error: certificate not trusted > fetchmail: Server certificate verification error: unable to verify the first certificate Take a look at the section on "sslcertpath" in the manual. You either need to run c_rehash (comes with OpenSSL), or tell fetchmail where to find the certificates. -- 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: Pongthep K. <ptk...@gm...> - 2007-05-16 15:42:34
|
> > You may not have to do anything, try restarting fetchmail (or stopping > > it and running "fetchmail --nosyslog --nodetach -vvv -c" to do a mail > > check). If everything is in the expected locations then the error > > will go away. > Is it secure as intent? If so I shall follow this instruction as it is very simple. Nope, those 3 errors still exist. fetchmail: Server certificate verification error: unable to get local issuer certificate fetchmail: Server certificate verification error: certificate not trusted fetchmail: Server certificate verification error: unable to verify the first certificate thank you Pongthep Kulkrisada |
From: Pongthep K. <ptk...@gm...> - 2007-05-16 15:34:16
|
> > Can I skip step 1) and carry on with steps 2), 3) and 4)? > > I have the binary of /usr/local/bin/cvsup > > Yup, that will be fine. So what I shall do are - mv /usr/ports/* /somewhere/else/ - cp /usr/share/examples/cvsup/ports-supfile /root - vim /root/ports-supfile - cvsup -g -L 2 /root/ports-supfile - cd /usr/ports/mail/fetchmail - make install - I shall do the same with its dependencies i.e. ca-roots, gettext, gmake, libiconv as ports should not know dependency. If I'm wrong, pls correct me. > You may not have to do anything, try restarting fetchmail (or stopping > it and running "fetchmail --nosyslog --nodetach -vvv -c" to do a mail > check). If everything is in the expected locations then the error > will go away. Is it secure as intent? If so I shall follow this instruction as it is very simple. thank you Pongthep Kulkrisada |
From: Rob M. <rob...@gm...> - 2007-05-16 13:35:28
|
On 5/16/07, Kyle Contreras-Barbour <kyl...@gm...> wrote: > > I've got plenty of space (lots more than 14MB, anyway) in both /var and > /tmp. I can view it in Gmail, and what of it I've downloaded is easily > viewable in Thunderbird. It's got a few .pdf files attached to it (hence the > size). <---SNIP---> > Sadly, I don't have access to a Linux box at the moment. Maybe soon - I'm > currently having modem troubles, but hopefully they'll be fixed soon and I > can give it a shot. If you're having comms problems then, given that downloading a 14 MB file over dialup will take some time, it may be related. One option you may want to look at is making use of the 30 trial period you can use VMWare for. That would allow you to stand up a virtual Linux box to test with, which would at least allow identification as to whether or not it's a Cygwin problem. > If it is a problem with communication with ppp.gmail.com, is there much I > can do about it? Also, it occurred to me that I'm using a dial-up > connection: could that be affecting this at all (due to the length of > download times, etc., maybe some sort of timeout issue)? Sadly there's nothing you can do about problems beyond the end of your network cable :) I'd, roughly, expect (if my maths is working) a 14 MB file to take about 40 minutes over a standard dialup (nominal 48 Kb/s, nothing else going on). If you're saying your connection is unstable then you've got a good window for problems to occur. -- 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: Kyle Contreras-B. <kyl...@gm...> - 2007-05-16 12:55:35
|
On 5/14/07, Rob MacGregor <rob...@gm... > wrote: > > That suggests a problem with the communication with the remote host > (ppp.gmail.com). However, it wouldn't hurt to check some of the > basics: > > 1) Do you have at least 14 MB of free space in /var (and possibly /tmp)? 2) Can you view this email via GMail? Can another mail client (say, > Thunderbird) view this email? > <snip> > > If you can get exim working it wouldn't hurt to remove the MDA line > and get some log info. I suspect it won't show anything useful > though. > > If you want to avoid fetchmail trying to download this email you can > use the "limit" directive to tell it to skip emails above a certain > size. See "Resource Limit Control Options" in the man page for > details. > <snip> > On 5/14/07, Jason Tishler < ja...@ti...> wrote: > You can enable verbose procmail logging by adding "VERBOSE=yes" to the > command line: > > mda "/usr/bin/procmail VERBOSE=yes -d %T" > <snip> > However, can you try this from a non-Cygwin host (e.g., Linux) > to rule out a Cygwin specific problem? > When running procmail with VERBOSE=yes, it outputs (snoutwood being my login): procmail: [588] Wed May 16 03:11:27 2007 procmail: Couldn't read "/home/snoutwood/-d" procmail: Locking "/var/spool/mail/snoutwood.lock" procmail: Assigning "LASTFOLDER=/var/spool/mail/snoutwood" procmail: Opening "/var/spool/mail/snoutwood" procmail: Acquiring kernel-lock procmail: [588] Wed May 16 03:11:28 2007 procmail: Unlocking "/var/spool/mail/snoutwood.lock" Subject: Camera manuals Folder: /var/spool/mail/snoutwood 1839916 When I removed the mda line and ran exim, /var/log/exim/exim_main.log looked like this: 2007-05-16 03:28:39 exim 4.66 daemon started: pid=852, -q15m, listening for SMTP on port 25 (IPv4) 2007-05-16 03:28:39 Start queue run: pid=1232 2007-05-16 03:28:39 End queue run: pid=1232 2007-05-16 03:40:03 SMTP connection from localhost (finnegan) [127.0.0.1] lost while reading message data I've got plenty of space (lots more than 14MB, anyway) in both /var and /tmp. I can view it in Gmail, and what of it I've downloaded is easily viewable in Thunderbird. It's got a few .pdf files attached to it (hence the size). I'll definitely use the size limit if I can't get it through somehow - seems like that's the best workaround if need be. It'd be nice to be able to grab the message with fetchmail, though. Sadly, I don't have access to a Linux box at the moment. Maybe soon - I'm currently having modem troubles, but hopefully they'll be fixed soon and I can give it a shot. If it is a problem with communication with ppp.gmail.com, is there much I can do about it? Also, it occurred to me that I'm using a dial-up connection: could that be affecting this at all (due to the length of download times, etc., maybe some sort of timeout issue)? Again, thanks for all the help! Kyle |
From: Rob M. <rob...@gm...> - 2007-05-15 18:00:59
|
On 5/15/07, Pongthep Kulkrisada <ptk...@gm...> wrote: > It should be kinda encryption, my password or messages are encoded and can't be read by any intermediate persons. And only the server has an algorithm to decode it. So nobody can steal my password or messages. If I'm wrong, pls correct me. Well sort of. Only your connection to the remote server is encrypted by SSL/TLS. The email will make its way to the server unencrypted and is stored in the clear on the server, so it is only the last hop that you're protecting. Of course, that does protect your username and password, if you are using PLAIN or LOGIN authentication. If you can it is better to use one of the stronger methods, but that's down to what the remote POP/IMAP server supports (and what you have compiled into fetchmail) > Can I skip step 1) and carry on with steps 2), 3) and 4)? > I have the binary of /usr/local/bin/cvsup Yup, that will be fine. > But I only use text mode no GUI. Never used the GUI version so I can assure you that is ok. > I still question. > after updating port and make install under /usr/ports/security/ca-roots, > what shall i do next with my .fetchmailrc? You may not have to do anything, try restarting fetchmail (or stopping it and running "fetchmail --nosyslog --nodetach -vvv -c" to do a mail check). If everything is in the expected locations then the error will go away. > BTW I shall read fetchmail(1) anyway, but I can say that it is very hard for noobies to understand. That is something others have said and I have already said that, when I have the time, I will help the project re-write it. Having a one year old child means I have little free time :) -- 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: Pongthep K. <ptk...@gm...> - 2007-05-15 17:48:16
|
> Ok, simply, as root: > > 1) pkg_add -r cvsup-without-gui There were some error messages. # pkg_add -r cvsup_without_gui pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/cvsup-without-gui.tbz' by URL Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/cvsup-without-gui.tbz: File unavailable (e.g., file not found, no access) > 2) cp /usr/share/examples/cvsup/ports-supfile /root > 3) vi /root/ports-supfile > (or use your favourite text editor, if you're not comfortable with any do: > sed "s/CHANGE_THIS/cvsup3/" /root/ports-supfile > /root/my-ports-supfile > mv /root/my-ports-supfile /root/ports-supfile I used vim and very familiar with it, but I can't do pkg_add, see above. > 4) cvsup /root/ports-supfile > Repeat command (4) when you're expecting to install or update software > - at most daily. > > I'd recommend portsnap instead personally, but cvsup is easier to get > going with initially (pre FreeBSD 6). Don't overlook help from the > various freebsd mailing lists (including freebsd-questions) - people > there are generally helpful. > > The FreeBSD manual goes into more detail: > > http://www.freebsd.org/doc/handbook/ports-using.html > > It is available in more than English, but I not many and I don't know > what languages you read. Thank you very much, BTW I can read English but not natively. But I can't read too long, I currently have the problem with my eyes. My doctor told me to reduce reading or using computer. > > What is root certificate? please give me a bit of more details. > > I'd suggest a look at the Wikipedia article for "ssl certificate" as > without knowing how much you know there's a risk of making it too > simple (and boring you) or assuming too much (and confusing you) :-) > > http://en.wikipedia.org/wiki/Ssl_certificate#Security > > (very) briefly a certificate is a way of being certain that a host is > what it claims to be (eg mail.google.com). There are different types, > with a root certificate being able of validating other certificates. > > > Can you please give me a brief example of --sslcertck? I did not find it in the provided handbook or man pages. > > It *is* detailed in at least the online manual: > > http://www.fetchmail.info/fetchmail-man.html Once I have skimmed thru these documents while I was configuring gmail account. so many things to learn. Anyway I started to understand. Thank you, It should be kinda encryption, my password or messages are encoded and can't be read by any intermediate persons. And only the server has an algorithm to decode it. So nobody can steal my password or messages. If I'm wrong, pls correct me. > > Shall I just cd /usr/ports/security/ca-roots and make install? > > Yes, but update your ports first. > > > How to obtain the new version? > > See the details on use of cvsup above. Can I skip step 1) and carry on with steps 2), 3) and 4)? I have the binary of /usr/local/bin/cvsup But I only use text mode no GUI. That should be the case of cvsup_without_gui. I don't know. I still question. after updating port and make install under /usr/ports/security/ca-roots, what shall i do next with my .fetchmailrc? BTW I shall read fetchmail(1) anyway, but I can say that it is very hard for noobies to understand. Thanks again, Pongthep Kulkrisada |
From: Matthias A. <mat...@gm...> - 2007-05-14 20:46:51
|
Rob MacGregor schrieb: > It *is* detailed in at least the online manual: > > http://www.fetchmail.info/fetchmail-man.html ...which I have just updated to version 6.3.8. |
From: Rob M. <rob...@gm...> - 2007-05-14 20:34:08
|
On 5/14/07, Pongthep Kulkrisada <ptk...@gm...> wrote: > > Pongthep, the easiest way for FreeBSD installations of fetchmail is to use > > the FreeBSD port - but your installation went apparently right anyways, > > except for the SSL certificates. > I dont know about SSL certificates. > Once I just cd /usr/ports/mail/fetchmail and make install. It brought me the old version. I don't know how to use cvsup. Once I read handbook, it came with tonnes of documentation, I just don't understand only confuse I got. So I downloaded a tarball and compiled from source. I am a noobie. Ok, simply, as root: 1) pkg_add -r cvsup-without-gui 2) cp /usr/share/examples/cvsup/ports-supfile /root 3) vi /root/ports-supfile (or use your favourite text editor, if you're not comfortable with any do: sed "s/CHANGE_THIS/cvsup3/" /root/ports-supfile > /root/my-ports-supfile mv /root/my-ports-supfile /root/ports-supfile 4) cvsup /root/ports-supfile Repeat command (4) when you're expecting to install or update software - at most daily. I'd recommend portsnap instead personally, but cvsup is easier to get going with initially (pre FreeBSD 6). Don't overlook help from the various freebsd mailing lists (including freebsd-questions) - people there are generally helpful. The FreeBSD manual goes into more detail: http://www.freebsd.org/doc/handbook/ports-using.html It is available in more than English, but I not many and I don't know what languages you read. > What is root certificate? please give me a bit of more details. I'd suggest a look at the Wikipedia article for "ssl certificate" as without knowing how much you know there's a risk of making it too simple (and boring you) or assuming too much (and confusing you) :-) http://en.wikipedia.org/wiki/Ssl_certificate#Security (very) briefly a certificate is a way of being certain that a host is what it claims to be (eg mail.google.com). There are different types, with a root certificate being able of validating other certificates. > Can you please give me a brief example of --sslcertck? I did not find it in the provided handbook or man pages. It *is* detailed in at least the online manual: http://www.fetchmail.info/fetchmail-man.html > Shall I just cd /usr/ports/security/ca-roots and make install? Yes, but update your ports first. > How to obtain the new version? See the details on use of cvsup above. -- 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: Pongthep K. <ptk...@gm...> - 2007-05-14 18:35:43
|
> Pongthep, the easiest way for FreeBSD installations of fetchmail is to use > the FreeBSD port - but your installation went apparently right anyways, > except for the SSL certificates. I dont know about SSL certificates. Once I just cd /usr/ports/mail/fetchmail and make install. It brought me the old version. I don't know how to use cvsup. Once I read handbook, it came with tonnes of documentation, I just don't understand only confuse I got. So I downloaded a tarball and compiled from source. I am a noobie. > The problem is with the server's certificate that your OpenSSL library does > not recognize - installing the root certificate should fix your problem. What is root certificate? please give me a bit of more details. > > Questions > > 1) My first account has nothing to do with TLS. > > Why is there such an error message? How to fix it? > > You can avoid the attempts if you add > sslproto '' > > to your configuration (that's two single quotes) Yes it fixed the problem. Thanks > > 2) Several errors with my second account (gmail). > > How to fix it? > > See below. > > > 3) I also have 6bone tunnel for IPv6. > > Shall I do anything special with fetchmail? > > There should be no need; FreeBSD 5.4 can do IPv6 as far as I know. Alright. Thanks, > The server offered TLS, so fetchmail tried. However, the server is not > configured properly ("opportunistic upgrade to TLS failed") and > additionally dropped the connection. > > Fetchmail noticed and retried without TLS. This is typical Courier > behavior. I'll talk to Sam Varshavchik if he sees a chance to fix this. > > Suggestion above (sslproto ''). As said it fixed the problem. > Looks as though the root certificate from Equifax is not installed on your > computer, so the OpenSSL library cannot verify that there is no man in the > middle attack going on. Fetchmail continues however (because you did not > specify --sslcertck). Can you please give me a brief example of --sslcertck? I did not find it in the provided handbook or man pages. > Do you have the ca-roots port installed? Try doing that, it makes the > problem go away on my computer (I have FreeBSD 6.2 and installed fetchmail > 6.3.8 from the port). Shall I just cd /usr/ports/security/ca-roots and make install? How to obtain the new version? Thank you very much Pongthep Kulkrisada |
From: Jason T. <ja...@ti...> - 2007-05-14 15:56:12
|
On Mon, May 14, 2007 at 02:39:06PM +0100, Rob MacGregor wrote: > On 5/14/07, Kyle Contreras-Barbour <kyl...@gm...> wrote: > > There isn't anything around that other than nearly identical "start > > queue run" and "end queue run" lines. Based on your comments here > > and the addition of 'mda "/usr/bin/procmail -d %T"' to my > > .fetchmailrc I'm guessing that I'm not actually using exim. > > I suspect you're right, which makes diagnosing this more difficult (I > don't know if there is any way to get logging info out of procmail). You can enable verbose procmail logging by adding "VERBOSE=yes" to the command line: mda "/usr/bin/procmail VERBOSE=yes -d %T" > [snip] > > fetchmail: about to deliver with: /usr/bin/procmail -d 'snoutwood' > > #<snip 250+ lines of asterisks> > > fetchmail: socket error while fetching from kyl...@gm... > > @pop.gmail.com > <---SNIP---> > > That suggests a problem with the communication with the remote host > (ppp.gmail.com). Agreed. However, can you try this from a non-Cygwin host (e.g., Linux) to rule out a Cygwin specific problem? Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 |
From: Rob M. <rob...@gm...> - 2007-05-14 15:41:29
|
On 5/14/07, Kyle Contreras-Barbour <kyl...@gm...> wrote: > > Sorry... I'm not meaning to be difficult. That's ok :) > There isn't anything around that > other than nearly identical "start queue run" and "end queue run" lines. > Based on your comments here and the addition of 'mda "/usr/bin/procmail -d > %T"' to my .fetchmailrc I'm guessing that I'm not actually using exim. I suspect you're right, which makes diagnosing this more difficult (I don't know if there is any way to get logging info out of procmail). > O.K. Here's my current .fetchmailrc: > > poll " pop.gmail.com" > protocol pop3 > service 995 > username "kyl...@gm..." > password "<password>" > ssl > keep > mda "/usr/bin/procmail -d %T" Looks ok, there's certainly nothing there that'll cause a problem. <---SNIP---> > fetchmail: POP3< +OK message follows > reading message kyl...@gm...@gmail-pop.l.google.com:293 of 649 > (14003782 octets) > About to rewrite From: Kyle Contreras-Barbour <kyl...@gm...> > Rewritten version is From: Kyle Contreras-Barbour < kyl...@gm...> > > About to rewrite To: "Kyle (me)" <kyl...@gm...> > Rewritten version is To: "Kyle (me)" < kyl...@gm...> > > fetchmail: about to deliver with: /usr/bin/procmail -d 'snoutwood' > #<snip 250+ lines of asterisks> > fetchmail: socket error while fetching from kyl...@gm... > @pop.gmail.com <---SNIP---> That suggests a problem with the communication with the remote host (ppp.gmail.com). However, it wouldn't hurt to check some of the basics: 1) Do you have at least 14 MB of free space in /var (and possibly /tmp)? 2) Can you view this email via GMail? Can another mail client (say, Thunderbird) view this email? If you can get exim working it wouldn't hurt to remove the MDA line and get some log info. I suspect it won't show anything useful though. If you want to avoid fetchmail trying to download this email you can use the "limit" directive to tell it to skip emails above a certain size. See "Resource Limit Control Options" in the man page for details. -- 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: Kyle Contreras-B. <kyl...@gm...> - 2007-05-14 15:22:31
|
On 5/14/07, Rob MacGregor <rob...@gm... > wrote: > > > Farther back than this, there's some entries such as this one: > > > > 2007-05-12 14:35:22 SMTP connection from localhost (<hostname>) [127.0.0.1 > ] > > lost while reading message data > > What else is there around this? Your careful snipping of the logs > makes it impossible to help you - we need context! Sorry... I'm not meaning to be difficult. There isn't anything around that other than nearly identical "start queue run" and "end queue run" lines. Based on your comments here and the addition of 'mda "/usr/bin/procmail -d %T"' to my .fetchmailrc I'm guessing that I'm not actually using exim. What I/we need to see is the output of "fetchmail --nosyslog > --nodetach -vvv" for the problem email AND the entries from your exim > log (assuming you're delivering via exim) for that point in time. We > also really need to see the contents of your .fetchmailrc (passwords > obscured). O.K. Here's my current .fetchmailrc: poll "pop.gmail.com" protocol pop3 service 995 username "kyl...@gm..." password "<password>" ssl keep mda "/usr/bin/procmail -d %T" And here's the output of "fetchmail --nosyslog --nodetach -vvv": $ fetchmail --nosyslog --nodetach -vvv fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Mon May 14 05:53:57 2007: poll started Trying to connect to 64.233.167.111/995...connected. fetchmail: Issuer Organization: Equifax fetchmail: Unknown Issuer CommonName fetchmail: Server CommonName: pop.gmail.com fetchmail: pop.gmail.com key fingerprint: 59:51:61:89:CD:DD:B2:35:94:BB:44:97:A0:39:D5:B4 fetchmail: Server certificate verification error: unable to get local issuer certificate fetchmail: Server certificate verification error: certificate not trusted fetchmail: Server certificate verification error: unable to verify the first certificate fetchmail: POP3< +OK Gpop ready for requests from 66.81.40.23f79pf3475397pyh fetchmail: POP3> CAPA fetchmail: POP3< +OK Capability list follows fetchmail: POP3< USER fetchmail: POP3< RESP-CODES fetchmail: POP3< EXPIRE 0 fetchmail: POP3< LOGIN-DELAY 300 fetchmail: POP3< X-GOOGLE-VERHOEVEN fetchmail: POP3< UIDL fetchmail: POP3< . fetchmail: POP3> USER kyl...@gm... fetchmail: POP3< +OK send PASS fetchmail: POP3> PASS * fetchmail: POP3< +OK Welcome. fetchmail: selecting or re-polling default folder fetchmail: POP3> STAT fetchmail: POP3< +OK 649 21915850 fetchmail: POP3> LAST fetchmail: POP3< -ERR Not supported fetchmail: Not supported fetchmail: POP3> UIDL fetchmail: POP3< +OK fetchmail: POP3< 1 GmailId106fbe14f6cfa650 <snip lines nearly identical to the above, counting from 2 to 292> fetchmail: POP3< 293 GmailId10869d8a1ae0cca0 fetchmail: 293 is unseen fetchmail: POP3< 294 GmailId1086cfbf8ea6c5dc fetchmail: 294 is unseen <snip lines nearly identical to the two above, counting from 295 to 648> fetchmail: POP3< 649 GmailId109d6cd4d6ef150d fetchmail: 649 is unseen fetchmail: POP3< . 649 messages (292 seen) for kyl...@gm... at pop.gmail.com (21915850 octets). skipping message kyl...@gm...@gmail-pop.l.google.com:1 not flushed skipping message kyl...@gm...@gmail-pop.l.google.com:2 not flushed <snip> skipping message kyl...@gm...@gmail-pop.l.google.com:292 not flushed fetchmail: POP3> LIST 293 fetchmail: POP3< +OK 293 14003782 fetchmail: POP3> RETR 293 fetchmail: POP3< +OK message follows reading message kyl...@gm...@gmail-pop.l.google.com:293 of 649 (14003782 octets) About to rewrite From: Kyle Contreras-Barbour <kyl...@gm...> Rewritten version is From: Kyle Contreras-Barbour <kyl...@gm...> About to rewrite To: "Kyle (me)" <kyl...@gm...> Rewritten version is To: "Kyle (me)" <kyl...@gm...> fetchmail: about to deliver with: /usr/bin/procmail -d 'snoutwood' #<snip 250+ lines of asterisks> fetchmail: socket error while fetching from kyl...@gm...@ pop.gmail.com fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Mon May 14 06:07:08 2007: poll completed fetchmail: discarding new UID list fetchmail: Query status=2 (SOCKET) fetchmail: Writing fetchids file. fetchmail: normal termination, status 2 fetchmail: Writing fetchids file. Thanks, Kyle |
From: Rob M. <rob...@gm...> - 2007-05-14 10:41:19
|
On 5/14/07, Kyle Contreras-Barbour <kyl...@gm...> wrote: > > I'm happy to post it - it's rather large, so here's a snippet. Let me know > if more (or a specific segment) would be helpful. > > 2007-05-13 20:59:25 Start queue run: pid=1596 > 2007-05-13 20:59:25 End queue run: pid=1596 <---SNIP many near identical lines---> If that truely is the related entries from your exim log then it would suggest you've either got some very broken logging, or you're not actually using exim. I'd expect to see some lines relating to the receipt of the problem email. > Farther back than this, there's some entries such as this one: > > 2007-05-12 14:35:22 SMTP connection from localhost (<hostname>) [127.0.0.1] > lost while reading message data What else is there around this? Your careful snipping of the logs makes it impossible to help you - we need context! What I/we need to see is the output of "fetchmail --nosyslog --nodetach -vvv" for the problem email AND the entries from your exim log (assuming you're delivering via exim) for that point in time. We also really need to see the contents of your .fetchmailrc (passwords obscured). -- 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: Kyle Contreras-B. <kyl...@gm...> - 2007-05-14 09:04:07
|
On 5/13/07, Jason Tishler <ja...@ti...> wrote: > > You don't need to use exim or another MTA, if you are only interested in > local mail delivery. If so, then you may want to model your fetchmail > configuration after mine which delivers via procmail: > > <snip> > I've put that into my rc file now, but I'm still getting socket errors at the same point, at the 14MB e-mail. It could be a problem related to your exim config (14 MB is pretty > large for an email). The contents of the exim log would be useful to > further diagnose, though from the snippet above it doesn't appear to > be a fetchmail problem. > I'm happy to post it - it's rather large, so here's a snippet. Let me know if more (or a specific segment) would be helpful. 2007-05-13 20:59:25 Start queue run: pid=1596 2007-05-13 20:59:25 End queue run: pid=1596 2007-05-13 21:14:26 Start queue run: pid=1640 2007-05-13 21:14:26 End queue run: pid=1640 2007-05-13 21:29:26 Start queue run: pid=1660 2007-05-13 21:29:26 End queue run: pid=1660 2007-05-13 21:44:27 Start queue run: pid=1720 2007-05-13 21:44:27 End queue run: pid=1720 2007-05-13 21:59:28 Start queue run: pid=1064 2007-05-13 21:59:28 End queue run: pid=1064 2007-05-13 22:14:47 Start queue run: pid=1208 2007-05-13 22:14:48 End queue run: pid=1208 2007-05-13 22:30:06 Start queue run: pid=1660 2007-05-13 22:30:06 End queue run: pid=1660 2007-05-13 22:45:06 Start queue run: pid=1460 2007-05-13 22:45:06 End queue run: pid=1460 2007-05-13 23:00:06 Start queue run: pid=1208 2007-05-13 23:00:06 End queue run: pid=1208 2007-05-13 23:15:07 Start queue run: pid=1208 2007-05-13 23:15:07 End queue run: pid=1208 2007-05-13 23:30:07 Start queue run: pid=1440 2007-05-13 23:30:07 End queue run: pid=1440 2007-05-13 23:45:07 Start queue run: pid=868 2007-05-13 23:45:07 End queue run: pid=868 Farther back than this, there's some entries such as this one: 2007-05-12 14:35:22 SMTP connection from localhost (<hostname>) [127.0.0.1] lost while reading message data Again, thanks for all the help in figuring this out. Kyle |
From: Jason T. <ja...@ti...> - 2007-05-14 02:42:17
|
Kyle, On Sat, May 12, 2007 at 11:03:18PM +0100, Rob MacGregor wrote: > On 5/12/07, Kyle Contreras-Barbour <kyl...@gm...> wrote: > > 6.3.8 and 3.22, respectively, according to setup.exe). > > > > I did indeed need to get exim running, it seems (thanks!) - I ran > > exim-config to get the daemon going and when I ran fetchmail, > > instead of giving "connection to localhost failed" it happily > > connected. However, it's still having certificate verification > > errors (I don't know if that's a big issue or not) and terminating > > with a socket error. This is what it's showing at the end: > > Not a big deal. Agreed, I get the same error messages when I fetch from gmail too. > > It's been getting stuck at the same message, which appears to be > > fairly large (14003782 octets), so I'm starting to wonder if there > > isn't some issue there. Before it hits that message, it's giving > > this: > > > > [snip] > > It could be a problem related to your exim config (14 MB is pretty > large for an email). The contents of the exim log would be useful to > further diagnose, though from the snippet above it doesn't appear to > be a fetchmail problem. You don't need to use exim or another MTA, if you are only interested in local mail delivery. If so, then you may want to model your fetchmail configuration after mine which delivers via procmail: poll "pop.gmail.com" protocol pop3 username "${USER}@gmail.com" password "${PASSWORD}" fetchall ssl nokeep mda "/usr/bin/procmail -d %T" where ${USER} and ${PASSWORD} are as appropriate. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 |
From: Matthias A. <mat...@gm...> - 2007-05-13 17:12:09
|
Pongthep Kulkrisada schrieb: > Hi all > > Error messages with fetchmail 6.3.8 > Firstly I shall say I am a noobie and sorry if my question is too simple > Previously I use fetchmail 6.2.5 on FreeBSD 5.4 (yes obsolete but still get work done). I had no problem with it. In order to be updated, yesterday I downloaded fetchmail 6.3.8. I installed it as I normally do. Pongthep, the easiest way for FreeBSD installations of fetchmail is to use the FreeBSD port - but your installation went apparently right anyways, except for the SSL certificates. > After test, I can still retrieve mails for both accounts, but I found some error messages I never seen before and don't know how to fix it. Anyone has a clue, please point me out and thank you in advance. (please also CC to me, I'm not in the list.) The problem is with the server's certificate that your OpenSSL library does not recognize - installing the root certificate should fix your problem. > Normally I use mutt as MUA. But for your diagnostic, I put direct command on console as shown below. > > Questions > 1) My first account has nothing to do with TLS. > Why is there such an error message? How to fix it? You can avoid the attempts if you add sslproto '' to your configuration (that's two single quotes) > 2) Several errors with my second account (gmail). > How to fix it? See below. > 3) I also have 6bone tunnel for IPv6. > Shall I do anything special with fetchmail? There should be no need; FreeBSD 5.4 can do IPv6 as far as I know. > % fetchmail -vv Thank you. > fetchmail: 6.3.8 querying mail.ego.co.th (protocol POP3) at Sun May 13 11:08:42 2007: poll started > Trying to connect to 202.5.93.197/110...connected. > 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: mail.ego.co.th: opportunistic upgrade to TLS failed, trying to continue. > fetchmail: POP3> USER pkr...@eg... > fetchmail: Repoll immediately on pkr...@eg...@mail.ego.co.th > Trying to connect to 202.5.93.197/110...connected. The server offered TLS, so fetchmail tried. However, the server is not configured properly ("opportunistic upgrade to TLS failed") and additionally dropped the connection. Fetchmail noticed and retried without TLS. This is typical Courier behavior. I'll talk to Sam Varshavchik if he sees a chance to fix this. Suggestion above (sslproto ''). > fetchmail: 6.3.8 querying mail.ego.co.th (protocol POP3) at Sun May 13 11:08:44 2007: poll completed > fetchmail: not swapping UID lists, no UIDs seen this query > fetchmail: Query status=1 (NOMAIL) > fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Sun May 13 11:08:44 2007: poll started > Trying to connect to 72.14.253.109/995...connected. > fetchmail: Issuer Organization: Equifax > fetchmail: Unknown Issuer CommonName > fetchmail: Server CommonName: pop.gmail.com > fetchmail: pop.gmail.com key fingerprint: 59:51:61:89:CD:DD:B2:35:94:BB:44:97:A0:39:D5:B4 > fetchmail: Server certificate verification error: unable to get local issuer certificate > fetchmail: Server certificate verification error: certificate not trusted > fetchmail: Server certificate verification error: unable to verify the first certificate Looks as though the root certificate from Equifax is not installed on your computer, so the OpenSSL library cannot verify that there is no man in the middle attack going on. Fetchmail continues however (because you did not specify --sslcertck). Do you have the ca-roots port installed? Try doing that, it makes the problem go away on my computer (I have FreeBSD 6.2 and installed fetchmail 6.3.8 from the port). HTH Matthias |