OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: How to configure a "pseudo null client"?

alanpatriot.net
Date: Fri Apr 04 2008 - 14:11:18 CDT


> alanpatriot.net wrote:
>
>> My present configuration sends this mail to "postmasterpatriot.net".
>> I wonder what would happen to mail sent by, say, a cron job on my
>> machine that failed. (Isn't such mail sent to root, and hence passed
>> on to me?)
>>
>
> it all depends on your configuration, which you forgot to post.
      I am not sure what you mean by "configuration". I give you here
      the relevant lines from my main.cf:
(start)---------------------
myhostname = debian.patriot.net
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = debian.patriot.net, localhost.patriot.net, localhost
relayhost = [smtp.patriot.net]
mynetworks = 127.0.0.0/8
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
                                           ------------------(finish)

My /etc/mailname contains the line:
           patriot.net

Whereas my /etc/hostname contains the line:
           alanmcc

I was given the lines above by the afore-mentioned tech support.
It works, mostly I think because the sasl stuff -- not given above
 -- works. But now that it is working, I think the above could
be improved.

> /etc/aliases are only used for mail delivered locally (in general, this
> means the domain is listed in mydestination).
      I think I should take out the debian.patriot.net from
      the mydestination entry, no? I have no idea what
      debian.patriot.net is supposed to mean.

> non fqdn addresses are
> subject to rewrite (myorigin).
      I wish I knew the definition of a Fully Qualified Domain Name!!
      I have picked "alanmcc" as my machine name, because, whatever
      a FQDN is, I'm almost sure that "alanmcc" isn't one. As stated
      many times -- including the last time I was on this E-list,
      about five years ago -- I don't want or need this machine to
      have anything to do with the Internet, except to send E-mail,
      which I do through PatriotNet, fetch my E-mail back from
      PatriotNet, which I do through fetchmail, and browse, which I
      do with firefox/iceweasel.

>> PatriotNet. Except, since I"m running Linux, there may be occasions,
>> as described above, where I want to receive mail that originates on
>> my machine, without it flying out to the outside world. Hence my
>> arch term "pseudo null client".
>>
>
> there's no such thing. if it's not a "null client", it's a server for
> its domains.
      <LOL> Did you read what I wrote? I explained, rather carefully,
      how my machine differs from the documentation definition of a
      null client. So I invented the term "pseudo null client". I admit
      it is a theoretical construct at the moment, but I hope to
      make it a reality, with the help of course of kindly members of
      this List.

Mr Mouss, thank you for your reply. Maybe this explanation has
made my problem a little clearer, to you and to others.

Alan McConnell