From: chad <chadpbrown@gmail.com>
To: David Reitter <david.reitter@gmail.com>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>,
ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Outgoing mail defaults
Date: Thu, 17 Mar 2011 18:27:06 -0400 [thread overview]
Message-ID: <57C2C312-5FE3-4152-8ACB-8761813E8692@gmail.com> (raw)
In-Reply-To: <41D75E0D-9F9E-4476-A6D3-93FA34156854@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Mar 17, 2011, at 3:02 PM, David Reitter wrote:
>
> Making it listen on port 80 would be easier than installing a server-side script taking a POST request on port 80.
> OTOH, Ted's suggestion about the hashcash seems very attractive, especially if the SMTP server would forward bug reports to other packages in the process.
Do you think we can expect hashcash to reasonably work in the case were the user hasn't configured emacs, it's not working, and sending mail doesn't work? I don't know the details of the hashcash implementation, but a quick internet search suggest that emacs would need to successfully communicate with a subprocess to a binary that isn't likely to be installed.
Hope that helps,
*Chad
[-- Attachment #2: Type: text/html, Size: 1024 bytes --]
next prev parent reply other threads:[~2011-03-17 22:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 17:04 Lars Magne Ingebrigtsen
2011-03-17 17:17 ` Ted Zlatanov
2011-03-17 17:31 ` Lars Magne Ingebrigtsen
2011-03-17 18:18 ` Ted Zlatanov
2011-03-17 18:33 ` Lars Magne Ingebrigtsen
2011-03-17 19:35 ` Ted Zlatanov
2011-03-17 17:25 ` David Reitter
2011-03-17 17:43 ` Lars Magne Ingebrigtsen
2011-03-17 18:22 ` Ted Zlatanov
2011-03-18 14:10 ` John Sullivan
2011-03-17 19:02 ` David Reitter
2011-03-17 22:27 ` chad [this message]
2011-03-18 2:38 ` Ted Zlatanov
2011-03-18 4:17 ` chad
2011-03-21 19:46 ` Adam Sjøgren
2011-03-21 19:50 ` Ted Zlatanov
2011-03-17 20:23 ` James Cloos
2011-03-17 20:30 ` Lars Magne Ingebrigtsen
2011-03-17 20:35 ` James Cloos
[not found] ` <87d3ln9b7y.fsf@stupidchicken.com>
2011-03-20 1:41 ` Ted Zlatanov
2011-03-20 3:06 ` Stefan Monnier
2011-03-20 12:20 ` Ted Zlatanov
2011-03-21 14:20 ` Stefan Monnier
2011-03-21 19:42 ` Ted Zlatanov
2011-03-21 22:14 ` Stefan Monnier
2011-03-22 2:01 ` Ted Zlatanov
2011-03-29 19:22 ` Lars Magne Ingebrigtsen
2011-03-29 19:34 ` Application resource storage (was: Outgoing mail defaults) Lars Magne Ingebrigtsen
2011-03-29 19:58 ` Application resource storage Ted Zlatanov
2011-03-29 20:14 ` Lars Magne Ingebrigtsen
2011-03-29 21:02 ` Ted Zlatanov
2011-03-29 20:51 ` chad
2011-03-22 11:26 ` Outgoing mail defaults Simon Josefsson
2011-04-16 16:45 ` Lars Magne Ingebrigtsen
2011-04-16 16:47 ` Lars Magne Ingebrigtsen
2011-04-16 16:51 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57C2C312-5FE3-4152-8ACB-8761813E8692@gmail.com \
--to=chadpbrown@gmail.com \
--cc=david.reitter@gmail.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).