Howdy all, I have a more or less off topic question about a situation my boss ran into the other day when he was travelling. He accessed our mailserver from a dialup account or from the company he was visiting (I'm not sure), which worked fine, of course. The problems arose when he tried to send an email to someone outside the company. We're using Gary Mills' DRACD for pop-before-smtp relay authentication, which he expected (and I, quite honestly) would allow him to send emails. Normally it does, but when he tried the other day, he got a message about the DNS address associated with the IP address he was assigned being possibly forged, and not allowing the email through. I was wondering if anyone has any thoughts they'd care to share on whether it is safe to move the DRACD rules to a point in the check_relay ruleset above where it does the DNS checks. My thinking on this is that, since the user has already authenticated themselves as being a valid user, they should be allowed to send, even though their DNS entries would not normally allow them to do so. We have several people who travel, and we're concerned this situation might arise again, and we need to have something in place where these users won't be blocked from sending emails. Does anyone have any suggestions on what we could do? Thanks in advance, Will ---------------------------------------------------------------------------- William K. Hardeman [EMAIL PROTECTED] http://www.wkh.org Always listen to experts. They'll tell you what can't be done and why. Then do it. --Robert A. Heinlein
