Search  Rules  Login
TheBat English » The Bat! - Configuring the E-mail Client
Pages: 1
RSS
5-0-30 version majorly broken, Fails to receive/send via localhost
 
#1
0  
I "upgraded" 5.0.24 pro to 5.0.30. As the result, mail transport stopped working - I could neither send nor receive mail. Here's a fragment of the receive log (with unread messages sitting in my mailbox):

1/3/2012, 02:17:43: FETCH - receiving mail messages
1/3/2012, 02:17:43: FETCH - Connecting to POP3 server localhost on port 110
1/3/2012, 02:17:44: FETCH - Couldn't connect to ::1 trying subsequent addresses...
1/3/2012, 02:17:44: FETCH - Connecting to 127.0.0.1...
!1/3/2012, 02:17:44: FETCH - Connect failed

Send logged similar (connect to localhost failed) errors.

I am using a Mercury/32 mail server running on localhost (Win7 x64), have been using this setup forever. Deleting the "upgraded" thebat.exe 5.0.30 and doing a repair install of 5.0.24 seems to have fixed things, at least I can now read the messages that have been sitting in my mailbox and could not be retrieved using 5.0.30. And sending also works. So much for this particular new year present.
 
 
 
#2
0  
Same here!  :cry:

Reported as part of an ongoing bug issue to support.
Edited: Peter Toye - 03 January 2012 12:23:00
Peter
 
 
 
#3
0  
It's a wreck. Can't email from localhost, have to switch back to my smtp. Deleted emails do not stay deleted. When I mark a folder as "Read" all deleted emails return since my last cache purge. I have been using Properties, Clear Cache all day today. Switching back. This version is NOT helpful.
 
 
 
#4
0  
Ritlabs Support say that they can't help and blame my SpamBayes spam reducer (which is on localhost). That doesn't explain DY's or batshades's comment.
Peter
 
 
 
#5
0  
For the record, I don't have any kind of email processing software between the bat and localhost pop3/smtp server. So with all due respect to ritlabs support IMHO this is bs. Do they ever post replies here BTW?
 
 
 
#6
0  
...and here's the solution, kind of:

Looking more closely at the logs I noticed that even when using 5.0.24 which worked, the logs did show errors preceding successful delivery, e.g.:

1/9/2012, 22:56:13: FETCH - receiving mail messages
1/9/2012, 22:56:13: FETCH - Connecting to POP3 server localhost on port 110
1/9/2012, 22:56:14: FETCH - Couldn't connect to ::1 trying subsequent addresses...
1/9/2012, 22:56:14: FETCH - Connecting to 127.0.0.1...
1/9/2012, 22:56:14: FETCH - connected to POP3 server
1/9/2012, 22:56:14: FETCH - authenticated (plain)
1/9/2012, 22:56:14: FETCH - 0 messages in the mailbox, 0 new
1/9/2012, 22:56:14: FETCH - connection finished - 0 messages received

The difference being that in 5.0.30/32, the 2nd attempt also failed:

1/9/2012, 23:00:42: FETCH - receiving mail messages
1/9/2012, 23:00:42: FETCH - Connecting to POP3 server localhost on port 110
1/9/2012, 23:00:43: FETCH - Couldn't connect to ::1 trying subsequent addresses...
1/9/2012, 23:00:43: FETCH - Connecting to 127.0.0.1...
!1/9/2012, 23:00:43: FETCH - Connect failed

Fooling around with the bat transport settings and the System32\drivers\etc\hosts file I found the following:

1) I'm running Windows 7. hosts file on it does not contain the 127.0.0.1 loopback (with the comment that it is handled by DNS itself). This seems relevant as adding the "127.0.0.1 localhost" line "fixed" the problem (but of course even without that line, "ping localhost" works).

2) Adding a "127.0.0.1 localmail" line instead, and specifying localmail as the pop3/smtp address in the bat! also worked.

3) Finally, leaving the hosts file alone and replacing localhost in the bat! transport settings with 127.0.0.1 also did the trick. That's what I am now using with 5.0.32. While I still think this is a bug in the bat!, that solution works and seems to be "good enough".
 
 
 
#7
0  
I just had a suggestion from tech. support to try using 120.0.0.1 instead of localhost. And found that it worked.

I agree about their previous reply, but at least they're still coming up with ideas. I was unaware with the comment in the hosts file about DNS resolving "localhost". And your solution (2) seems a good one. My guess is that the latest version does something subtly different with DNS which screws it up.

I notice that you're using 5.0.32. The version I downloaded only a month ago was 5.0.30. Do they really manage two subversions a month?

I've no idea if this forum is monitored at all by Ritlabs. I'd assumed it was just a user mutual help-fest.
Peter
 
 
 
#8
0  
My assumption is that a small bug in Windows 7 DNS and a small (buggy?) change in the Bat! 5.0.30's mail transport combined to screw up things for people using localhost.

As for my solution #2 - problem with it is, it is yet another thing to remember/set up when changing operating systems or computers. Using 127.0.0.1 does not involve that so I went with it.
 
 
 
Pages: 1