Bill Catambay wrote:
>I have an update on this. I was trying to pinpoint exactly what
>"change" caused this, and as I deleted changes, starting with the
>link, I still kept getting the same rejection. Then I just went to
>edit the page, and made no changes at all, clicked on Submit Changes,
Grant Taylor wrote:
>On 08/25/09 07:55, David Walker wrote:
>>
>> So my question is: how can I configure mailman to allow person to
>> post when he registered as person+mmusers
>
>I personally ran in to that very issue a while ago. My (sub-optimal)
>solution was to subscribe both "person" and
I have an update on this. I was trying to pinpoint exactly what
"change" caused this, and as I deleted changes, starting with the
link, I still kept getting the same rejection. Then I just went to
edit the page, and made no changes at all, clicked on Submit Changes,
and it *still* gave me the
On 08/25/09 07:55, David Walker wrote:
However mailman, doesn't. Since the "registered" user person+mmusers
exists and is all good, when person sends a message to the list it
gets bounced.
So my question is: how can I configure mailman to allow person to
post when he registered as person+mmu
On Tue, Aug 25, 2009 at 08:55:20AM -0400, David Walker wrote:
> Since the "registered" user person+mmusers exists and is
> all good, when person sends a message to the list it gets bounced.
>
> So my question is: how can I configure mailman to allow person to post when
> he registered as person+mm
I am trying to customize our Options page, and I want to add links to
our main website within the page (really the only changes I am
making). When I try to save, I get:
"The page you saved contains suspicious HTML that could potentially
expose your users to cross-site scripting attacks. This
Sorry if the subject is not quite clear, but I have a question on
configuring mailman. I set up a list for a group I'm apart of, and one
person uses easier to filter on email addresses. I guess I'll jump to the
example it'll make sense then
Suppose I had an email: per...@world.com
However, for
Stephen J. Turnbull writes:
> The email address which was dropped may have been the poster or an
> explicit recipient, with the appropriate "no dupes, please" flag set.
> There are two of these; 'not metoo' says "don't send to me when I am
> the poster," 'nodupes' "don't send to the post to me
