Please, cut me some slack. It's not my web-client. I didn't install it. And I'm not going to switch
ISPs to get a better web client. End of story.
Anyway, I know about fetchmailconf, so thanks for nothing. The reason I asked for an example is
because earlier in this SuSE install I WAS using fetchmail, but it was deleting emails (only
certain ones) that it wasn't supposed to be deleting. So certain email messages weren't getting
through. I used fetchmailconf to configure it and still it wasn't working right so I was hoping to
see a nice working example of a good .fetchmailrc example because I know about fetchmailconf, I
know how to RTFM, I know how to Google and still I can't come up with a .fetchmailrc file that
doesn't kill certain email messages for some odd reason.
Preston
----- Original Message -----
From: Patrick Shanahan
To: suse-linux-e@suse.com
Sent: Thu, 8 Jul 2004 20:41:14 -0500
Subject: Re: [SLE]
* me@prestoncrawford.com
If someone wants to forward a nice .fetchmailrc example I'll gladly take it.
If it will help get you to stop top-posting and full-quoting, yes. fetchmailconf is a tk-based gui configuration editor for fetchmail. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
* me@prestoncrawford.com
Please, cut me some slack. It's not my web-client. I didn't install it. And I'm not going to switch ISPs to get a better web client. End of story.
Plenty of slack available. We will byass that you cannot edit your quotes or are forced to top post
Anyway, I know about fetchmailconf, so thanks for nothing.
You are welcome
The reason I asked for an example is because earlier in this SuSE install I WAS using fetchmail, but it was deleting emails (only certain ones) that it wasn't supposed to be deleting. So certain email messages weren't getting through. I used fetchmailconf to configure it and still it wasn't working right so I was hoping to see a nice working example of a good .fetchmailrc example because I know about fetchmailconf, I know how to RTFM, I know how to Google and still I can't come up with a .fetchmailrc file that doesn't kill certain email messages for some odd reason.
example set logfile "/path-to/fetchmail.log" set postmaster "who-ever-you-want" set bouncemail set spambounce set properties "v" set daemon 150 poll pop-server.your.isp with proto POP3 timeout 60 user 'your-log-on-name' there with password 'your-password' is 'your-name-on-your-computer' here options fetchall stripcr mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554 this if for pop3, change to your required protocol (you didn't say). If you want to leave the mail on the server, add following with the set statements at the begining: set keep This has been working for me for over ten years. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 09 July 2004 04:24, Patrick Shanahan wrote:
example
set logfile "/path-to/fetchmail.log" set postmaster "who-ever-you-want" set bouncemail set spambounce set properties "v"
What is "v" for? man fetchmail does not tell that.
set daemon 150
poll pop-server.your.isp with proto POP3 timeout 60 user 'your-log-on-name' there with password 'your-password' is 'your-name-on-your-computer' here options fetchall stripcr mda '/usr/lib/sendmail -i -oem -f %F %T' antispam 571 550 501 554
Cheers, Leen
* Leendert Meyer
set properties "v"
What is "v" for? man fetchmail does not tell that.
?? man fetchmail General Options ... -v | --verbose Verbose mode. All control messages passed between fetchmail and the mailserver are echoed to stdout. Overrides --silent. Doubling this option (-v -v) causes extra diagnostic information to be printed. This is fetchmail release 6.2.3+POP2+RPA+NTLM+SDPS+SSL+OPIE+NLS fetchmail-6.2.3-28 -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 09 July 2004 17:09, Patrick Shanahan wrote:
* Leendert Meyer
[07-09-04 09:32]: set properties "v"
What is "v" for? man fetchmail does not tell that.
?? man fetchmail
set properties String value is ignored by fetchmail (may be used by extension scripts) *** Later on in the manpage: The `properties' option is an extension mechanism. It takes a string argument, which is ignored by fetchmail itself. The string argument may be used to store configuration information for scripts which require it. In particular, the output of `--configdump' option will make properties associated with a user entry readily available to a Python script.
General Options ... -v | --verbose Verbose mode. All control messages passed between fetchmail and the mailserver are echoed to stdout. Overrides --silent. Doubling this option (-v -v) causes extra diagnostic information to be printed.
Yes, found that. Couldn't find any association between set properties and (setting) general options.
This is fetchmail release 6.2.3+POP2+RPA+NTLM+SDPS+SSL+OPIE+NLS fetchmail-6.2.3-28
This is fetchmail release 6.2.5+POP2+RPA+NTLM+SDPS+SSL+OPIE+NLS Cheers, Leen
* Leendert Meyer
Couldn't find any association between set properties and (setting) general options.
TTTT, I believe that I originally used someone else's config as a templet and probably did not pay enought attention to all of the settings in haste to achieve operation. I have had that rc file for a long time, only making changes to the lower portion 8-(. Thanks for the info (should have spent more time RTFM myself 8-) ). -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
On Friday 09 July 2004 17:47, Patrick Shanahan wrote:
* Leendert Meyer
[07-09-04 10:25]: Couldn't find any association between set properties and (setting) general options.
TTTT, I believe that I originally used someone else's config as a templet and probably did not pay enought attention to all of the settings in haste to achieve operation. I have had that rc file for a long time, only making changes to the lower portion 8-(.
Thanks for the info (should have spent more time RTFM myself 8-) ).
LOL! (you had 10 years to do that!) Never mind. ;P Thanks, Leen
On 2004-07-09 03:51, me@prestoncrawford.com wrote: [No subject? :-O]
because earlier in this SuSE install I WAS using fetchmail, but it was deleting emails (only certain ones) that it wasn't supposed to be deleting. So certain email messages weren't getting through.
I reported a similar behaviour time ago on this list; when an email has
what fetchmail considers a broken header, the version in SuSE 8.2
didn't download it and left it at the server. The next version of the
program (fetchmail-6.2.5), which is the one SuSE 9.1 is using, I think
tries the download, complains, and then erases the email (both locally
and at the server).
This behaviour I noticed with a 6.2.5 I compiled myself, I don't know
about the one supplied by SuSE.
The thread where we talked about this was:
Subject: Re: [SLE] fetchmail - Version 6.2.5
Date: 2004-02-02 21:18
From: "Carlos E. R."
To: suse-linux-e@
X-Message-Number-for-archive: 178455
[...]
I can confirm that this is indeed ocurring now with the version shipped
with SuSE 9.1 - just search your logs for "incorrect header line":
Jul 8 02:00:34 nimrodel fetchmail[15462]: POP3> LIST 61
Jul 8 02:00:34 nimrodel fetchmail[15462]: POP3< +OK 61 1148
Jul 8 02:00:34 nimrodel fetchmail[15462]: POP3> RETR 61
Jul 8 02:00:34 nimrodel fetchmail[15462]: POP3< +OK 1148 bytes
Jul 8 02:00:34 nimrodel fetchmail[15462]: reading message ****tiscali.
es:61 of 124 (1148 octets)
Jul 8 02:00:34 nimrodel fetchmail[15462]: incorrect header line found
while scanning headers
Jul 8 02:00:34 nimrodel fetchmail[15462]: line: ----
9160626280983045335^M
Jul 8 02:00:34 nimrodel fetchmail[15462]: flushed
Jul 8 02:00:34 nimrodel fetchmail[15462]: POP3> DELE 61
This is indeed a lost email, there is no "RCPT TO" part as in a normal
email:
Jul 8 02:00:35 nimrodel fetchmail[15462]: reading message
*****tiscali.es:62 of 124 (2513 octets)
Jul 8 02:00:35 nimrodel fetchmail[15462]: SMTP> MAIL FROM:
On Fri, 2004-07-09 at 05:44, Carlos E. R. wrote:
On 2004-07-09 03:51, me@prestoncrawford.com wrote:
[No subject? :-O]
Yeah, don't know how that happened. Like I said, I have a funky web-based client that my ISP provides. It functions, but apparently not well.
because earlier in this SuSE install I WAS using fetchmail, but it was deleting emails (only certain ones) that it wasn't supposed to be deleting. So certain email messages weren't getting through.
The recomended solution, in my opinion, is to downgrade fetchmail :-/
Else, somebody patches fetchmail.
Thanks for confirming that I'm not nuts. The emails that were being deleted were from just one person, also using a web-based email client. So perhaps her emails were being munged or somehow incorrectly produced and they'd slip through fine with Evolution, but fetchmail would kill them. I'm trying to find this in my logs, but I can't find the correct log so far. Thanks, though, for the confirmation that perhaps fetchmail is at fault in this case. How did you downgrade it? i.e. What version did you roll back to? Preston
The Friday 2004-07-09 at 07:32 -0700, Preston Crawford wrote:
The recomended solution, in my opinion, is to downgrade fetchmail :-/
Else, somebody patches fetchmail.
Thanks for confirming that I'm not nuts. The emails that were being deleted were from just one person, also using a web-based email client. So perhaps her emails were being munged or somehow incorrectly produced and they'd slip through fine with Evolution, but fetchmail would kill them. I'm trying to find this in my logs, but I can't find the correct log so far.
grep "incorrect header line" /var/log/mail | less zgrep "incorrect header line" /var/log/mail*gz | less
Thanks, though, for the confirmation that perhaps fetchmail is at fault in this case. How did you downgrade it? i.e. What version did you roll back to?
I haven't done that yet, I have so many things going on, after upgrading from SuSE 8.2 to 9.1 (real life aside), that till I saw your message and searched the logs I was not aware that SuSE 9.1 had that version of fetchmail. I did my testing with SuSE 8.2, where the version included worked correctly (well, not quite), but I tried to upgrade to 6.2.5, compiling it myself, and then noticed that problem. I mean, I did not downgrade, but upgrade - and then noticed the problem. I will probably get the sources from the SuSE 8.2 DVD and downgrade to fetchmail-6.2.1-25. I don't expect problems in the downgrade, except one: those mails with "incorrect header line" will be left on the server, not downloaded. Or perhaps I'll investigate the sources... but don't count on it :-) Also, I think I will investigate that "getmail" that Preston says. And, there is "animail", but I'm not fully convinced about that one (not so feature rich). -- Cheers, Carlos Robinson
On Sun, 2004-07-11 at 17:19, Carlos E. R. wrote:
I will probably get the sources from the SuSE 8.2 DVD and downgrade to fetchmail-6.2.1-25. I don't expect problems in the downgrade, except one: those mails with "incorrect header line" will be left on the server, not downloaded.
Thanks for the tip on this. Like I said, I downgraded with the last "gold" sources from Fetchmail's site and everything is working perfect. So you won't be subjected to my horrid headers ever again. :-) Sorry for the inconvenience. Thanks for the help, Carlos. Preston
On Fri, 2004-07-09 at 05:44, Carlos E. R. wrote:
The recomended solution, in my opinion, is to downgrade fetchmail :-/
Else, somebody patches fetchmail.
Okay. I found the "gold" version, 6.2.0, and compiled it. I'll have people email me and see how it goes. Thanks. Let me know, though, if this version worked for you or if you had to downgrade further. Preston
Hi Preston, On Fri, 09 Jul 2004 07:49:12 -0700 UTC (7/9/2004, 9:49 AM -0500 UTC my time), Preston Crawford wrote:
The recomended solution, in my opinion, is to downgrade fetchmail :-/
Else, somebody patches fetchmail.
P> Okay. I found the "gold" version, 6.2.0, and compiled it. I'll have P> people email me and see how it goes. Thanks. Let me know, though, if P> this version worked for you or if you had to downgrade further. Like everything else in Linux, you have choices. The better choice is getmail.. written in python, fast, easy to set up, secure. Never had a security problem like fetchmail... It just works. http://www.qcc.ca/~charlesc/software/getmail-3.0/ -- Gary
On Fri, 2004-07-09 at 08:12, Gary wrote:
Hi Preston,
On Fri, 09 Jul 2004 07:49:12 -0700 UTC (7/9/2004, 9:49 AM -0500 UTC my time), Preston Crawford wrote:
The recomended solution, in my opinion, is to downgrade fetchmail :-/
Else, somebody patches fetchmail.
P> Okay. I found the "gold" version, 6.2.0, and compiled it. I'll have P> people email me and see how it goes. Thanks. Let me know, though, if P> this version worked for you or if you had to downgrade further.
Like everything else in Linux, you have choices. The better choice is getmail.. written in python, fast, easy to set up, secure. Never had a security problem like fetchmail... It just works.
Huh. Never heard of getmail until today. Can anyone else vouch for it? Not that I don't trust you, Gary. :-) Just never heard of it before, thus don't know how good it is. Whereas fetchmail (at least used to be) tried and true, you know. Maybe I'll give it a whirl either way. Does it drop stuff in a typical Mail directory in mbox format like fetchmail? Asking since I use pine when I do remote email over SSH. Preston
Hi Preston, Sorry, I inadvertently sent this to you directly instead of the list; trying out a new MUA, and it has its quirks... On Fri, 09 Jul 2004 08:34:09 -0700 UTC (7/9/2004, 10:34 AM -0500 UTC my time), Preston Crawford wrote:
Like everything else in Linux, you have choices. The better choice is getmail.. written in python, fast, easy to set up, secure. Never had a security problem like fetchmail... It just works.
P> Huh. Never heard of getmail until today. Can anyone else vouch for it? P> Not that I don't trust you, Gary. :-) there is nothing to vouch for. Google, it won an award a couple of years ago, and the author is well known, *professional* qmail administrator / open source software author.. In other words, he knows his __.. http://www.qcc.ca/~charlesc/software/getmail-3.0/getmail.html#summary P> Just never heard of it before, thus don't know how good it is. Whereas P> fetchmail (at least used to be) tried and true, you know. so has this... save yourself a headache, and just try it. It is a hell of a lot safer, more secure than fetchmail... I turned Bruce Marshall on to it a few years ago, and some others... Don't know if Bruce still uses it. P> Maybe I'll give it a whirl either way. Does it drop stuff in a typical P> Mail directory in mbox format like fetchmail? Asking since I use pine P> when I do remote email over SSH. Yes, read the FAQs for your answers... it will even filter. See summary above and FAQs. http://www.qcc.ca/~charlesc/software/getmail-3.0/faq.html#faq -- Gary
On Thursday 08 July 2004 09:51 pm, me@prestoncrawford.com wrote:
Please, cut me some slack. It's not my web-client. I didn't install it. And I'm not going to switch ISPs to get a better web client. End of story.
Anyway, I know about fetchmailconf, so thanks for nothing. The reason I asked for an example is because earlier in this SuSE install I WAS using fetchmail, but it was deleting emails (only certain ones) that it wasn't supposed to be deleting. So certain email messages weren't getting through. I used fetchmailconf to configure it and still it wasn't working right so I was hoping to see a nice working example of a good .fetchmailrc example because I know about fetchmailconf, I know how to RTFM, I know how to Google and still I can't come up with a .fetchmailrc file that doesn't kill certain email messages for some odd reason.
Might they be spam?? A different fetcmailrc won't fix that problem.. Some spam emails are broken to the point that it is best to delete them. They really can't be fetched. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 07/09/04 09:26 + +----------------------------------------------------------------------------+ "Horse sense is the thing a horse has which keeps it from betting on people." - W.C. Fields
On Fri, 2004-07-09 at 06:27, Bruce Marshall wrote:
Google and still I can't come up with a .fetchmailrc file that doesn't kill certain email messages for some odd reason.
Might they be spam?? A different fetcmailrc won't fix that problem.. Some spam emails are broken to the point that it is best to delete them. They really can't be fetched.
No. The emails that were getting lost were emails from a client. Important emails. And strangely they weren't even getting dropped into the spam folder (I do use SpamAssassin when at home using Evolution) at home. But they weren't getting picked up by fetchmail. Very weird. They wouldn't get picked up by fetchmail, then they'd be gone from the servers. Preston
participants (7)
-
Bruce Marshall
-
Carlos E. R.
-
Gary
-
Leendert Meyer
-
me@prestoncrawford.com
-
Patrick Shanahan
-
Preston Crawford