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: Aaron W. <aa...@vi...> - 2006-09-23 14:46:34
|
I would like to be able to save each email fetched in it's own file. Is there a way to do this using the option bsmtp? The manual page for the .fetchmailrc file states that there is an option to bsmtp which is -o. What does this do? TIA! - Aaron |
|
From: Matthias A. <mat...@gm...> - 2006-09-23 11:29:56
|
"Andrea Bencini" <and...@ti...> writes: >> If your original question was "how to duplicate messages for two >> accounts" > > Yes, it was that. > >> For anything that is remotely sendmail compatible (i. e. most mailers >> except qmail), writing something like this line into /etc/aliases > > This is the way. But doesn't work on qmail -- you need add-on software for that. -- Matthias Andree |
|
From: Andrea B. <and...@ti...> - 2006-09-22 16:14:41
|
> If your original question was "how to duplicate messages for two > accounts" Yes, it was that. > For anything that is remotely sendmail compatible (i. e. most mailers > except qmail), writing something like this line into /etc/aliases This is the way. Thank Matthias Andrea |
|
From: Matthias A. <mat...@gm...> - 2006-09-22 00:13:28
|
"Andrea Bencini" <and...@ti...> writes: >> what exactly was unclear about "Multiple servers may be listed:" in said >> section? > > The section that I read was "Configuration examples". > The examples are clear, but I did'nt find the answer to my question. If your original question was "how to duplicate messages for two accounts", fetchmail doesn't directly support that, since it's built around the idea of a local fully-fledged mail server that can do alias expansion. For anything that is remotely sendmail compatible (i. e. most mailers except qmail), writing something like this line into /etc/aliases or /etc/mail/aliases (check your manuals, details differ!) would work after running "sendmail -bi" or whatever else your system requires to rebuild the alias database: locallist: localuser1 localuser2 Alternatively, but not recommended, you can trick it into doing that by using an program that can deliver to multiple recipients at the same time, for instance: mda "/usr/sbin/sendmail -i -f %F -- localuser1 localuser2" Syntax is crucial for the MDA option, do NOT add single quotes here, and don't forget the -i. Note that most filtering MDAs do not support multiple recipients on the command line, so you'd need to spell this out in the configuration file. -- Matthias Andree |
|
From: Andrea B. <and...@ti...> - 2006-09-20 14:05:04
|
> what exactly was unclear about "Multiple servers may be listed:" in said > section? The section that I read was "Configuration examples". The examples are clear, but I did'nt find the answer to my question. Andrea |
|
From: Roberto M. <rob...@gm...> - 2006-09-19 22:42:38
|
2006/9/14, Rob MacGregor <rob...@gm...>: > On 9/13/06, Roberto Meyer <rob...@gm...> wrote: > > > > Finally I got a couple of errors with single connections. > > > > I've attached a .tgz file with the logs of fetchmail and tcpdump at > > the moment of the errors, and both logs for a well done connection > > too. > > A quick scan of the logs show what I'd expect for a networking > problem. I'll have a look at the text outputs from tcpdump later, > though a quick scan doesn't show anything obvious right now. [snip] Yep, I think it's somewhat prooved. I tested this options: 1- server 1 -> ISP 1 -> actual hosting = socket error 2- server 1 -> ISP 1 -> another server = socket error 3- server 2 -> ISP 2 -> actual hosting = ok!!! Both server 1 and 2 have the same fetchmail setup. It's an ISP problem! As you said (and I read over the Internet) people who had this problem solved it when they changed their ISP. ie: problems from work, when they went home and fetched mail they had no problem at all. There's almost 24hs I'm testing every 5' without trouble :-) HTH someone else. Thanx a lot for your help. - Roberto |
|
From: Matthias A. <mat...@gm...> - 2006-09-19 21:35:49
|
"Andrea Bencini" <and...@ti...> writes: >> This is detailed in the man page, which you obviously didn't bother to >> read. See the section titled "CONFIGURATION EXAMPLES". >> >> The online manual can be found at: >> http://www.fetchmail.info/fetchmail-man.html >> > I am sorry, but before writing mailing-list I just read the fetchmail manual > at http://www.fetchmail.info/fetchmail-man.html. Reading the section " > CONFIGURATION EXAMPLES" I didn't undestand what answer was to my question. > Perhaps, kindly, it was better that you gave me the answer. Andrea, what exactly was unclear about "Multiple servers may be listed:" in said section? Do you have any suggestions how to reword this so it's easier to find or recognize? Grazie. -- Matthias Andree |
|
From: Rob M. <rob...@gm...> - 2006-09-17 19:08:27
|
On 9/17/06, Andrea Bencini <and...@ti...> wrote: > > This is detailed in the man page, which you obviously didn't bother to > > read. See the section titled "CONFIGURATION EXAMPLES". > > > > The online manual can be found at: > > http://www.fetchmail.info/fetchmail-man.html > > > I am sorry, but before writing mailing-list I just read the fetchmail manual > at http://www.fetchmail.info/fetchmail-man.html. Reading the section " > CONFIGURATION EXAMPLES" I didn't undestand what answer was to my question. > Perhaps, kindly, it was better that you gave me the answer. poll POP.ISP.NET user USERA with password PASSA is LOCALA here user USERB with password PASSB is LOCALB here If however you want to put the same email into 2 separate accounts then you'll have to handle that with your local SMTP 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: Andrea B. <and...@ti...> - 2006-09-17 17:51:32
|
> This is detailed in the man page, which you obviously didn't bother to > read. See the section titled "CONFIGURATION EXAMPLES". > > The online manual can be found at: > http://www.fetchmail.info/fetchmail-man.html > I am sorry, but before writing mailing-list I just read the fetchmail manual at http://www.fetchmail.info/fetchmail-man.html. Reading the section " CONFIGURATION EXAMPLES" I didn't undestand what answer was to my question. Perhaps, kindly, it was better that you gave me the answer. Thank you Andrea |
|
From: Matthias A. <mat...@gm...> - 2006-09-16 18:10:24
|
"Roberto Meyer" <rob...@gm...> writes: > I'm really tired about it... I think I'll put my effort in testing the > ISP and hosting service... fetchmail has a rock solid reputation and I > think it's not fair for it to be the first suspect of this mistery ;-) Well, you aren't the first, Wikipedia used to link several critics of fetchmail, and some of them have, although exaggerated, a reasonable amount of truth in them -- some of the shortcomings have been resolved since those articles appeared though, or are at least on the plan -- I do not agree with some of the decisions ESR made, but I cannot change everything over night. One reason is the lack of time, another that fetchmail is stable code that cannot change radically with patchlevel releases... and the 6.4 round hasn't really opened yet. There IS 6.4 stuff on the trunk but I think I'll ditch that and copy 6.3 later, probably a while after 6.3.5 if no new problems crop up with 6.3.5 (which is also a few more weeks out probably) since redoing the few 6.3.0 -> 6.4 changes will probably be easier than porting 6.3.5 back onto the trunk... Subversion isn't too good at picking cherries. -- Matthias Andree |
|
From: Rob M. <rob...@gm...> - 2006-09-15 20:48:23
|
On 9/15/06, Andrea Bencini <and...@ti...> wrote: > I have a e-mail address and I would like to download my e-mails and put > them in two accounts on my local server. > example: > my e-mail address= an...@ti... > pop3=mail.tin.it > first account on my local server=andrea1 > second account on my local server=andrea2 > How can I do in .fetchmailrc? This is detailed in the man page, which you obviously didn't bother to read. See the section titled "CONFIGURATION EXAMPLES". The online manual can be found at: http://www.fetchmail.info/fetchmail-man.html -- 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: Andrea B. <and...@ti...> - 2006-09-15 15:44:16
|
I have a e-mail address and I would like to download my e-mails and put them in two accounts on my local server. example: my e-mail address= an...@ti... pop3=mail.tin.it first account on my local server=andrea1 second account on my local server=andrea2 How can I do in .fetchmailrc? Can you help me? Andrea |
|
From: Roberto M. <rob...@gm...> - 2006-09-15 02:11:17
|
2006/9/14, Matthias Andree <mat...@gm...>: [snip] > > Finally I got a couple of errors with single connections. > > Please update fetchmail (newer versions have fewer bugs and better error > reporting) and if the problem persists, run: > > env LC_ALL=C fetchmail -vvv --nodetach --nosyslog -d0 > > to obtain a more detailed log. However, it still looks like the problem > is outside fetchmail to me. Beacause it's a random error I agree with that. I thought about fetching e-mails from a different place, over a different ISP to figure out if the problem could be related to the ISP or the hosting service instead. Today I did an 'mtr' of 600 pings. Below you'll find the results which, BTW, I think are reasonable. HOST: myfetchmachine Loss% Snt Last Avg Best Wrst StDev 1. host.200.55.19.330 0.0% 600 25.4 40.0 21.3 307.8 32.1 2. 201.10.19.45 0.0% 600 21.4 46.8 20.6 841.2 62.2 3. 201.10.19.41 0.0% 600 36.3 49.4 21.3 876.4 65.9 4. 201.15.63.207 0.0% 600 56.5 77.6 38.9 806.1 74.6 5. mng-ats.impsat.net.ar 0.0% 600 41.6 68.7 38.7 659.6 71.5 6. remotemailserver.com 8.8% 600 46.3 72.8 42.8 669.9 64.5 I'm really tired about it... I think I'll put my effort in testing the ISP and hosting service... fetchmail has a rock solid reputation and I think it's not fair for it to be the first suspect of this mistery ;-) Thanks a lot for your kind answers. -- Roberto |
|
From: Matthias A. <mat...@gm...> - 2006-09-14 23:25:09
|
"Roberto Meyer" <rob...@gm...> writes: > 2006/9/13, Rob MacGregor <rob...@gm...>: > >> On 9/12/06, Roberto Meyer <rob...@gm...> wrote: >> > >> > Still having problems with it, I decided to put tcpdump in action. The >> > problem is I don't really know much about it. I read the man pages and >> > understood a little about flags, etc. but don't know a lot of tcp/ip. >> > >> > I've attached the output of two connections triggered at the same time >> > for two different users through cron jobs. One of them was successful, >> > the other one failed with a socket, status=2 result. >> > >> > The command I issued was: >> > "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw" >> > >> > I've attached the 'text' version of it which I rescued through >> > "tcpdump -r /tmp/tcpdump.raw" >> >> Separating the 2 is, sadly, not possible. If you could capture one >> working run and one failed run then I *may* be able to help work out >> what's going wrong. It would help to have the binary pcap of the >> failed run, though obviously you'd need to change passwords >> immediately afterwards (or before and after) for security reasons. > > Finally I got a couple of errors with single connections. Please update fetchmail (newer versions have fewer bugs and better error reporting) and if the problem persists, run: env LC_ALL=C fetchmail -vvv --nodetach --nosyslog -d0 to obtain a more detailed log. However, it still looks like the problem is outside fetchmail to me. -- Matthias Andree |
|
From: Rob M. <rob...@gm...> - 2006-09-14 10:12:49
|
On 9/13/06, Roberto Meyer <rob...@gm...> wrote:
>
> Finally I got a couple of errors with single connections.
>
> I've attached a .tgz file with the logs of fetchmail and tcpdump at
> the moment of the errors, and both logs for a well done connection
> too.
A quick scan of the logs show what I'd expect for a networking
problem. I'll have a look at the text outputs from tcpdump later,
though a quick scan doesn't show anything obvious right now.
> "cat /proc/sys/net/ipv4/tcp_ecn" returns "0" (zero)
Ok, so ECN isn't on so can't be the source of the problem (which is a
confirmation of what I already suspected).
> "ifconfig eth0" returns:
>
> eth0 Link encap:Ethernet HWaddr 11:50:24:64:09:BE
> inet addr:201.65.9.43 Bcast:201.65.9.255 Mask:255.255.255.224
> ^^^^^^^^^^^^^^^^
> I noticed here broadcast address is wrong... could this be hurting
> packets or fetchmail connections? It should be 201.65.9.63 because of
> the netmask...
Well, that won't matter to fetchmail. It'll only matter when
something does a broadcast (like DHCP).
> Thanx a lot for your help.
So far, everything seems to point to intermittent network problems
somewhere in the path from your host to the remote POP server. It
could be that the other software doesn't report these errors, or it
could be that something about the network topology means they take a
different route...
Once I've had the time to take a better look at the tcpdump output
I'll get back to 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: Roberto M. <rob...@gm...> - 2006-09-13 23:13:34
|
2006/9/13, Rob MacGregor <rob...@gm...>:
> On 9/12/06, Roberto Meyer <rob...@gm...> wrote:
> >
> > Still having problems with it, I decided to put tcpdump in action. The
> > problem is I don't really know much about it. I read the man pages and
> > understood a little about flags, etc. but don't know a lot of tcp/ip.
> >
> > I've attached the output of two connections triggered at the same time
> > for two different users through cron jobs. One of them was successful,
> > the other one failed with a socket, status=2 result.
> >
> > The command I issued was:
> > "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw"
> >
> > I've attached the 'text' version of it which I rescued through
> > "tcpdump -r /tmp/tcpdump.raw"
>
> Separating the 2 is, sadly, not possible. If you could capture one
> working run and one failed run then I *may* be able to help work out
> what's going wrong. It would help to have the binary pcap of the
> failed run, though obviously you'd need to change passwords
> immediately afterwards (or before and after) for security reasons.
Finally I got a couple of errors with single connections.
I've attached a .tgz file with the logs of fetchmail and tcpdump at
the moment of the errors, and both logs for a well done connection
too.
> Can you provide the output of "ifconfig eth0" (feel free to mangle MAC
> and IP addresses) and "cat /proc/sys/net/ipv4/tcp_ecn"?
"cat /proc/sys/net/ipv4/tcp_ecn" returns "0" (zero)
"ifconfig eth0" returns:
eth0 Link encap:Ethernet HWaddr 11:50:24:64:09:BE
inet addr:201.65.9.43 Bcast:201.65.9.255 Mask:255.255.255.224
^^^^^^^^^^^^^^^^
I noticed here broadcast address is wrong... could this be hurting
packets or fetchmail connections? It should be 201.65.9.63 because of
the netmask...
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1240552 errors:34 dropped:0 overruns:0 frame:34
TX packets:636714 errors:0 dropped:0 overruns:0 carrier:105
collisions:0 txqueuelen:1000
RX bytes:397976183 (379.5 MiB) TX bytes:78105812 (74.4 MiB)
Interrupt:14 Base address:0xdc00
Carrier error were due to a cable unplug a week ago.
As far as I checked, frame errors don't seem to be directly related to
fetchmail problems.
I'll change broadcast setup, though I didn't write it in
/etc/init.d/interfaces, I only specified address, network and
gateway... I'm surprised Linux didn't calculate it well...
Thanx a lot for your help.
--
Roberto
|
|
From: Rob M. <rob...@gm...> - 2006-09-13 10:10:41
|
On 9/12/06, Roberto Meyer <rob...@gm...> wrote:
>
> Still having problems with it, I decided to put tcpdump in action. The
> problem is I don't really know much about it. I read the man pages and
> understood a little about flags, etc. but don't know a lot of tcp/ip.
>
> I've attached the output of two connections triggered at the same time
> for two different users through cron jobs. One of them was successful,
> the other one failed with a socket, status=2 result.
>
> The command I issued was:
> "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw"
>
> I've attached the 'text' version of it which I rescued through
> "tcpdump -r /tmp/tcpdump.raw"
Separating the 2 is, sadly, not possible. If you could capture one
working run and one failed run then I *may* be able to help work out
what's going wrong. It would help to have the binary pcap of the
failed run, though obviously you'd need to change passwords
immediately afterwards (or before and after) for security reasons.
I still think you'll get some information from a simple telnet. That
at least will confirm that it's not fetchmail that's at fault. Worth
noting that things like ECN can cause problems with remote mail
servers.
Can you provide the output of "ifconfig eth0" (feel free to mangle MAC
and IP addresses) and "cat /proc/sys/net/ipv4/tcp_ecn"?
--
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: Roberto M. <rob...@gm...> - 2006-09-13 00:27:28
|
2006/9/12, Rob MacGregor <rob...@gm...>: > On 9/11/06, Roberto Meyer <rob...@gm...> wrote: > > Hi, > > > > I translated the error message in the subject of this mail from > > spanish, I don't know if it shows exactly like this in other systems. > The error relates to fetchmail being unable to communicate with the > remote server. This is almost always a network issue. [snip] Still having problems with it, I decided to put tcpdump in action. The problem is I don't really know much about it. I read the man pages and understood a little about flags, etc. but don't know a lot of tcp/ip. I've attached the output of two connections triggered at the same time for two different users through cron jobs. One of them was successful, the other one failed with a socket, status=2 result. The command I issued was: "tcpdump -v -s1500 -i eth0 -n tcp port 110 -w /tmp/tcpdump.raw" I've attached the 'text' version of it which I rescued through "tcpdump -r /tmp/tcpdump.raw" I know this is a bit off-topic but as this thread started with fetchmail maybe someone knows help: TIA, PD: the mail server is only one and always the same, at least it resolves always to a single IP. -- Roberto |
|
From: Rob M. <rob...@gm...> - 2006-09-12 12:54:25
|
On 9/11/06, Roberto Meyer <rob...@gm...> wrote: > Hi, > > I translated the error message in the subject of this mail from > spanish, I don't know if it shows exactly like this in other systems. > > I'm running processes for each user from crontabs. I get error > messages, not always, not always from the same user's cron job. I'm > running Debian Sarge with fetchmail: 6.2.5. Please update to 6.3 (though it probably won't help this particular case). > I'm stuck. I've tried IMAP and POP3 and didn't find much difference. > Fetchmail is connecting to Courier-IMAP or/and Courier-POP. The error relates to fetchmail being unable to communicate with the remote server. This is almost always a network issue. > fetchmail: 6.2.5 interrogando a mail.mydomain.com (protocolo POP3) en lun 11 s > iniciada > fetchmail: error `socket' recibiendo de mail.mydomain.com > fetchmail: 6.2.5 interrogando mail.mydomain.com (protocolo POP3) en lun 11 sep > erminada > fetchmail: Estado de la consulta=2 (SOCKET) > fetchmail: terminación normal, estado 2 <---SNIP---> > I'll appreciate any help. TIA, One test you can try is to see if "telnet mail.mydomain.com 110" works consistently. You may find that you've got a number of remote mailservers and one of them is causing this problem. Without real domain names for the ISP it's hard to say more. -- 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: Roberto M. <rob...@gm...> - 2006-09-11 20:36:05
|
Hi, I translated the error message in the subject of this mail from spanish, I don't know if it shows exactly like this in other systems. I'm running processes for each user from crontabs. I get error messages, not always, not always from the same user's cron job. I'm running Debian Sarge with fetchmail: 6.2.5. I'm stuck. I've tried IMAP and POP3 and didn't find much difference. Fetchmail is connecting to Courier-IMAP or/and Courier-POP. Each user has a .fetchmailrc which looks like this: poll mail.mydomain.com protocol POP3 user "us...@my..." pass "pass" smtpaddress "mydomain.com" Each user's cron job (8 at this time) is set to: */5 * * * * fetchmail -vvv 1>> fe.log 2>&1 where fe.log is a log file at user's home directory. Here the error I found at many fe.log: fetchmail: 6.2.5 interrogando a mail.mydomain.com (protocolo POP3) en lun 11 s iniciada fetchmail: error `socket' recibiendo de mail.mydomain.com fetchmail: 6.2.5 interrogando mail.mydomain.com (protocolo POP3) en lun 11 sep erminada fetchmail: Estado de la consulta=2 (SOCKET) fetchmail: terminación normal, estado 2 As a plus, people at this organization is downloading mail using something calles "mail diamond" for Winbug without problem :-( I'll appreciate any help. TIA, -- Roberto |
|
From: Neil W. <ne...@dc...> - 2006-09-08 16:24:43
|
Thanks Matthias, > Any only halfway recent fetchmail version will use an empty envelope > sender address, avoiding that problem. Thanks, I've upgraded it and it's now sending them from a blank address, so it's working. >> So I somehow need to be able to add qvirtual for each domain that the >> multi drop mailbox supports. > > Not at this time I'm afraid - send patches - or even better tell them to > stop doing that nonsense. Ok, I'll see what I can do.' Thanks again Matthias! Neil -- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html |
|
From: Neil W. <ne...@dc...> - 2006-09-08 14:46:59
|
Rob Funk wrote: > Neil Wilson wrote: >> >> Has the site been moved, or is it just temporarily down? > > Must have been temporary, because it looks fine to me right now. > It's working again now, so must have been a temp problem. I know berlios was doing an upgrade on the 6th Sept so maybe this has something to do with it. Thanks! -- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html |
|
From: Rob F. <rf...@fu...> - 2006-09-08 14:31:07
|
Neil Wilson wrote: > I tried to go to the fetchmail homepage http://fetchmail.berlios.de/ and > got the following. > > Gone > The requested resource > / > is no longer available on this server and there is no forwarding > address. Please remove all references to this resource. Apache/1.3.27 > Server at fetchmail.berlios.de Port 80 > > > Has the site been moved, or is it just temporarily down? Must have been temporary, because it looks fine to me right now. -- ==============================| "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: Neil W. <ne...@dc...> - 2006-09-08 13:25:35
|
I tried to go to the fetchmail homepage http://fetchmail.berlios.de/ and got the following. Gone The requested resource / is no longer available on this server and there is no forwarding address. Please remove all references to this resource. Apache/1.3.27 Server at fetchmail.berlios.de Port 80 Has the site been moved, or is it just temporarily down? Thanks. Neil -- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html |
|
From: Matthias A. <mat...@gm...> - 2006-09-07 16:17:44
|
Neil Wilson <ne...@dc...> writes: > Hi guys, > > I have two questions regarding fetchmail. > > The first one is... > > One of our ISP's SMTP servers is discarding all mail that comes from FETCHMAIL-DAEMON@domain so miss-addressed bounced messages aren't getting back to the > original senders. Any only halfway recent fetchmail version will use an empty envelope sender address, avoiding that problem. > Is there a way to change the address that fetchmail bounces mail >from(the sender address of the bounced message) instead of >FETCHMAIL-DAEMON? No. > My next questions is... > > I have a client who collects email from a multi-drop mailbox with a local domain of domain1.co.za > EG: user bla with password "blabla" is * here > > At the moment I'm using "envelope To:" as the envelope, but I'd like to use "Delivered-To:" because the mail is originating from a qmail server and mail from > mailing lists etc.(Bcc'd) mail is bouncing. > > The qmail server adds on a dom...@do... so I'd like to use qvirtual "domain1.co.za-" part, but the problem is that the mailbox has multiple > domains attached to it. > > eg: localdomains: domain1.co.za domain2.co.za domain3.co.za > > So I somehow need to be able to add qvirtual for each domain that the > multi drop mailbox supports. Not at this time I'm afraid - send patches - or even better tell them to stop doing that nonsense. -- Matthias Andree |