On Thu, Jan 03, 2008 at 05:48:06PM -0500, Bill Moran wrote:
> In response to Gary Kline <[EMAIL PROTECTED]>:
>
> > On Thu, Jan 03, 2008 at 05:06:49PM -0500, Bill Moran wrote:
> > > In response to Gary Kline <[EMAIL PROTECTED]>:
> > >
> > > >
> > > > I stumpped. I get incomiing ail, but nothing gets out from my
> > > > private networked servers. Anybody know where to start figuring
> > > > out why??
> > >
> > > Have you checked /var/log/maillog?
>
> Bill Moran
> http://www.potentialtech.com
The two lines you suggested I add to my .cf file idn't work,
Bill, but it was a start at least. ....
Somehow I managed to screw up even incoming mail on
sage==ns1. And most or all of my other internal servers
are hosed too. TO get mail flowing again, at least incoming, I
retrieved that last sendmail from RCS and restarted mail.
I'm hoping that somebody can clue me in. It may be a peermissions
problem. But where/ and why would this be
a SYSERR problem. For instance, from my new server, when I try to send
mail to my DNS server, the following is what is
reported in maillog:
Jan 4 13:25:45 tao sendmail[18706]: m04LPjIr018706: SYSERR(kline): collect:
Cannot write ./dfm04LPjIr018706 (bfcommit, uid=1004, gid=25): Permission denied
Jan 4 13:25:45 tao sendmail[18706]: m04LPjIr018706: from=kline, size=543,
class=0, nrcpts=1, [EMAIL PROTECTED]
Jan 4 13:25:45 tao sendmail[18706]: m04LPjIr018706: SYSERR(kline): queueup:
cannot create queue file ./qfm04LPjIr018706, euid=1004, fd=-1, fp=0x0:
Permission denied
Anybody know how I messed up? ---This is no excuse, but because
of the recent build problems I did wholesale ``portupgrades -af''
(**sigh**)
Why cannot creat the queue files??
gary
--
Gary Kline Seattle BSD Users' Group (seabug) | [EMAIL PROTECTED]
Thought Unlimited Org's Alternate Email Site
http://www.magnesium.net/~kline
To live is not a necessity; but to live honorably...is a necessity. -Kant
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
