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
(24) |
Nov
(14) |
Dec
|
|
From: Rob M. <rob...@gm...> - 2007-03-28 18:01:06
|
On 3/28/07, Kramer, Barbara <B.K...@nu...> wrote: > Hi, > There is a mailbox on an exchange server, named NTBV-shipment. This box is > receiving mail. I want to fetch the mail there and bring it to my HPUX, > where the file will be read into a software. I chose to use fetchmail. > > Just installed fetchmail on my hp server with hpux 11.11 on it. > I have done the following: > * Created a user named podeliv > * Started a mail box for him /var/mail/podeliv > * Send mail to him through sendmail - mail podeliv - mail was received > ok So we know the basics of your sendmail config are good. > * Logged on as podeliv and send a mail to my mail account - which is > an exchange server - mail kam ok and sender is po...@nu... > * Installed ixFetchmail A.08.00-6.3.6 for HPUX 11.11 - all went well Close enough to current (6.3.7 is current). > * Created a .fetchmailrc for user podeliv, which reads: > > set logfile /home/podeliv/fetch.log > poll pnw2k01.pfrimmer.de > proto pop3 port 110 > user pfrimmer\\NTBV-shipment > there has password ******* > no keep > > * Fetch.log is being filled with entries, when I do fetchmail -av, as > user podeliv > * Now the problem: - I always read message SMTP< 501 Sender domain > must exist - podeliv is always being shown as podeliv@localhost > From my Mail Delivery System [MAI...@er...], which is > root on the hpux machine: > podeliv@localhost > SMTP error: 501 Sender domain must exist > What did I forget to do? Not sure, because... > Attached you'll find the fetch.log, after I had send a mail to > NTBV-shipment, as user podeliv I did fetchmail -av <<fetch.log>> No log attached. -- 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: Kramer, B. <B.K...@nu...> - 2007-03-28 17:03:00
|
Hi, There is a mailbox on an exchange server, named NTBV-shipment. This box is receiving mail. I want to fetch the mail there and bring it to my HPUX, where the file will be read into a software. I chose to use fetchmail. Just installed fetchmail on my hp server with hpux 11.11 on it. I have done the following: * Created a user named podeliv * Started a mail box for him /var/mail/podeliv * Send mail to him through sendmail - mail podeliv - mail was received ok * Logged on as podeliv and send a mail to my mail account - which is an exchange server - mail kam ok and sender is po...@nu... * Installed ixFetchmail A.08.00-6.3.6 for HPUX 11.11 - all went well * Created a .fetchmailrc for user podeliv, which reads: set logfile /home/podeliv/fetch.log poll pnw2k01.pfrimmer.de proto pop3 port 110 user pfrimmer\\NTBV-shipment there has password ******* no keep * Fetch.log is being filled with entries, when I do fetchmail -av, as user podeliv * Now the problem: - I always read message SMTP< 501 Sender domain must exist - podeliv is always being shown as podeliv@localhost From my Mail Delivery System [MAI...@er...], which is root on the hpux machine: podeliv@localhost SMTP error: 501 Sender domain must exist What did I forget to do? Attached you'll find the fetch.log, after I had send a mail to NTBV-shipment, as user podeliv I did fetchmail -av <<fetch.log>> Can anyone help me? That would be super - already read all kinds of stuff online about hosts, hostsequiv, changed sendmail.cf, sendmail.cw, restarted sendmail numerous times, yet all did not help. Thanks in advance Barbara PRIVACY: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or priviliged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Thank you. |
|
From: Christian E. <bla...@gm...> - 2007-03-28 14:30:40
|
* Peter Pentchev on Monday, March 26, 2007 at 18:40:08 +0300: > On Mon, Mar 26, 2007 at 06:16:51PM +0300, Peter Pentchev wrote: >> On Mon, Mar 26, 2007 at 02:48:22PM +0000, Rob MacGregor wrote: >>> 1) Have your mail server listen on IPv6 loopback >>> 2) Disable IPv6 on your host >>> 3) Edit your /etc/hosts and comment out the IPv6 loopback >>> >>> I don't believe there is any way in fetchmail to tell it not to use >>> IPv6. I think your only option is to either ensure that your SMTP >>> server listens on IPv6 or disable IPv6 (or at least the lookup), with >>> the first being the cleanest approach IMO. >>> >>> You could also simply specify the smtphost as 127.0.0.1. Potentially dangerous with postfix -- if, like me you don't know the parameters you'd have to change there ;) >> And, of course, >> >> 4) Edit your /etc/hosts, add another alias for 127.0.0.1 and specify that >> as fetchmail's smtphost. That's what I'm doing now, and also added the alias to postfix' $mydestination. Thanks. c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
|
From: Joe A. <jo...@j4...> - 2007-03-26 20:53:47
|
Matthias Andree <mat...@gm...> Wrote on: 3/26/2007 12:47 PM: > Joe Acquisto schrieb: >> Maybe not the correct place to post this, but I am told this information is >> no longer accurate: >> >> ********************************************** >> http://www.fetchmail.info/fetchmail-FAQ.html#F3 >> >> "S4. How can I use fetchmail with Novell GroupWise? >> >> The Novell GroupWise IMAP server would be better named GroupFoolish; it is >> (according to the designer of IMAP) unusably broken. Among other things, it >> doesn't include a required content length in its BODY[TEXT] response. >> >> Fetchmail works around this problem, but we strongly recommend voting with >> your dollars for a server that isn't brain-dead." >> ********************************************** > > So in what respect is it sill broken, in what respect has it been fixed > by Novell, and what is the oldest version that talks proper IMAP? > > TIA > MA I've no idea, myself. I am forwarding a copy of this to a GW admin's list, hoping for an answer. joe a. |
|
From: Christian E. <bla...@gm...> - 2007-03-26 19:05:00
|
* Peter Pentchev on Monday, March 26, 2007 at 18:40:08 +0300: > On Mon, Mar 26, 2007 at 06:16:51PM +0300, Peter Pentchev wrote: >> On Mon, Mar 26, 2007 at 02:48:22PM +0000, Rob MacGregor wrote: >>> On 3/26/07, Christian Ebert <bla...@gm...> wrote: >>>> Trying to connect to ::1/25...connection failed. >>>> fetchmail: connection to localhost:smtp [::1/25] failed: Connection refused. >>>> Trying to connect to 127.0.0.1/25...connected. >>> <---SNIP---> >>> >>> 1) Have your mail server listen on IPv6 loopback >>> 2) Disable IPv6 on your host >>> 3) Edit your /etc/hosts and comment out the IPv6 loopback >>> >>> I don't believe there is any way in fetchmail to tell it not to use >>> IPv6. I think your only option is to either ensure that your SMTP >>> server listens on IPv6 or disable IPv6 (or at least the lookup), with >>> the first being the cleanest approach IMO. >>> >>> You could also simply specify the smtphost as 127.0.0.1. >> >> And, of course, >> >> 4) Edit your /etc/hosts, add another alias for 127.0.0.1 and specify that >> as fetchmail's smtphost. Then I also loose mail, with specifying a port as well. Might be due to some postfix config, or to Apple's /etc/hostconfig: $ cat /etc/hostconfig ## # /etc/hostconfig ## # This file is maintained by the system control panels ## # Network configuration HOSTNAME=krille.blacktrash.org ROUTER=-AUTOMATIC- # Services AFPSERVER=-NO- AUTHSERVER=-NO- AUTOMOUNT=-YES- CUPS=-YES- IPFORWARDING=-NO- IPV6=-YES- MAILSERVER=-YES- NETINFOSERVER=-AUTOMATIC- NFSLOCKS=-AUTOMATIC- NISDOMAIN=-NO- RPCSERVER=-AUTOMATIC- TIMESYNC=-YES- QTSSERVER=-NO- WEBSERVER=-YES- SMBSERVER=-NO- DNSSERVER=-NO- COREDUMPS=-NO- VPNSERVER=-NO- CRASHREPORTER=-YES- ARDAGENT=-NO- Probably I could unset ipv6 there, but I'd prefer not to. Probably the best bet is to upgrade postfix -- once I find the time. Thanks for the advice though. c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
|
From: Matthias A. <mat...@gm...> - 2007-03-26 18:49:25
|
Joe Acquisto schrieb: > Maybe not the correct place to post this, but I am told this information is no longer accurate: > > ********************************************** > http://www.fetchmail.info/fetchmail-FAQ.html#F3 > > "S4. How can I use fetchmail with Novell GroupWise? > > The Novell GroupWise IMAP server would be better named GroupFoolish; it is (according to the designer of IMAP) unusably broken. Among other things, it doesn't include a required content length in its BODY[TEXT] response. > > Fetchmail works around this problem, but we strongly recommend voting with your dollars for a server that isn't brain-dead." > ********************************************** So in what respect is it sill broken, in what respect has it been fixed by Novell, and what is the oldest version that talks proper IMAP? TIA MA |
|
From: Rob F. <rf...@fu...> - 2007-03-26 17:56:33
|
Peter Pentchev wrote: > since the berlios server seems to dislike > multipart/signed messages containing a text/plain part and > an application/pgp-signature part: I've just fixed that. -- ==============================| "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: Peter P. <ro...@ri...> - 2007-03-26 17:42:01
|
On Mon, Mar 26, 2007 at 06:16:51PM +0300, Peter Pentchev wrote: > On Mon, Mar 26, 2007 at 02:48:22PM +0000, Rob MacGregor wrote: > > On 3/26/07, Christian Ebert <bla...@gm...> wrote: > > > Hello, > > > > > > When polling, fetchmail gives the following warning after the > > > first message: > > > > > > Trying to connect to ::1/25...connection failed. > > > fetchmail: connection to localhost:smtp [::1/25] failed: Connection refused. > > > Trying to connect to 127.0.0.1/25...connected. > > <---SNIP---> > > > Otherwise everything is working fine, I just wanted to know > > > whether there's an "innocent" way to get rid of this warning? > > > > 1) Have your mail server listen on IPv6 loopback > > 2) Disable IPv6 on your host > > 3) Edit your /etc/hosts and comment out the IPv6 loopback > > > > I don't believe there is any way in fetchmail to tell it not to use > > IPv6. I think your only option is to either ensure that your SMTP > > server listens on IPv6 or disable IPv6 (or at least the lookup), with > > the first being the cleanest approach IMO. > > > > You could also simply specify the smtphost as 127.0.0.1. > ...resending my own reply, since the berlios server seems to dislike multipart/signed messages containing a text/plain part and an application/pgp-signature part: > And, of course, > > 4) Edit your /etc/hosts, add another alias for 127.0.0.1 and specify that > as fetchmail's smtphost. G'luck, Peter -- Peter Pentchev ro...@ri... ro...@cn... ro...@Fr... PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence would be seven words long if it were six words shorter. |
|
From: Christian E. <bla...@gm...> - 2007-03-26 17:17:22
|
* Rob MacGregor on Monday, March 26, 2007 at 14:48:22 +0000: > On 3/26/07, Christian Ebert <bla...@gm...> wrote: >> When polling, fetchmail gives the following warning after the >> first message: >> >> Trying to connect to ::1/25...connection failed. >> fetchmail: connection to localhost:smtp [::1/25] failed: Connection refused. >> Trying to connect to 127.0.0.1/25...connected. > <---SNIP---> >> Otherwise everything is working fine, I just wanted to know >> whether there's an "innocent" way to get rid of this warning? > > 1) Have your mail server listen on IPv6 loopback > 2) Disable IPv6 on your host > 3) Edit your /etc/hosts and comment out the IPv6 loopback > > I don't believe there is any way in fetchmail to tell it not to use > IPv6. I think your only option is to either ensure that your SMTP > server listens on IPv6 or disable IPv6 (or at least the lookup), with > the first being the cleanest approach IMO. I'd have to upgrade postfix then; might do that some day. > You could also simply specify the smtphost as 127.0.0.1. I exprimented with that, but then, judging from the log, the mails were dispatched to my relayserver (by postfix?), bounced there due to missing envelope, and were lost (luckily only test mails). Might be because my postfix setup is a bit complicated as I am using ClamSmtpd. So I guess I'll just tolerate the warnings until I upgrade postfix. Thanks for answering. c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
|
From: Joe A. <jo...@j4...> - 2007-03-26 17:13:30
|
Maybe not the correct place to post this, but I am told this information is no longer accurate: ********************************************** http://www.fetchmail.info/fetchmail-FAQ.html#F3 "S4. How can I use fetchmail with Novell GroupWise? The Novell GroupWise IMAP server would be better named GroupFoolish; it is (according to the designer of IMAP) unusably broken. Among other things, it doesn't include a required content length in its BODY[TEXT] response. Fetchmail works around this problem, but we strongly recommend voting with your dollars for a server that isn't brain-dead." ********************************************** I am far from an IMAP expert. joe a. |
|
From: Rob M. <rob...@gm...> - 2007-03-26 16:50:15
|
On 3/26/07, Christian Ebert <bla...@gm...> wrote:
> Hello,
>
> When polling, fetchmail gives the following warning after the
> first message:
>
> Trying to connect to ::1/25...connection failed.
> fetchmail: connection to localhost:smtp [::1/25] failed: Connection refused.
> Trying to connect to 127.0.0.1/25...connected.
<---SNIP--->
> Otherwise everything is working fine, I just wanted to know
> whether there's an "innocent" way to get rid of this warning?
1) Have your mail server listen on IPv6 loopback
2) Disable IPv6 on your host
3) Edit your /etc/hosts and comment out the IPv6 loopback
I don't believe there is any way in fetchmail to tell it not to use
IPv6. I think your only option is to either ensure that your SMTP
server listens on IPv6 or disable IPv6 (or at least the lookup), with
the first being the cleanest approach IMO.
You could also simply specify the smtphost as 127.0.0.1.
--
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: Christian E. <bla...@gm...> - 2007-03-26 12:38:07
|
Hello, When polling, fetchmail gives the following warning after the first message: Trying to connect to ::1/25...connection failed. fetchmail: connection to localhost:smtp [::1/25] failed: Connection refused. Trying to connect to 127.0.0.1/25...connected. I believe this is due to the ipv6 loopback interface in my /etc/hosts: $ cat /etc/hosts ## # Host Database # # localhost is used to configure the loopback interface # when the system is booting. Do not change this entry. ## 127.0.0.1 localhost krille.blacktrash.org ::1 localhost krille.blacktrash.org 255.255.255.255 broadcasthost Otherwise everything is working fine, I just wanted to know whether there's an "innocent" way to get rid of this warning? $ fetchmail -V This is fetchmail release 6.3.8-rc2+SSL. Copyright (C) 2002, 2003 Eric S. Raymond Copyright (C) 2004 Matthias Andree, Eric S. Raymond, Rob F. Funk, Graham Wilson Copyright (C) 2005-2006 Sunil Shetye Copyright (C) 2005-2007 Matthias Andree Fetchmail comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For details, please see the file COPYING in the source or documentation directory. Fallback MDA: (none) Darwin krille.blacktrash.org 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc Taking options from command line and /Users/chris/.fetchmailrc Idfile is /Users/chris/.fetchids Fetchmail will show progress dots even in logfiles. Fetchmail will forward misaddressed multidrop messages to chris. Options for retrieving from *******@pop.gmx.net: True name of server is pop.gmx.net. Protocol is POP3 (forcing UIDL use). Password authentication will be forced. SSL encrypted sessions enabled. SSL key fingerprint (checked against the server key): ************* Server nonresponse timeout is 60 seconds. Default mailbox selected. All messages will be retrieved (--all on). Fetched messages will not be kept on the server (--keep off). Old messages will not be flushed before message retrieval (--flush off). Oversized messages will not be flushed before message retrieval (--limitflush off). Rewrite of server-local addresses is enabled (--norewrite off). Carriage-return stripping is enabled (stripcr on). 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 3 out of 4 polls (--fastuidl 4). Messages will be SMTP-forwarded to: localhost (default) Single-drop mode: 1 local name recognized. No UIDs saved from this host. TIA c -- _B A U S T E L L E N_ lesen! --->> <http://www.blacktrash.org/baustellen.html> |
|
From: Rob M. <rob...@gm...> - 2007-03-26 08:07:59
|
On 3/26/07, Joe Acquisto <jo...@j4...> wrote:
>
> Ah. Well. Point taken. This is a SUSE SLES 9 install with their provided
> version of fetchmail.
Which could be any version, but fortunately that isn't important.
> The startup script does show it is looking for /etc/fetchmailrc. But, it seems I recall clearly
> that I got this running, logged in as root, only after creating .fetchmailrc in root's home.
>
> fetchmailconfig did that, I believe.
Just keep in mind that any vaguely modern version of fetchmail will
warn you about running as root and future versions will refuse to run.
> I supposed that during system startup the script at /etc/init.d will run (called via /etc/init.d/rc(x).d) while saying "fetchmail" while logged in, does the deed via /usr/sbin/fetchmail. ?
If I understand you correctly, yes. I'd suggest you take a look at
the init script yourself to see what it does and how.
--
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: Joe A. <jo...@j4...> - 2007-03-26 02:11:33
|
"Rob MacGregor" <rob...@gm...> Wrote: 3/25/2007 4:19 PM: > On 3/25/07, Joe Acquisto <jo...@j4...> wrote: >> My first foray into fetchmail. Seem to have configured it properly, by >> some happenstance. Even runs at system startup, as if I know what I was >> doing. And that is certainly not certain. >> >> However, I am given pause. I am a bit puzzled how one can specify an >> alternate startup file, within the startup file (--fetchmailrc = >> path/file). A circular argument kind of thing. >> >> When I first started it (fetchmail, via system startup) it complained (from >> logs) that it could not find /etc/fetchmailrc. Thinking that a typo, and >> having an "aha" moment regarding my above pondering, I copied my >> /root/.fetchmailrc to /etc/. Alas, it still complained, so I renamed it, >> leaving off the leading ".". >> >> Now it seems to be quite happy reading /etc/fetchmailrc. But I am not >> certain why. Or if it is only reading that to find the "real" config file. >> I hesitate to start hacking to find out, as it takes several minutes for >> this older Dell Poweredge to start up. Boring. > > My crystal ball tells me you're probably running some form of Linux > and have some version of fetchmail installed, possibly from a binary > package... > > Seriously, if you want help you need to provide information. At the > very least you need to fill in the blanks above. Ah. Well. Point taken. This is a SUSE SLES 9 install with their provided version of fetchmail. > Now, if you're running Linux then you'll most likely find the startup > script as /etc/init.d/fetchmail. If you look at that script you'll > find what your package provider has set as the defaults for that > build. The startup script does show it is looking for /etc/fetchmailrc. But, it seems I recall clearly that I got this running, logged in as root, only after creating .fetchmailrc in root's home. fetchmailconfig did that, I believe. I supposed that during system startup the script at /etc/init.d will run (called via /etc/init.d/rc(x).d) while saying "fetchmail" while logged in, does the deed via /usr/sbin/fetchmail. ? One learns by doing. joe a. |
|
From: Rob M. <rob...@gm...> - 2007-03-25 22:21:27
|
On 3/25/07, Joe Acquisto <jo...@j4...> wrote:
> My first foray into fetchmail. Seem to have configured it properly, by some happenstance. Even runs at system startup, as if I know what I was doing. And that is certainly not certain.
>
> However, I am given pause. I am a bit puzzled how one can specify an alternate startup file, within the startup file (--fetchmailrc = path/file). A circular argument kind of thing.
>
> When I first started it (fetchmail, via system startup) it complained (from logs) that it could not find /etc/fetchmailrc. Thinking that a typo, and having an "aha" moment regarding my above pondering, I copied my /root/.fetchmailrc to /etc/. Alas, it still complained, so I renamed it, leaving off the leading ".".
>
> Now it seems to be quite happy reading /etc/fetchmailrc. But I am not certain why. Or if it is only reading that to find the "real" config file. I hesitate to start hacking to find out, as it takes several minutes for this older Dell Poweredge to start up. Boring.
My crystal ball tells me you're probably running some form of Linux
and have some version of fetchmail installed, possibly from a binary
package...
Seriously, if you want help you need to provide information. At the
very least you need to fill in the blanks above.
Now, if you're running Linux then you'll most likely find the startup
script as /etc/init.d/fetchmail. If you look at that script you'll
find what your package provider has set as the defaults for that
build.
Oh, and when any program complains about the lack of a given file,
it's unlikely to be a typo :)
--
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: Joe A. <jo...@j4...> - 2007-03-25 22:10:48
|
My first foray into fetchmail. Seem to have configured it properly, by some happenstance. Even runs at system startup, as if I know what I was doing. And that is certainly not certain. However, I am given pause. I am a bit puzzled how one can specify an alternate startup file, within the startup file (--fetchmailrc = path/file). A circular argument kind of thing. When I first started it (fetchmail, via system startup) it complained (from logs) that it could not find /etc/fetchmailrc. Thinking that a typo, and having an "aha" moment regarding my above pondering, I copied my /root/.fetchmailrc to /etc/. Alas, it still complained, so I renamed it, leaving off the leading ".". Now it seems to be quite happy reading /etc/fetchmailrc. But I am not certain why. Or if it is only reading that to find the "real" config file. I hesitate to start hacking to find out, as it takes several minutes for this older Dell Poweredge to start up. Boring. Thanks for any assistance. joe a. |
|
From: Matthias A. <mat...@gm...> - 2007-03-25 17:03:40
|
"Rob MacGregor" <rob...@gm...> writes: > I'd be tempted to go with your second paragraph - if fetchmail is > linked with the socks libraries *and* the required socks config file > is in place then, by default, use socks. As long as there is a > command line argument to either disable socks or use an alternative > socks config file (which implicitly enables socks) then that should be > fine. I have decided to do exactly that, even if it causes pain to those who experiment with socks -- IOW, if you leave shards lying around, wear tough shoes. >> Not my essay, and I'm not enthusiastic about several of the assumptions >> fetchmail makes, and I'm still pondering whether a complete redesign is >> more of an effort than rewriting existing code... > > Which is more effort to maintain :) Need not be your concern though. 8-) > It probably wouldn't hurt for the --configdump option to include the > fact that socks is compiled in - which, in theory, is little more > than: > > #ifdef HAVE_SOCKS > "'socks'," > #endif > > after line 186 of conf.c Done for 6.3.8. Thanks for the report. -- Matthias Andree |
|
From: Chris <cpo...@ea...> - 2007-03-22 11:55:50
|
On Thursday 22 March 2007 2:00 am, Rob MacGregor wrote: > On 3/22/07, Chris <cpo...@ea...> wrote: > > I think though that the key may be the "socket error while fetching from > > cpo...@po...". It appears to my untrained eye that the > > connection was dropped while fetching this particular message? > > Yes, and if it (the dropping of the connection upon issuing the DEL > command) happens each time with the same email then I'd suspect that > their POP server is badly broken. Everything at Earthlink is badly broken, mail, usenet, techsupport and so forth. > > > I also see, I > > think, how UIDL comes into play. Each message is assigned a unique ID. > > For instance, the 'bad' message above has an UIDL of 1huc3u2DT3Nl36v1, > > and looking at the .fetchids file I see cpo...@po... > > 1huc3u2DT3Nl36v1. Once I delete that message from the server the > > .fetchids file is removed since all messages have been downloaded. Makes > > sense. > > Glad it's all working for you. Me too Rob, and thanks very much for your help. I've the FAQ bookmarked now and if/when I have another problem thats the very *first* place I'll check for a solution. -- Chris KeyID 0xE372A7DA98E6705C |
|
From: Rob M. <rob...@gm...> - 2007-03-22 08:01:46
|
On 3/22/07, Chris <cpo...@ea...> wrote:
> I think though that the key may be the "socket error while fetching from
> cpo...@po...". It appears to my untrained eye that the
> connection was dropped while fetching this particular message?
Yes, and if it (the dropping of the connection upon issuing the DEL
command) happens each time with the same email then I'd suspect that
their POP server is badly broken.
> I also see, I
> think, how UIDL comes into play. Each message is assigned a unique ID. For
> instance, the 'bad' message above has an UIDL of 1huc3u2DT3Nl36v1, and
> looking at the .fetchids file I see cpo...@po...
> 1huc3u2DT3Nl36v1. Once I delete that message from the server the .fetchids
> file is removed since all messages have been downloaded. Makes sense.
Glad it's all working for you.
--
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: Chris <cpo...@ea...> - 2007-03-22 02:39:19
|
On Wednesday 21 March 2007 5:54 pm, Rob MacGregor wrote: > On 3/21/07, Chris <cpo...@ea...> wrote: > > Robb, I tried replying to this last night, when I got home from work > > today I had this: > > > > The message's content type was not explicitly allowed > > > > Along with the signed message I'd sent encapsulated. I guess signed > > messages are no longer allowed? > > There's been a problem of people sending HTML only emails to the list > lately, resulting in the allowed types being clamped down on. If you > can did out the MIME type for the signed email I'll see about adding > it to the list of allowed types. I'll have to see if I can figure it out. This is probably not it but according to Kmail its OpenPGP/MIME. > > > Anyway, here is what I sent: > > > > Thanks Rob, I'll have to wait until another message gets stuck on the > > server at earthlink to send the output. I did change logging from syslog > > to a seperate fetchmaillog file, that should make things easier when it > > happens again. I've also enabled uidl. One probably dumb question though, > > when you say "don't use "-m procmail" but deliver directly to your SMTP > > server" what do you mean? > > Well, by default fetchmail will try to connect to an SMTP on loopback. > If you're running an SMTP server > (sendmail/postfix/exim/qmail/whatever) then you can have fetchmail > just pass the email on to it. > > (If that's equally as clear as mud let me know - it's getting a late here > :>) I have courier-imap running and have Kmail setup using an IMAP account. Procmail tosses into the maildir folders I have setup. -- Chris KeyID 0xE372A7DA98E6705C |
|
From: Rob M. <rob...@gm...> - 2007-03-21 23:56:31
|
On 3/21/07, Chris <cpo...@ea...> wrote:
>
> Robb, I tried replying to this last night, when I got home from work today I
> had this:
>
> The message's content type was not explicitly allowed
>
> Along with the signed message I'd sent encapsulated. I guess signed messages
> are no longer allowed?
There's been a problem of people sending HTML only emails to the list
lately, resulting in the allowed types being clamped down on. If you
can did out the MIME type for the signed email I'll see about adding
it to the list of allowed types.
> Anyway, here is what I sent:
>
> Thanks Rob, I'll have to wait until another message gets stuck on the server
> at earthlink to send the output. I did change logging from syslog to a
> seperate fetchmaillog file, that should make things easier when it happens
> again. I've also enabled uidl. One probably dumb question though, when you
> say "don't use "-m procmail" but deliver directly to your SMTP server" what
> do you mean?
Well, by default fetchmail will try to connect to an SMTP on loopback.
If you're running an SMTP server
(sendmail/postfix/exim/qmail/whatever) then you can have fetchmail
just pass the email on to it.
(If that's equally as clear as mud let me know - it's getting a late here :>)
--
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: Chris <cpo...@ea...> - 2007-03-21 23:51:49
|
On Wednesday 21 March 2007 2:04 am, Rob MacGregor wrote: > On 3/21/07, Chris <cpo...@ea...> wrote: > > I reported this back on the 11th of March, since then I've upgraded to > > what I understand is the latest version. Looking at the required > > information for a problem in the FAQ I'll try to provide it: > > Thanks for all that. Typically there was still one thing that the FAQ > doesn't ask for that would have helped :) Can you provide the output > of "fetchmail -v -v -v -m procmail" for the problem email (that > should, hopefully, show what's happening). > > You may find that enabling UIDL support helps as it moves to problem > of tracking seen emails from the server to fetchmail. > > It may be that the problem will go away if you don't use "-m procmail" > but deliver directly to your SMTP server, but that's just a guess. Robb, I tried replying to this last night, when I got home from work today I had this: The message's content type was not explicitly allowed Along with the signed message I'd sent encapsulated. I guess signed messages are no longer allowed? Anyway, here is what I sent: Thanks Rob, I'll have to wait until another message gets stuck on the server at earthlink to send the output. I did change logging from syslog to a seperate fetchmaillog file, that should make things easier when it happens again. I've also enabled uidl. One probably dumb question though, when you say "don't use "-m procmail" but deliver directly to your SMTP server" what do you mean? Chris -- Chris KeyID 0xE372A7DA98E6705C |
|
From: Rob M. <rob...@gm...> - 2007-03-21 21:16:01
|
On 3/21/07, Santa Clause <fu...@ho...> wrote:
> HI
> Please could you let me know if the following is possiable and how to do it.
>
> I am using fetchmail to download email from a "catchall account" at our isp.
> I want to know if it is possiable to block / delete a user when it is
> downloaded by fetchmail. The user must still be able to send and receive
> mail on the local server.
I'm not sure what you're asking.
As you asking - is it possible to stop a user directly connecting to
the remote POP server?
That, and the configuration of your local mail server, is nothing to
do with fetchmail. To achieve that you'll need to configure your
firewall to only allow the host running fetchmail access to the POP
server.
--
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: Santa C. <fu...@ho...> - 2007-03-21 17:39:43
|
HI Please could you let me know if the following is possiable and how to do it. I am using fetchmail to download email from a "catchall account" at our isp. I want to know if it is possiable to block / delete a user when it is downloaded by fetchmail. The user must still be able to send and receive mail on the local server. This is my fetchmail.cron file (Runs every 10min) fetchmail -f /etc/fetchmailrc if [ $? = 0 ] then echo "Mail completed at `date`">>/etc/mail/fetchmail.log elif [ $? = 1 ] then echo "No mail to retrieve at `date`">>/etc/fetchmail.log fi This is my fetchmail rc file: set postmaster (ro...@co...) set bouncemail set properties "" poll pop.connoisseur.co.za protocol POP3 nodns localdomains connoisseur.co.za username web...@co... password mxg123 to * here smtp 192.1.1.240 fetchall forcecr regards Fution _________________________________________________________________ Message offline contacts without any fire risk! http://www.communicationevolved.com/en-za/ |
|
From: Rob M. <rob...@gm...> - 2007-03-21 08:06:35
|
On 3/21/07, Chris <cpo...@ea...> wrote:
> I reported this back on the 11th of March, since then I've upgraded to what I
> understand is the latest version. Looking at the required information for a
> problem in the FAQ I'll try to provide it:
Thanks for all that. Typically there was still one thing that the FAQ
doesn't ask for that would have helped :) Can you provide the output
of "fetchmail -v -v -v -m procmail" for the problem email (that
should, hopefully, show what's happening).
You may find that enabling UIDL support helps as it moves to problem
of tracking seen emails from the server to fetchmail.
It may be that the problem will go away if you don't use "-m procmail"
but deliver directly to your SMTP server, but that's just a guess.
--
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
|