Hello bats, on Sun, 7. Mar 2004 at 01:41:42 +0700 Thomas Fernandez wrote:
> So there is no connection at all. If you take the above-mentioned > tickmark off, then only the main modul will try to dial out. If the > hamster-account is set to dial out and the main setting says the > same, there is likely to be an interference on OS-level. The hamster-account is set to LAN, not to a special connection. Because of this the account will be checked immediately, but it also causes the dialup SEND tasks to be done immediately, whivch fails of course. >> But I suspect your localhost account hasn't "LAN network settings" >> activated. > No. There is no tickmark at "Use account-specific...", so I have no > settings available at all. The main setting in TB is for dial-up, and > all accounts follow that lead, rather than have their own settings. So the bug does not happen on your system and your local mailserver (if you have any) will be checked only after dialup is up. I think, you don't understand, what I'm targeting: if there is an account set to "LAN", rather than dialup (which all others are, simply because they don't use account specific Network settings) TB will try to immediately send on all accounts, without waiting for an established dialup connection. I removed the special network settings for the hamster-account and it works of course like before (apart from that it takes longer until the account gets checked) and stops the bug bugging me, but of course the bug itself is still there. TB should simply not try to SEND mail for dialup accounts before the appropriate connection is up. Hope you understand now, what I mean. Just showing off a bug.. :) -- 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
