Wanjiku Maina wrote:
>Is it possible to use my passwd(Unix Authentication) file to authenticate in
>the list creators pass word in create.py in place of the file that it is
>using to authenticate?
Only by modifying the code in Mailman/Cgi/create.py
>Is there a script that I could use to authe
Is it possible to use my passwd(Unix Authentication) file to authenticate in
the list creators pass word in create.py in place of the file that it is
using to authenticate?
Is there a script that I could use to authenticate passwd file using python?
-
On May 10, 2005, at 04:22, James wrote:
> Is there a way to authenticate people by domain?
> For example, all people at domain.com should be able to email any
> lists at domain.com, while people outside the domain.com must be
> members to post to the list.
Adding a regular expression that matches
Is there a way to authenticate people by domain?
For example, all people at domain.com should be able to email any
lists at domain.com, while people outside the domain.com must be
members to post to the list.
--
Mailman-Users mailing list
Mailman
On Apr 8, 2005, at 18:06, Brad Knowles wrote:
At 11:09 PM -0700 2005-04-07, Lynn Siprelle wrote:
Exim logs tell me only this:
2005-04-07 22:54:38 H=sccrmhc14.comcast.net [204.127.202.59]
F=<[EMAIL PROTECTED]> rejected RCPT <[EMAIL PROTECTED]>:
authentication required
It was working fine until
At 8:52 AM -0700 2005-04-08, Lynn Siprelle wrote:
Could have done without the dollop of snark, but that's the internet.
I wasn't being snarky. I was being honest -- there are a few
Exim-knowledgeable people on this list, but most of them are over on
the mailing lists devoted to supporting Exim
It sounds like your ISP changed their configuration so as to require
authentication for outgoing mail. Or the remote MTA is misconfigured
so that it thinks you should have to authenticate before it will
accept your message.
Either way, this appears to be a problem you need to discuss with
t
At 11:09 PM -0700 2005-04-07, Lynn Siprelle wrote:
Exim logs tell me only this:
2005-04-07 22:54:38 H=sccrmhc14.comcast.net [204.127.202.59]
F=<[EMAIL PROTECTED]> rejected RCPT <[EMAIL PROTECTED]>:
authentication required
It was working fine until about 36 hours ago.
It sounds like your ISP c
Why is this happening? I tried searching the archives without success:
The following addresses had delivery problems:
<[EMAIL PROTECTED]>
Permanent Failure: 550_authentication_required
Delivery last attempted at Fri, 8 Apr 2005 05:53:18 -
Reporting-MTA: dns; comcast.net
Arrival
Hey all, I hope your holidays went well.
I have a few questions that I hope some one can answer or point me in
the correct direction. I'm a long time admin of Mailman installations,
but I was just recently given a project that would appear to stretch
what I know already about its internals.
I w
I did not run the configure script, it was already installed by the
host, just not configured.
I check in my apache httpd.conf file and i see that the group and user
apache runs under is apach.
In the documentation I now see that the default for Mailman is either
www, www-data, or nobody; apache
Did you configure with-cgi-gid set to your web server's gid?
On Thu, 13 Mar 2003, ben strawbridge wrote:
> Hello,
>
> I have just finished configuring mailman, and I have a list set up, but
> I can't access the administration pages through the website. I believe
> this is a permissions issue, bu
Hello,
I have just finished configuring mailman, and I have a list set up, but
I can't access the administration pages through the website. I believe
this is a permissions issue, but I can't find documentation. I have run
check_perms -f and it says everything is ok.
I'd love to get some help on
* Dave Stern - Former Rocket Scientist ([EMAIL PROTECTED]) wrote:
> > > AttributeError: 'Mailman.Cookie' module has no attribute 'SimpleCookie'
> >
> > Try cleaning out the cookies on the client machine. There have been
> > problems with old 2.0.13 cookies interfearing with 2.1 cookies.
> >
>
> S
On Mon, 24 Feb 2003, Matthew Davis wrote:
> * Dave Stern - Former Rocket Scientist ([EMAIL PROTECTED]) wrote:
> > I'm going from 2.0.13 to 2.1.1. The machine I want to first test it on
> > has no compiler so I copy the real mailman structures onto another machine,
> > (let's call it "test.domain")
* Dave Stern - Former Rocket Scientist ([EMAIL PROTECTED]) wrote:
> I'm going from 2.0.13 to 2.1.1. The machine I want to first test it on
> has no compiler so I copy the real mailman structures onto another machine,
> (let's call it "test.domain") have account, group, perms etc set up,
[snip]
> Tr
I'm going from 2.0.13 to 2.1.1. The machine I want to first test it on
has no compiler so I copy the real mailman structures onto another machine,
(let's call it "test.domain") have account, group, perms etc set up,
configure --prefix=/etc/mailman --build=test.domain \
--host=test.domain
make i
I have mailman setup with two virtual domains. Emails seem to work
fine, but authentication on one of the virtual domains does not work.
Primary: www.rupa.com/mailman/... works fine
virtual: list.gurukuli.com/mailman/... doens't.
The symptom is that I can "login" on the virtual, but any action a
I haven't seen this problem myself, but others who have seen it say to
delete all the old Cookies (that were generated from Mailman v2.0x).
There appears to be a problem with the structure of the old Cookie
files. Apparently, the problem goes away if you delete the old files
and then let the new M
Hello,
I apologize in advance if this is a dumb question, though I didn't
find anything about it in the archives or FAQ...
I've recently upgraded to mailman 2.1 on a redhat 8.0 system, and
since the upgrade list administrators are seeing a problem where they
go to the administration web page (the
I am sending this to the list mostly for the archives so that others who
have the same problem will not have to search as long as I did for the
solution. I also want to thank Richard for helping me by pointing me in the
right direction so that I could "logic" out the rest.
This is on a basic serve
hi all.
As a newbie I have installed mailman 2.0.13 with python 2.2.1c1 on Suse
8.0.
Login screen for admin appears and accepts my password but mailman
does not write any change and brings login screen again.
My browser accepts cookies properly also I have checked with different
machines an
My students and I keep getting a "user unknown" message back when I try to
subscribe to my list-serve. The message goes out fine. It is in the reply
that something gets fowled up. Is there something I have done wrong in the
configuration?
My main mail server is on a W2k box on the network. I
Finally I can get in after the USE_CRYPT=0...
Thanks for your attention!
On Thu, Nov 22, 2001 at 04:52:10PM +0800, Reed Lai wrote:
> Seniors,
>
> I just installed mailman and created a test list, but I can't get
> in from the page http://.../mailman/admin/test for configuration
> because always
Seniors,
I just installed mailman and created a test list, but I can't get
in from the page http://.../mailman/admin/test for configuration
because always "Authentication failed!"
Please help! Thanks!
--
Reed Lai http://w3.icpdas.com/reed/ | ICPDAS http://www.icpdas.com
GnuPG (DSA/ElGamal) 0x71
Mailman passwords implement a very mild level of
security.
We are using radius too and I never ever would pool it together
with a system which sends the passwords in cleartext and
e-mails through the network.
But if it is vital for you, you can override the mailman password
dead easy.
"Vania Lol
Does anyone have any ideas about using RADIUS to override internal mailman
password authentication for addresses inside the domain? We'd really like
our users to be able to have single sign-on.
Thanks,
Scott
--
Mailman-Users maillist - [EMA
>Is there any way to configure Mailman to authenticate posters against
>headers other than From:?
>
>I have a subscriber who frequently changes From: addresses, but has a
>consistent Reply-To: address, and Mailman is properly rejecting his posts
>because they originate from varying addressen
On Tue, 17 Apr 2001, JC Dill wrote:
> What I do (on a majordomo list) is have the person subscribe all the other
> "from" addresses to a companion list that is allowed to post to the main
> list. With Mailman, I believe you can accomplish the same thing in an
> easier fashion by having him subscr
On 07:58 PM 4/17/01, Ashton Treadway wrote:
>
>Hi:
>
>Is there any way to configure Mailman to authenticate posters against
>headers other than From:?
>
>I have a subscriber who frequently changes From: addresses, but has a
>consistent Reply-To: address, and Mailman is properly rejecting h
Hi:
Is there any way to configure Mailman to authenticate posters against
headers other than From:?
I have a subscriber who frequently changes From: addresses, but has a
consistent Reply-To: address, and Mailman is properly rejecting his posts
because they originate from varying addressen.
Tha
31 matches
Mail list logo
