| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-www(at)postgresql(dot)org |
| Subject: | Re: reply-to set |
| Date: | 2013-07-30 18:20:06 |
| Message-ID: | CAM-w4HMnfbM34aL6di1Ui6pDnLgMgG9tfRmhesDLW1adoBz4mQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Tue, Jul 30, 2013 at 6:52 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> There are always bad mail hosts who send any bounce message to FROM (or
> REPLY-TO) instead of any other address.
Yes, but setting reply-to won't make those any worse. We should really
ban any such hosts from our lists.
> In general, I think reply-to for announce should be set to a black hole
> address (e.g. do-not-reply(at)postgresql(dot)org). There's never a good reason
> to reply to an -announce message.
I disagree with noreply addresses on principle. They usually just
represent the sender being lazy and not thinking hard enough about
where replies should go. Why wouldn't there be a good reason to reply
to an announcement? I've often wanted to reply to announcements.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-07-30 19:24:37 | Re: reply-to set |
| Previous Message | Josh Berkus | 2013-07-30 17:52:06 | Re: reply-to set |