> "Jon" == Jon Carnes <[EMAIL PROTECTED]> writes:
Jon> The browser connection manages to create the lock files but
Jon> then it stops and refuses to authenticate. I'm fairly
Jon> certain it is using an old cookie at this point.
Well, the obvious and pleasant solution is
1) rev
Howdy,
Is Mailman vulnerable to mail-loops caused by auto-responders
that are configured to look like an email sent by a person?
If not, how does Mailman discern that an email from a person
is actually from an auto-responder and visa versa.
Thanks,
--Paul
--
"Yesterday's the past and tomorr
I have a similar problem which I've traced down to Internet Explorer and bad
or old Mailman cookies.
I've seen a lot of problems with IE6 (and now IE5.5 after the last security
upgrade... damn MS). The browser connection manages to create the lock
files but then it stops and refuses to authentic
Thanks to all who replied.
I'm a bonehead. I botched the cron (yes, there was plenty in the qfiles dir
;). I re-reran crontab for crontab.in in and everything works like a charm.
It did help hearing the replies none-the-less (to understand overall
function).
Thanks for the help and patience <:)
it does indeed sounf like the problem is with cron. Everything else sounds
like it's working properly, but cron is never calling qrunner to proccess
it. Can you look in your ~mailman/qfiles dir and see if there's anything in
there? If it's full of unprocessed .msg, and .db files, then the cron, or
At 10:38 17/01/2002 -0600, Alex Sammons wrote:
>Does anyone have a script now to subscribe a lot of
>users in my unix system taking the input from a file,
>changing /etc/passwd, /etc/group,etc
>
> Thanks!
>
>__
why not look at using the $prefix/bin/add_members script
>
Paul,
The logs (/usr/local/mailman/logs/*) show things (i.e. subscribe and smtp)
that have been done via the web interface. Nothing shows up at all from
anything done by email (piped by postfix to the mailman scripts).
The only thing the system logs show is that postfix successfully (?) pipes
th
Does anyone have a script now to subscribe a lot of
users in my unix system taking the input from a file,
changing /etc/passwd, /etc/group,etc
Thanks!
_
Do You Yahoo!?
Encuentra el coche de tus sueños en Yahoo! Autos http:
Sorry if this has been answered before...
I'm using Mailman 2.0.8 w/ postfix on freebsd 4.5 PRE-.
I have set up a test list. All functions appear to work via the web
interface. The problem is that none of the email subscriptions, posts,
confirmations, etc. via email are working.
They are gett
I am having a serious problem with mailman with lists getting
apparently corrupted and becoming none functional. The first symptom
is you try to send a piece of mail to a list and it does nothing. The
email just disappears into a black hole. There is a record in the
maillog that them message c
OK - I have a permission problem that I can't seem to find. I have run
check_perms and changed my --with-mail-gid settings and tried some different
combinations. I think it has something to do with the permission of my
/home/mailman/mail directory? I looked though the FAQ's and the issues
there
At 12:30 17/01/2002 +0100, Krause, Uwe wrote:
>Hello,
>
>maybe a FAQ (but i havent found it in the FAQ`s).
>How can i prevent sending out messages with attachments for a respective
>list ?
>We run several lists on the host, but one list-manager ask for prevent his
>list against
>html (simple sol
Hello,
maybe a FAQ
(but i havent found it in the
FAQ`s).
How can i
prevent sending out
messages with attachments for a respective list
?
We run several lists
on the host, but one list-manager ask for
prevent his list against
html (simple
solution -> stripmime.pl) and any attachments (
At 16:50 16/01/2002 -0600, Gary McClellan wrote:
>On Wed, 16 Jan 2002 16:42:33 -0500, Jon Carnes wrote:
>
> >some effects of mm_cfg are immediate, but the parts that act as defaults to
> >the list are incorporated into the list when it is created. You will have
> >to change already created lists
> I think you will find this problem arises if the list the
> attachment is directed at is being archived and it is the internal
archiver
> code that is digging its way to the centre of the earth. I may be wrong
> but try turning of archiving for lists to which you allow large
attachments
> to
I fixed it.
It was slightly embarrasing really.
Apparently there were two aliases to mailman in httpd.conf.
One ScriptAlias and one Alias pointing /prefix/mailman/.
Apparently it used the Alias (without cgi).
mvh/ Regards,
Martin S.
CTO, Forum Syd
"To err is human--and to blame it on a compute
16 matches
Mail list logo
