It would be nice if this was re-enabled, because quite a few people have trouble
setting up darcs to send mail (and we want to make it easy for people to send us
patches)

As I understand it, sending from darcs.net to darcs-users@darcs.net doesn't work
because darcs.net thinks that darcs-users is a local mail recipient.  Tricky
business.

Maybe a quick and dirty solution would be to send mail to a non-darcs.net address?

http://lists.osuosl.org/pipermail/darcs-users/2008-September/013779.html

AIUI the web server darcs.net doesn't host the MTA that processes darcs.net
addresses, which is why it's bad for darcs-users@darcs.net to be treated as
a local address.

That being the case, would it work to simply add to /etc/aliases the line

    darcs-users: darcs-users@<IP address>

or something similar?  (Don't forget to run newaliases.)

A summary of the MTA and HTTPd software (versions and relevant config) and
what hosts are involved and their network config (hostnames, etc.) would
help us armchair commentators make informed (if still unhelpful) suggest-
ions.

I guess this is ultimately blocked on getting net-/sys-admin help?
http://wiki.darcs.net/index.html/DarcsTeam has that role filled by Eric,
but no "help wanted" flag?

I'd use real hostname of the target machine instead of its IP. Moreover, it 
might be better to use transport table (instead of an alias) if you are using 
postfix.

I guess I ought to look into this: 
  darcs-users@lists.osuosl.org will do what we want

so the main task is just for me to learn how to deploy that cgi script

On Tue, Aug 18, 2009 at 10:36:38PM +0000, Eric Kow wrote:
> I guess I ought to look into this:
>   darcs-users@lists.osuosl.org will do what we want
>
> So the main task is just for me to learn how to deploy that cgi
> script.

Are we talking about the recent work so that "darcs send <repo>" will
use HTTP POST instead of email?  If so, what will the CGI script that
receives the bundle do with it?  Bounce it to the mailing list?

Is there a way to disable the use of HTTP POST on the client side, if
the remote repo declares that it supports it, but it is (say)
temporarily broken?

On Wed, Aug 19, 2009 at 02:14:05 +0000, Trent W. Buck wrote:
> Are we talking about the recent work so that "darcs send <repo>" will
> use HTTP POST instead of email?  If so, what will the CGI script that
> receives the bundle do with it?  Bounce it to the mailing list?

It will bounce it to the mailing list indeed.

> Is there a way to disable the use of HTTP POST on the client side, if
> the remote repo declares that it supports it, but it is (say)
> temporarily broken?

I don't think so.

Moreover, when I send --dry-run it said:
  Patch bundle would be sent to: http://darcs.net/cgi-bin/upload.cgi darcs-users@darcs.net
which sounds potentially unpleasant.

So now I'm not sure how to proceed.  I guess we'll just have to live
without HTTP post for the darcs repo and assume that people either won't
mind the duplication or can live with mutual exclusivity.