when I send mails I have this line in the header
X-Authentication-Warning: localhost.localdomain: nikhil owned process doing -bs
what does it mean?
-- My life needs a rewind/erase button. -- Calvin
Sometime on Apr 2, Nikhil Joshi assembled some asciibets to say:
X-Authentication-Warning: localhost.localdomain: nikhil owned process doing -bs
what does it mean?
It means that you changed the From address in your message. Your username on your machine is nikhil@localhost.localdomain, but you told your mail client (pine) to pretend that you are nikhiljoshi@subdimension.com
Of course, pine followed your orders. However, pine invoked mighty sendmail in -bs mode - that is SMTP via stdio mode. It did this running as you - nikhil.
Sendmail in its infinite wisdom noted that you - nikhil - who owned the humble pine process - were trying to send a mail as someone you weren't.
It checked to see how trustworthy you were, and found that you weren't. Therefore, it could not, in good concience, send the mail without first attaching an appropriate warning.
Hope this answers your question.
Philip
Today @ 12:49am Philip S Tellis wrote:
Of course, pine followed your orders. However, pine invoked mighty sendmail in -bs mode - that is SMTP via stdio mode. It did this running as you - nikhil.
Boy they mean cryptic when they say Unix messages are cryptic ;)
On Wed, 3 Apr 2002, Nikhil Joshi wrote:
sendmail in -bs mode - that is SMTP via stdio mode. It did this running as you - nikhil.
Boy they mean cryptic when they say Unix messages are cryptic ;)
well, then you try fitting all that into a single line.
Sometime on Apr 3, Nikhil Joshi assembled some asciibets to say:
X-Authentication-Warning: nikhil probably is a spammer
but that doesn't tell the truth. what is really needed is that the warning say what it knows has happened. If it is relevant to the reader, he will be able to decipher it. If he can't, he will read the docs, and then decipher it.
Today @ 12:48am Philip S Tellis wrote:
X-Authentication-Warning: nikhil probably is a spammer
but that doesn't tell the truth. what is really needed is that the warning say what it knows has happened. If it is relevant to the reader, he will be able to decipher it. If he can't, he will read the docs, and then decipher it.
Hi! Was just kiddin' Afterall Unix should be fun right?