francis picabia wrote:
>>>
>>> On second thought what we needed is similar, but probably:
>>>
>>> SENDER_HEADERS = ('from')
>>>
>>> Would there be problems "from" this?
It should be
SENDER_HEADERS = ('from',)
The comma is important. It makes SENDER_HEADERS a tuple with one
member. Without the c
On Thu, Oct 27, 2011 at 11:22 AM, francis picabia wrote:
> On Thu, Oct 27, 2011 at 10:07 AM, francis picabia wrote:
>> On Thu, Oct 27, 2011 at 9:54 AM, francis picabia wrote:
>>> On Thu, Oct 27, 2011 at 9:37 AM, francis picabia wrote:
Hello,
We run a mailing list for staff which
On Thu, Oct 27, 2011 at 10:07 AM, francis picabia wrote:
> On Thu, Oct 27, 2011 at 9:54 AM, francis picabia wrote:
>> On Thu, Oct 27, 2011 at 9:37 AM, francis picabia wrote:
>>> Hello,
>>>
>>> We run a mailing list for staff which should not
>>> receive email from outside of the list membership.
On Thu, Oct 27, 2011 at 9:54 AM, francis picabia wrote:
> On Thu, Oct 27, 2011 at 9:37 AM, francis picabia wrote:
>> Hello,
>>
>> We run a mailing list for staff which should not
>> receive email from outside of the list membership.
>>
>> The only non-member address allowed to post is
>> another
On Thu, Oct 27, 2011 at 9:37 AM, francis picabia wrote:
> Hello,
>
> We run a mailing list for staff which should not
> receive email from outside of the list membership.
>
> The only non-member address allowed to post is
> another mailing list.
>
> Today we received a post from p...@kijiji.ca
> a
Hello,
We run a mailing list for staff which should not
receive email from outside of the list membership.
The only non-member address allowed to post is
another mailing list.
Today we received a post from p...@kijiji.ca
and it made it through to the list.
I see this in the post log file:
Oct
Russell L. Carterwrote:
>
>On 10/27/2011 04:33 PM, Mark Sapiro wrote:
>
>>> What's the Right Way to fix this so that clicking the visit archives
>>> link on a new list doesn't result in a 403 Forbidden barf?
>>
>>
>> Make the archives/private/ directory searchable by the web server.
>> Either
>>
On 10/27/2011 04:33 PM, Mark Sapiro wrote:
>> What's the Right Way to fix this so that clicking the visit archives
>> link on a new list doesn't result in a 403 Forbidden barf?
>
>
> Make the archives/private/ directory searchable by the web server.
> Either
>
> chown www-data:list archives/p
Mark Sapiro wrote:
>
>Because the archives are always in the archives/private/ tree and
>archives/public contains only symlinks to archives/public.
That should be
archives/public contains only symlinks to archives/private.
--
Mark Sapiro The highway is for gamblers,
San Francisco Bay A
Russell L. Carter wrote:
>I've just brought up mailman on a debian-testing box
>and almost everything works. (Hooray!) The problem I'm having
>is that after creating a list, subscribing a user, and
>sending a message to the list, I go to the list info
>page:
>
>http://lists.pinyon.org/listinfo/tes
Greetings,
I've just brought up mailman on a debian-testing box
and almost everything works. (Hooray!) The problem I'm having
is that after creating a list, subscribing a user, and
sending a message to the list, I go to the list info
page:
http://lists.pinyon.org/listinfo/testing3
and click on ..
Christopher Adams wrote:
>
>If an individual sends a priority message via Outlook to a Mailman
>list, does it assume that it is a bcc?
No.
>I was able to verify that the
>person sent the message directly to the list, but the message was sent
>to the administrator with the "implicit destination"
Hello,
If an individual sends a priority message via Outlook to a Mailman
list, does it assume that it is a bcc? I was able to verify that the
person sent the message directly to the list, but the message was sent
to the administrator with the "implicit destination" tag. I realize
that I can contr
13 matches
Mail list logo
