Finally, I changed using withlist the URL to the IP address and that
made things point to things in a better fashion, but now I get the
infamous message:
Forbidden
You don't have permission to access /pipermail/linuxmednews-announce
on this server.
Apache/2.2.6 (Fedora) Server at 7 2.5 1.3 x9 .1
Also, my mailman.conf file looks like this which should redirect to
the archives and everything else properly but doesn't seem too. -- IV
#
# httpd configuration settings for use with mailman.
#
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
AllowOverride None
Options ExecCGI
Order
Hi Chris, A ServerBeach admin added this to httpd.conf
DocumentRoot /var/www/html
ServerAdmin [EMAIL PROTECTED]
which fixed it so that I can use both Zope and and I can now get to
the Mailman web interface page, but I get an error with the archive
URL and I don't know how to get it t
Hi,
We run Mailman 2.1.5 on Mac OS X 10.4.11 Server. Postfix 2.1.5 is the
SMTP server. A number of our subscribers who are sent digests are not
able to receive them. The digest messages are bouncing with the error
message:
Action: failed
Status: 5.6.1
Diagnostic-Code: smtp;554 5.6.1 Body typ
On 12/2/07, Noel da Costa wrote:
> It sounds, from what you are saying, that I shouldn't need to set the
> aliases up manually via the management console if Postfix is
> correctly integrated.
Correct. What will happen is that, as new lists are created, Mailman
will add the appropriate aliase
Hi all,
Thanks for the replies so far.
> From: "Shadow" <[EMAIL PROTECTED]>
> I would say that this line shows the problem
> Diagnostic-Code: smtp; 550 <[EMAIL PROTECTED]>: invalid address
Yes, I agree.. but I'm not sure how to add a mail alias to my domain
if not through the admin console.
On Sat, 1 Dec 2007, Ignacio Valdes wrote:
> I'm running a Zope instance that requires me to have re-write rules
> (below) in httpd.conf that are not compatible with Mailman. I can use
> mailman if I don't use the Zope re-write rules or I can use Zope but
> not mailman with the re-write rules below
