#1 Login failure: configuration oddities

[cfr]

Mac OS X 10.4.8 PPC G4 1.5 GHz 1.25G RAM

Login to mailserver repeatedly fails. I would assume this was my failure to set up correctly, except that the Console log includes the following:

ALERT: [/Users/bmoore/Work/MacBiff/web/MacBiff/MacBiff.m:77] Stopping Check. Received SIGUSR2
ALERT: [/Users/bmoore/Work/MacBiff/web/MacBiff/comms_ssl.c:150] res: -1, err: 2, errno: 4
ALERT: [/Users/bmoore/Work/MacBiff/web/MacBiff/comms.c:151] read: No such file or directory
ALERT: [/Users/bmoore/Work/MacBiff/web/MacBiff/comms_ssl.c:150] res: 0, err: 5, errno: 0

It isn't suprising the computer can't deal with this since there is no such user on my machine. What I don't understand, though, is why the programme should be looking here in the first place. Is something hard coded here which ought be be picked up from the user's environment and/or set as a configuration option?

[Branden Moore]

Logged In: YES
user_id=1443959
Originator: NO

My apologies for such a delayed response. I did not receive the email with this bug for some reason.

First of all, the whole part inside of the square brackets is just text to assist in debugging. They give the source code file name and line number associated with the warning. The lack of a 'bmoore' user on your machine is irrelevant. They paths are determined at compile time, and MacBiff is not looking for that file.

As for the problem that you are experiencing, please double-check to make sure that you have MacBiff configured correctly, and you have given it the correct username, password and IMAP server configuration. Since it appears that you are using SSL, please check to make sure that the port is set correctly. It should be 993. (There is a bug in the last released version that would not automatically update the port when set to SSL.)

Hopefully you have solved this problem already, but let me know if it remains.

[cfr]

Logged In: YES
user_id=643832
Originator: YES

Thanks. I cannot now remember what I did, but I did get it to work in the end. For some reason, it always failed initially but then cancelling the attempt (rather than trying to re-enter login data) caused it to work just fine. I could understand the initial failure if maybe network connexions weren't up, but it seemed very odd that it worked if, and only if, I then cancelled rather than telling it to retry.

Actually, that may be all that I did - learnt to cancel rather than retrying.