From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5fc834161c5048a2eddd41a26be25d2c@quanstro.net>
To: 9fans@9fans.net
From: erik quanstrom <quanstro@quanstro.net>
Date: Sat, 10 Jan 2009 15:57:52 -0500
In-Reply-To: <8b61afb60947d38fa542dc6cb692ee7f@csplan9.rit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] dealing with spam
Topicbox-Message-UUID: 7fa43c90-ead4-11e9-9d60-3106f5b1d025

> If nupas gets installed to /$objtype/bin/nupas, what files will I need
> to update to make sure everything uses nupas rather than the old
> upas? I'm assuming stuff in the listen scripts, any references in my
> profile, but anything else?

i didn't put this on sources because i thought it would be easier
for folks other than me to cut over cold-turkey.  i have a special
requirement to support both for a while.  this is what i use as
a ugly little shim for everything but listen:

	minooka; cat /bin/usenupas
	#!/bin/rc

	bind /$objtype/bin/nupas /bin/upas
	bind -b /$objtype/bin/nupas /acme/bin/$objtype

this is called from lib/profile.

instead of fighting with /rc/bin/service*/tcp25 and remotemail,
i copied the newsmtp* to /$objtype/bin/upas.  i didn't want to
have a large pile of things to undo later.

if you use imap4d, you'll also need to make arrangements for
it in /rc/bin/service*/tcp^(143 993).

this is what i use:
	#!/bin/rc

	switch($sysname){
	case *
		l=imap4
		im=(/bin/nupas/imap4d -b /bin/nupas -vl$l)
		d=coraid.com
	}
	exec tlssrv -c/sys/lib/ssl/imap.pem -limap4d.tls -r`{cat $3/remote} \
		$im -pd$d -r`{cat $3/remote}>[2]/sys/log/$l


- erik