public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: FW: Good old nabble
Date: Tue, 18 Apr 2006 23:55:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.63.0604181951080.21441@access1.cims.nyu.edu> (raw)
In-Reply-To: <20060418234349.GC776@trixie.casa.cgf.cx>

On Tue, 18 Apr 2006, Christopher Faylor wrote:

> On Tue, Apr 18, 2006 at 03:50:42PM -0700, Rod Morris wrote:
>
> >You're right, we need to resolve this problem. Right now, the
> >message gets posted locally and we forward the email to the list
> >using the Nabble user's registered email address as the sender.
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >If the user's post is rejected or if the user doesn't complete the
> >subscription process or if he gets banned from the list, we would
> >only know because we never get the message back from the list.
>
> I can't quite parse the above but ezmlm does send a bounce message when
> lists@nabble.com tries to send a message to the cygwin-apps mailing
> list.

I think I can parse it.  Look at the underlined text above.  I believe
this means that the bounce goes back to the user, and the Nabble software
never receives it...

> >Currently, we assume that the user screwed up the confirmation step and
> >we send him an email once a day to remind him to complete it and tell
> >him that the message didn't go through. But if that never happens, then
> >we do have a problem.
> >
> >Flag these messages as 'Pending' sounds like a good idea. I can have our
> >UI guy come up with something that makes sense and will make it obvious.
>
> nabble is blocked from sending emal to cygwin-apps.  So no matter what
> process the user goes through on your end, their messages will never
> show up in the cygwin-apps mailing list.

Hmm, does Nabble actually try to subscribe them to the list? :-o

> >Then what? Should we delete them from the archive if they don't go
> >through after some period of time, a weeks perhaps?
>
> You're calling this "an archive" but it is not an archive of cygwin-apps
> if it (even briefly) contains a copy of a message which never was part
> of actual cygwin-apps traffic.
>
> Can you mark sourceware's subscriber-only mailing lists as read-only on
> your end so that attempts to send a message are blocked immediately?
>
> OTOH, you could also notice when sourceware sends you a message
> indicating that your message was denied and remove the message.

Can Nabble be set up so that the bounce message goes to Nabble and not to
the user?
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

  reply	other threads:[~2006-04-18 23:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-18 22:50 Rod Morris
2006-04-18 23:43 ` Christopher Faylor
2006-04-18 23:55   ` Igor Peshansky [this message]
2006-04-19 18:07     ` Nabble Support
2006-04-19 17:52   ` Rod Morris
2006-04-19 18:06     ` Dave Korn
  -- strict thread matches above, loose matches on Subject: below --
2006-04-18 16:23 Dave Korn
2006-04-18 16:36 ` Christopher Faylor
2006-04-18 17:08   ` Igor Peshansky
2006-04-18 17:27     ` Dave Korn
2006-04-18 17:44       ` Igor Peshansky
2006-04-18 17:40     ` Christopher Faylor

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=Pine.GSO.4.63.0604181951080.21441@access1.cims.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin-talk@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).