Custom Query (1145 matches)

Reported by tabbott, 17 years ago.

We should fix mh on Debathena. I think we've still got the mhl and defaults problems remaining.

Reported by andersk, 17 years ago.

The current debathena-nmh is based on the patched nmh 1.0 sources from Athena 9.4. We should figure out a minimal set of patches and apply them to Debian's nmh 1.2 package instead.

Reported by mitchb, 16 years ago.

This morning, I caught the following in a DSN:

----- The following addresses had permanent fatal errors -----

"|/usr/bin/dsmail -A -d /var/spool/discuss/lsc-trailers"

(reason: Can't create output) (expanded from: <lsc-trailers-mtg@…>)

----- Transcript of session follows -----

550-Can't enter transaction 550- into meeting /var/spool/discuss/lsc-trailers: Connection reset by peer 550 5.0.0 "|/usr/bin/dsmail -A -d /var/spool/discuss/lsc-trailers"... Can't c reate output

This is due to a reversion in the recently updated debathena-discuss-server package. It results in dsmail being completely unable to work, but not via a bug in dsmail itself.

Ordinarily, if root@ATHENA.MIT.EDU has bits on a meeting, then user 'root' on that server is granted those bits. This means that to set up a mail feed to a discuss archive, you figure out what user your MTA will exec dsmail as, and adjust the ACL of the meeting to grant bits to that username@ATHENA.MIT.EDU. With the revised debathena-discuss-server package, if you run discuss as some user on the local server and try to so much as add a non-public meeting, you get the "Connection reset by peer" error.

Downgrading only debathena-discuss from 10.0.8-0debathena1 to 10.0.7-0debathena3 does not fix the problem. Downgrading only debathena-discuss-server does fix the problem.