Hi Les At this point it probably becomes more of a documentation issue. With a realitivly standard Windows network, mail delivery from openfiler won't work unless an MX record is manually added to DNS. Possibly a note in the Admin guide mentioning it would be worthwhile.
Thanks Dave > -----Original Message----- > From: Les Mikesell [mailto:[EMAIL PROTECTED] > Sent: Thursday, 17 August 2006 9:26 a.m. > To: Dave Watkins > Cc: Mukund; [email protected] > Subject: RE: [OF-users] Email server configuration > > On Thu, 2006-08-17 at 09:00 +1200, Dave Watkins wrote: > > Hi Mukund > > > > Thanks, although that would lead to some issues for anyone using > > multiple domain controllers in Active Directory that have their > > internal domain name set to the same as their external domain name. > > > > What would happen in that case is that the openfiler box > would try to > > find an MX record for the domain in question, which (by default at > > least) wouldn't exist as AD doesn't create any MX records. When it > > didn't find that it would use the A record, which in AD > round-robins > > between all the domain controllers. Obviously they won't all be > > running MTA's and so delivery would fail. Setting an MX record > > internally would get around this but that probably only > covers some of > > the possible fringe cases. Although in saying that I can't think of > > any others ;) > > You should be able to point the openfiler box to a working > DNS server which will then make email work as designed. Or > use the address of a server that you know will accept it. > > -- > Les Mikesell > [EMAIL PROTECTED] > > > _______________________________________________ Openfiler-users mailing list [email protected] https://lists.openfiler.com/mailman/listinfo/openfiler-users
