On Fri, Apr 23, 1999 at 10:23:06AM -0400, David Shaw wrote:
>
> Hhere is no such domain as "hals.box" and some (but, as you found out, not
> all) systems won't talk to you because of it. This is generally done as a
> spam protection technique (all those mails coming from "[EMAIL PROTECTED]" and
> such nonsense).
>
> Some sites bounce it immediately, like the example above, and some give a
> temporary error which causes your system (or relay) to try again later.
> The temporary error makes more sense to me, as if the receiving site's DNS
> is either down or having problems it can come up with false positives, so
> retrying later prevents valid mail from being bounced. On the other hand,
> if a name is completely bogus, it'll sit in the queue for potentially days
> before the user who sent it knows what happened.
>
> Either way, what you need to do is arrange for your envelope sender to be
> something valid. Probably the most elegant way to do this is to use
> sendmail's genericstable feature to rewrite '[EMAIL PROTECTED]' to
> '[EMAIL PROTECTED]'. A less elegant, but simpler, way would be to change your
> $sendmail variable to something like:
>
> set sendmail="/usr/sbin/sendmail -oem -oi [EMAIL PROTECTED]"
>
Well I am starting sendmail as : sendmail -bd -f [EMAIL PROTECTED] I
thought this might help, but doesn't seem to. ????
> That should work in most setups, but it might (again, depending on your
> configuration) add a header to your mail saying:
>
> X-Authentication-Warning: hals.box: hal set sender to hdb using -f
>
> If that bothers you, either add yourself to the "trusted user" section of
> /etc/sendmail.cf or just use genericstable. :)
>
> David
>
I've got several good suggestions now. I apprecitate your time and
help. Thanks again David!
--
Hal B
[EMAIL PROTECTED]
