From: Oliver B. <ob...@de...> - 2003-12-08 11:43:58
|
Hello All, wouldn't it be nice if this list would set the Reply-To: to the list address? Many times I forget to correct the address when answering to the list, and the reply goes to the poster instead of the list. And I would also set the list to accept mail only from subscribers due to two reasons: spammers send mail to this list *), and I don't want to send (successfully) by accident with the mail address of my employer. Oliver *) the "Remote Control Boats" guy is a very nasty spammer - he used also mail addresses from our domain so I get bounces now... Sadly he is too far away from Europe to LART him. |
From: Bishop <bi...@pl...> - 2003-12-15 06:34:40
|
> Hello All, > > wouldn't it be nice if this list would set the Reply-To: to the list > address? Many times I forget to correct the address when answering to > the list, and the reply goes to the poster instead of the list. -1 I don't usually write so much mail to so many people, just so that my mail isn't soon seen as 'spam.' Likewise, although I have procmail weeding out these reply-to addresses, my preference is also that lists DON'T force replies back to the list. Replying only to the author of a message - unless the message specifically should be one addressed to the entire list - and having the author of the original messages assemble a follow-up to his/her original post in order summarise the responses, helps keep mail traffic down while still keeping the information high. Signal/noise and all that. > And I would also set the list to accept mail only from subscribers > due to two reasons: spammers send mail to this list *), and I don't > want to send (successfully) by accident with the mail address of my > employer. +1 While that one's a bit of a hassle to force posters to subscribe, it avoids a lot of crap posting from spammers who may be wanting to harvest brain dead 'away'/'vacation' messages. A product of the times, setting member-only to posts on a list is now almost a required thing. In short, I'm all about signal-noise ratios. |
From: Carsten K. <car...@us...> - 2003-12-16 21:00:11
|
On Monday, December 15, 2003, at 01:34 am, Bishop wrote: >> Hello All, >> >> wouldn't it be nice if this list would set the Reply-To: to the list >> address? Many times I forget to correct the address when answering to >> the list, and the reply goes to the poster instead of the list. > > -1 > > I don't usually write so much mail to so many people, just so that my > mail > isn't soon seen as 'spam.' Likewise, although I have procmail weeding > out > these reply-to addresses, my preference is also that lists DON'T force > replies back to the list. Replying only to the author of a message - > unless the message specifically should be one addressed to the entire > list > - and having the author of the original messages assemble a follow-up > to > his/her original post in order summarise the responses, helps keep mail > traffic down while still keeping the information high. Signal/noise > and > all that. > >> And I would also set the list to accept mail only from subscribers >> due to two reasons: spammers send mail to this list *), and I don't >> want to send (successfully) by accident with the mail address of my >> employer. > > +1 > > While that one's a bit of a hassle to force posters to subscribe, it > avoids a lot of crap posting from spammers who may be wanting to > harvest > brain dead 'away'/'vacation' messages. A product of the times, setting > member-only to posts on a list is now almost a required thing. > > In short, I'm all about signal-noise ratios. I prefer not to force a Repy-To address. Just remember to hit "Reply-all" in your email software when replying to a list posting (and if needed, then delete either the poster's name from the CC, or the list name from CC). However I *would* like to add a Reply-To header for only the phpwiki-checkins list to make sure followups don't get posted to the checkins list, rather to phpwiki-talk instead. Further reading: Quote from Mailman docs on SF: > There are many reasons not to introduce or override the Reply-To: > header. One is that some posters depend on their own Reply-To: > settings to convey their valid return address. Another is that > modifying Reply-To: makes it much more difficult to send private > replies. See 'Reply-To' Munging Considered Harmful for a general > discussion of this issue. See 'Reply-To Munging Considered Useful' > for a dissenting opinion. Reply-To Munging Considered Useful http://www.metasystema.net/essays/reply-to.mhtml "Reply-To" Munging Considered Harmful http://www.unicom.com/pw/reply-to-harmful.html Carsten |
From: Bishop <bi...@pl...> - 2003-12-17 02:57:57
|
> However I *would* like to add a Reply-To header for only the > phpwiki-checkins list to make sure followups don't get posted to the > checkins list, rather to phpwiki-talk instead. > Carsten Carsten, That's a good exception to my normal opinion on it. I'm totally in agreement - FWIW - that it's a Good Thing. The commits lists should be admin-only-posting as well as replies directed to another list, so that only the commits will ever be on the commits list. Hmm. Now I'll have to toss something into my procmail recipe (package) so that I can turn OFF the reply-to-munging on incoming mail from the commits list... - bish |
From: Oliver B. <ob...@de...> - 2003-12-17 07:44:23
|
Carsten Klapp wrote: [...] > I prefer not to force a Repy-To address. Just remember to hit > "Reply-all" in your email software when replying to a list posting (and most people will forget (or even ignore) to delete the poster's address and the poster receives the answer twice. [...] > "Reply-To" Munging Considered Harmful > http://www.unicom.com/pw/reply-to-harmful.html interestig reading (thanks!), although very elm-centric. Many mail readers don't support an easy way to reply _only_ to the To: address. Pegasus does (if configured correctly), but I simply forget it. Since most replies (should) go to the list, I am still convinced that the list address should be the default offered by the mail reader. The important argument is IMHO what you cited from the Mailman docs: "...that some posters depend on their own Reply-To: settings to convey their valid return address." although I don't know the circumstances why one can't set the From: accordingly. Oliver |
From: <jw...@fi...> - 2003-12-17 08:48:23
|
Hello, I added a small patch to the sources in order to have a "copypage" functionality : When doing an action=3DEdit©page=3DMyPage, The resulting textarea is prefilled with the content of MyPage This allows, via a patched Calendar plugin for example, to have a single prefilled template every time you want to add an entry in the calendar. I'd like to know if there already is such a functionality in the wiki, = if it interests anyone, and how we could to do add such a thing in the code = base. Thanx J=E9r=F4me -----Message d'origine----- De=A0: php...@li... [mailto:php...@li...] De la part de Oliver = Betz Envoy=E9=A0: mercredi 17 d=E9cembre 2003 08:44 =C0=A0: php...@li... Objet=A0: Re: [Phpwiki-talk] Configuration of this list: Reply-To:, = acceptance Carsten Klapp wrote: [...] > I prefer not to force a Repy-To address. Just remember to hit=20 > "Reply-all" in your email software when replying to a list posting = (and=20 most people will forget (or even ignore) to delete the poster's=20 address and the poster receives the answer twice. [...] > "Reply-To" Munging Considered Harmful > http://www.unicom.com/pw/reply-to-harmful.html interestig reading (thanks!), although very elm-centric. Many mail=20 readers don't support an easy way to reply _only_ to the To: address.=20 Pegasus does (if configured correctly), but I simply forget it. Since=20 most replies (should) go to the list, I am still convinced that the=20 list address should be the default offered by the mail reader. The important argument is IMHO what you cited from the Mailman docs:=20 "...that some posters depend on their own Reply-To: settings to=20 convey their valid return address." although I don't know the=20 circumstances why one can't set the From: accordingly. Oliver ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for = IBM's Free Linux Tutorials. Learn everything from the bash shell to sys = admin. Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick _______________________________________________ Phpwiki-talk mailing list Php...@li... https://lists.sourceforge.net/lists/listinfo/phpwiki-talk |
From: Reini U. <ru...@x-...> - 2003-12-17 12:29:52
|
please attach your patch to an email or post it at sf.net. we will review it and add it to the current CVS. very good idea indeed! Jérôme WAGNER schrieb: > I added a small patch to the sources in order to have a "copypage" > functionality : > > When doing an action=Edit©page=MyPage, > > The resulting textarea is prefilled with the content of MyPage > > This allows, via a patched Calendar plugin for example, to have a single > prefilled template every time you want to add an entry in the calendar. > > I'd like to know if there already is such a functionality in the wiki, if it > interests anyone, and how we could to do add such a thing in the code base. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: <jw...@fi...> - 2003-12-17 14:11:30
Attachments:
lib_editpage.php.diff
lib_plugin_Calendar.php.diff
|
Hello again, Here are the patches for the "copypage" functionnality - The modification in editpage.php catches the copypage argument and = forces this page to be chosen as the basis for edition - The modification in Calendar adds the "copypage" argument to the = plugin. This way, when a user clicks on a date, the "empty" wiki page that is = opened contains the same content as the copypage Page e.g. <?plugin Calendar copypage=3DMyChosenExistingTemplatePage?> I hope the patches have been made at the best places in the phpwiki = code, and that you will be able to tweak them into the project code base. Keep me posted! J=E9r=F4me -----Message d'origine----- De=A0: Reini Urban [mailto:ru...@x-...]=20 Envoy=E9=A0: mercredi 17 d=E9cembre 2003 13:30 =C0=A0: J=E9r=F4me WAGNER Cc=A0: php...@li... Objet=A0: Re: [Phpwiki-talk] copypage functionnality please attach your patch to an email or post it at sf.net. we will review it and add it to the current CVS. very good idea indeed! J=E9r=F4me WAGNER schrieb: > I added a small patch to the sources in order to have a "copypage" > functionality : >=20 > When doing an action=3DEdit©page=3DMyPage, >=20 > The resulting textarea is prefilled with the content of MyPage >=20 > This allows, via a patched Calendar plugin for example, to have a = single > prefilled template every time you want to add an entry in the = calendar. >=20 > I'd like to know if there already is such a functionality in the wiki, = if it > interests anyone, and how we could to do add such a thing in the code base. --=20 Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: John K. <jo...@ke...> - 2003-12-17 08:56:16
|
At 8:44 am +0100 17/12/03, Oliver Betz wrote: >The important argument is IMHO what you cited from the Mailman docs: >"...that some posters depend on their own Reply-To: settings to >convey their valid return address." although I don't know the >circumstances why one can't set the From: accordingly. I can think of one that applies directly to mailing lists. Someone may subscribe to the list using one address, but want replies to go to another address, because: a) they subscribed address is an old one and they can't be bothered/don't wish to subscribe with their new address, but still have to POST (From) using the old address b) they subscribed using a dummy/spamproofed address but want mail to go to their real address c) they post from their work address but want replies to go to their home address d) they use a webmail app such as mali2web, which puts their real POP address in the From and their desired 'who I am known as' address in the Reply-To OTOH I hit 'Reply' to your message, spotted it was going to you not the list, closed the message, hit cmd-opt-R to Reply-To-All, then had to tab back into the 'To' field to remove Oliver Betz so you wouldn't get two copies. That's 7 key presses and a whole lot of thinking compared to the one brainless key press that I need for all the other lists to which I'm subscribed. I have enough thinking to do without adding more :( And I'm not convinced by the 'reply to the sender and let them summarise back to the list' argument. Very often a post will go to the list, be replied to by several persons and those replies spark further replies. Those replies *then* generate further posts, which might not have happened if the first round of posts had gone just to the original sender. I thought mailing lists were about pooling the experience & knowledge of everyone? I'm person A is having a problem, person B has probably already solved it, person C is stuck with the same problem but has some insight/situation that bears on the matter and person D will encounter it in the future. If C posts directly to A, and so does B, B doesn't see C's post and can't comment on it, answering only A's direct point, not creating a generalised solution for when D hits the snag. John. -- ------------------------------------------- 01274 581519 / 07944 755613 jo...@ke... / http://www.kershaw.org AOL johnkershaw / Y! & MSN john_m_kershaw |