Yeah, a search on google, and a translation on babelfish, and I realized
what I had done :-)  FIxed now and working.

Thanks :-)

ADam

On Wed, 12 Mar 2003, Perry E. Metzger wrote:

> Date: 12 Mar 2003 09:58:36 -0500
> From: Perry E. Metzger <perry@piermont.com>
> To: Adam K Kirchhoff <adamk@voicenet.com>
> Cc: current-users <current-users@netbsd.org>
> Subject: Re: Postfix and emuxki on current...
>
>
> Your problem is that you did not upgrade your postfix configuration
> files. I sent a warning about this to current-users.
>
> Unfortunately, new postfixen rarely work okay with old postfix config
> files.
>
> Perry
>
> Adam K Kirchhoff <adamk@voicenet.com> writes:
>
> > I'm hoping someone can point me in the right direction.
> >
> > I just upgraded my system to -current earlier today (thanks to all who
> > helped!), and now postfix seems to be broken.
> >
> > Poostfix starts up without any problems:
> >
> > Mar 10 20:19:57 sorrow spamd[166]: server started on port 783 (running version 2.44)
> > Mar 10 20:19:57 sorrow postfix/postfix-script: starting the Postfix mail system
> > Mar 10 20:19:58 sorrow postfix/master[254]: daemon started -- version 2.0.6
> > Mar 10 15:30:20 sorrow spamd[164]: server started on port 783 (running version 2.44)
> > Mar 10 15:30:21 sorrow postfix/postfix-script: starting the Postfix mail system
> > Mar 10 15:30:21 sorrow postfix/master[252]: daemon started -- version 2.0.6
> >
> > (spamd is SpamAssassin, which I installed and got working before upgrading
> > to -current)
> >
> > I run fetchmail in the background to poll my pop3 server every minute or
> > so.  It gets the mail and tries to drop it off with postfix...
> > Unfortunately, postfix isn't liking this:
> >
> > Mar 10 20:33:08 sorrow postfix/smtpd[1585]: warning: connect #1 to subsystem /var/spool/postfix/private/proxymap: No such file or directory
> > Mar 10 20:33:18 sorrow postfix/smtpd[1585]: warning: connect #2 to subsystem /var/spool/postfix/private/proxymap: No such file or directory
> > Mar 10 20:33:28 sorrow postfix/smtpd[1585]: warning: connect #3 to subsystem /var/spool/postfix/private/proxymap: No such file or directory
> > Mar 10 20:33:38 sorrow postfix/smtpd[1585]: warning: connect #4 to subsystem /var/spool/postfix/private/proxymap: No such file or directory
> >
> > And, of course, /var/spool/postfix/private/proxymap does not exist...
> > There are number of other sockets in that directory, by no proxymap...
> >
> > Now, I'm not too familiar with postfix.  Is it safe to just create that
> > socket?  If not, what do I need to do to get it working once again?
> >
> > Also, I notice in the archives that someone recently posted about problems
> > they were having with the emuxki driver.  Just as an FYI, I'm having the
> > same problem...  /dev/audio just stopped responding, giving a "resource
> > temporarily unavailable" message.  Rebooting was the only way I got it to
> > work.
> >
> > I decided to try with a yds card, and I couldn't even get it to boot all
> > the way up.  The kernel just *stopped* when it got to the midi port on
> > yds0.
> >
> > Adam
> >
> >
>
> --
> Perry E. Metzger		perry@piermont.com
>
>