Well, I think James is operating correctly. It seems to support IPv6 and it probably binds to the default IP for the machine that seems to be "fe80:0:0:0:230:65ff:febf:2988". BTW, a bug could be somewhere near: are you able to specify Authorized addresses in the Ipv6 form?
Stefano > I have been experiencing some strange behavior in the james > smtp server running on OS X (10.3.9). > > Beginning early this month, I started getting intermittent > relay rejections because computers on my local network were > not recognized as having an authorized address. > > At that time, smtpserver log messages changed from something > like this: > > "smtpserver-[..] INFO smtpserver: Connection from > 192.168.1.56 (192.168.1.56)" > > to this: > > "smtpserver-[..] INFO smtpserver: Connection from > topeka.local (fe80:0:0:0:230:65ff:febf:2988)" > > The string inside the parentheses is the contents of the > remoteIP data member in the SMTPHandler class. It has changed > from something meaningful to James (eg. 192.168.1.56) to > jibberish (eg. > fe80:0:0:0:230:65ff:febf:2988). > > After doing some digging, I figured out that > "fe80:0:0:0:230:65ff:febf:2988" is an IPv6 address. I made > the problem go away by disabling IPv6 in the James host > machine. It had been set to configure itself automatically. > > So is this a bug in James? Should it matter to James that > IPv6 is enabled on its host machine? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
