email alias issue

[ik]

On Tue, Jul 19, 2011 at 23:55, Geoff Shang <geoff at quitelikely.com> wrote:

> On Tue, 19 Jul 2011, ik wrote:
>
>  2011/7/19 Hetz Ben Hamo <hetzbh at gmail.com>
>>
>>  Hi,
>>>
>>> I have a weird issue with /etc/aliases
>>> I've setup the root to send emails to my email (hetz at benhamo.org) and
>>> ran
>>> the newaliases command to rebuild the aliases db file.
>>> I've restarted sendmail.
>>>
>>> And yet, sendmail simply ignores this alias and tries to send emails to
>>> root at benhamo.org (which of course doesn't exists).
>>>
>>> Any suggestions?
>>>
>>>
>> Yes, DON'T work with sendmail
>>
>
> <rant>
> I really *hate* these sorts of non-answers.  They don't help at all with
> the immediate problem and only really serve to annoy the person asking the
> question.  Yes, I realise that in this case the questioner ended up taking
> this person's advice, but there may well have been plenty of cases where
> they might not have been able to.  Questions like this don't usually outline
> the rationale for why they are using the software/hardware/whatever they're
> asking about, and neither should they have to.
>

Yes you do. If you are saying I have a problem with something, and want
others to help you, you should provide as much as possible information about
the issue. Hetz imho gave only limited information about the problem, and
where he think that it might be. That's does not helping us to help him, so
usually when someone lack of proper information about the whole thing, get
an answer as detailed as they provided.
Even though I consider Hetz as a friend, he should know better and provide
more information on the subject, such as "I have a new installation" or "old
installation" and "here are the entire settings I provided" etc... all of
that information even if it seems not very helpful, it might provide a clue
for the helpers to help him. Let's assume that you have only 10 reasons why
sendmail acts like it acts, don't you think that such information can limit
the amount of guess work ?


>
> If I ask about a problem I'm having with my cat, the last thing I want to
> hear from someone is that I should have a dog instead.  The fact is that I
> have a cat.  There may be good reasons for recommending a dog instead, and I
> can see why it might be relevent to mention this when answering, but to just
> say "get a dog" is not at all helpful.
>
> And if you *must* say "get a dog", at least say why.
>

Wrong way example that does not suite the issue at hand.
If you rant that your cat does not understand your commands, and you want to
make it understand it, then "take a dog" is the answer. That's not what you
are looking for, please provide additional information or rephrase your
question regarding the issue with your cat. Maybe the problem is that the
cat keep on getting hurt because it stand on electric oven and get burns,
and then the solution is completly different, but when you phrase it that
you want an animal that answer commands, the the answer you'll have is "get
a dog"


> </rant>
>
> Geoff.


Ido

>
>
>
> ______________________________**_________________
> Linux-il mailing list
> Linux-il at cs.huji.ac.il
> http://mailman.cs.huji.ac.il/**mailman/listinfo/linux-il<http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.cs.huji.ac.il/pipermail/linux-il/attachments/20110720/060b447c/attachment-0001.html>