Tim wrote:
>
>We have a subscriber address that has /t on the end of it ([EMAIL
>PROTECTED]/t) which can only be seen when dumping the lists config file. The
>subscriber address looks normal [EMAIL PROTECTED]) when looking for it using
>any other method (list members, etc).
Do you mean '\t',
> On Thursday 23 February 2006 16:36, Jon D. Slater wrote:
>> I've been using Mailman for some time, and just recently installed
>> SpamAssassin on my Fedora Core 4, Linux machine.
>
> Spam-assassin would normally be used with the MTA (i.e. exim, qmail, etc.)
> and
> not Mailman. Basically, you s
> "Mark" == Mark Sapiro <[EMAIL PROTECTED]> writes:
Mark> Henrik wrote:
>> On 2/24/06, Mark Sapiro <[EMAIL PROTECTED]> wrote:
>>> Then maybe someone put it in Defaults.py. Let's hope Mandrake
>>> is not distributing its package this way.
>> They are, I'm afraid.
Mar
We are using Mailman v 2.1.4 on a Linux box with postfix and I am site admin.
We have a subscriber address that has /t on the end of it ([EMAIL PROTECTED]/t)
which can only be seen when dumping the lists config file. The subscriber
address looks normal [EMAIL PROTECTED]) when looking for it us
Jeff Donsbach wrote:
>Has anyone out there had any problems with their lists where messages
>were not being delivered to subscribers on Prodigy?
My prodigy users receive list posts OK.
>I have one user
>on Prodigy (small lists) that says he hasn't received any list emails
>for a while now. I c
Dennis Carr wrote:
>
>The problem, as I discovered completely by accident, is that the list
>owner also needs to be subscribed to the list - this is not
>automatically done in 2.1.5, which is what is current in Debian Sarge.
I don't know why that would be a problem unless the problem was that
the
