note: fetching two POP3 accounts from same remote server fails for one of them randomly
Hello bats, on Tue, 16. Mar 2004 at 04:23:22 +0100 I wrote: What now happens, is that when I do Check all accounts (alt-f2 / f11) one of both will fail like this: after looking further into this it has not to be one of the pop accounts for the same server (which is encoded in the smtp username anyway), but seems to be random on all accounts. I have altogether eight, which are all pulled over POPFile, but as POPFile is configured to allow concurrent connection it should accept all 8.. They are all using default network setup, which is dialup and the one that fails (IIRC there were two failing together sometime) fails after establishing the connection. Which is as I expect, but wanted to note this.. It looks like that TB cannot connect to POPFile at all (for the eighth account), but does not log it to the account's session log. IMO thebat should log this error (and what is causing it) to the file defined in protocol.ini.. any idea to track this down more? -- shinE! http://www.thequod.de ICQ#152282665 GnuPG/PGP key: http://thequod.de/danielhahler.asc Using The Bat! v2.04.7 on Windows XP 5.1 Build 2600 Service Pack 1 with POPFile 0.20.1 and avast Mar2004 (4.1.357). Current version is 2.04.7 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
fetching two POP3 accounts from same remote server fails for one of them randomly
Hello bats, I have redesigned my mailflow and am pulling now two pop3 accounts on the same server, both via POPFile (Proxy). For that I have set the pop3 server for both accounts to server: 127.0.0.1 user: samesmtpserver.com:differentusername password: thesameforbothpoplogins What now happens, is that when I do Check all accounts (alt-f2 / f11) one of both will fail like this: -8 16.03.2004, 03:33:26: FETCH - Couldn't connect to 127.0.0.1 trying subsequent addresses... !16.03.2004, 03:33:26: FETCH - Could not connect to the server -8 I have enabled traffic logging via protocol.ini, but there is NOTHING written into for that failure. POPFile log is also silent about this, so I guess thebat does not really try connecting at all. Both accounts only slightly differ in the username for the POP account, reagrding transport settings. Thought that it was POPFile's setting to use 'no concurrent connections' and therefor TB's request blocking. But this should have been logged in TB's pop3 session log and changing it to concurrent mail catching (with restart of popfile-service) does not help either. POPFile 0.20.1 is still running here. Any hint(s)? -- shinE! http://www.thequod.de ICQ#152282665 GnuPG/PGP key: http://thequod.de/danielhahler.asc Using The Bat! v2.04.7 on Windows XP 5.1 Build 2600 Service Pack 1 with POPFile 0.20.1 and avast Mar2004 (4.1.357). Current version is 2.04.7 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
