On 11/13/2008 6:41 AM, Patricia A Moss wrote:
I have already run that test and mail from the system, itself, sends
fine. It is just from mailman that there is a problem.
Good. That means that basic MTA functionality is working.
This is the "From" address of the test email: root
<[EMAIL PROT
Troy Knabe wrote:
>I have several lists that I do not want mailman moderating for size,
>implicit destination addresses, too many recipients, etc.
>
>But I would like mailman to moderate non-members posting, etc. How do
>I alter the settings for the above moderations?
On General Options
Ma
[EMAIL PROTECTED] wrote:
> By diabling SELinux altogether it worked.
If you don't want to keep SELinux disabled, it should be possible to
make mailman work without too much trouble. I do know that the Red
Hat packages install mailman in locations that are more FHS compliant
to help ease the writi
I have several lists that I do not want mailman moderating for size,
implicit destination addresses, too many recipients, etc.
But I would like mailman to moderate non-members posting, etc. How do
I alter the settings for the above moderations?
Thanks
-Troy
---
[EMAIL PROTECTED] wrote:
>By diabling SELinux altogether it worked. My only question is regarding
>what you said earlier, the working was a bit confusing for me:
>
>> > Then you need to remove any mailman aliases from /etc/aliases or
>> > whereever they were before if not
>> /usr/local/mailman/da
Everything is working now! I am able to create a list via the
interface. I read a thread where someone disabled SELinux, then
re-enabled it, and then rebooted and it worked for them. Sure enough it
worked for me too. Not sure why. I am still wanting to know about the
aliases though.
Thanks
By diabling SELinux altogether it worked. My only question is regarding
what you said earlier, the working was a bit confusing for me:
> > Then you need to remove any mailman aliases from /etc/aliases or
> > whereever they were before if not
> /usr/local/mailman/data/aliases, and
> > run 'postali
[EMAIL PROTECTED] wrote:
>My maillog shows:
>
>Nov 14 16:43:27 lists postfix/smtp[18085]: 60CE58C0013:
>to=<[EMAIL PROTECTED]>,
>relay=relay.washburnlaw.edu[198.252.9.211]:25, delay=0.18,
>delays=0.1/0.02/0.05/0.02, dsn=2.0.0, status=sent (250 Message accepted
>for delivery)
>Nov 14 16:43:27 lists
Ok, I stand corrected. Mail is working fine!
My problem is issuing the genaliases command. If it only works for root
when SELinux is off it should work for the user mailman. I have also
added the hash:/usr/local/mailman/data/aliases to my alias_maps in
/etc/postfix/main.cf
Jewel
- Ori
My maillog shows:
Nov 14 16:43:27 lists postfix/smtp[18085]: 60CE58C0013:
to=<[EMAIL PROTECTED]>,
relay=relay.washburnlaw.edu[198.252.9.211]:25, delay=0.18,
delays=0.1/0.02/0.05/0.02, dsn=2.0.0, status=sent (250 Message accepted
for delivery)
Nov 14 16:43:27 lists postfix/qmgr[1858]: 60CE58C0013:
[EMAIL PROTECTED] wrote:
>When I add: MTA='Postfix' to my mm_cfg.py file mail stops getting
>delivered. I don't see anything suspicous in my logs to help. I
>checked to confirm that the OutgoingRunner hasn't died. Postfix appears
>to still be livering based on it's logs saying 'sent'. Anyone e
When I add: MTA='Postfix' to my mm_cfg.py file mail stops getting
delivered. I don't see anything suspicous in my logs to help. I
checked to confirm that the OutgoingRunner hasn't died. Postfix appears
to still be livering based on it's logs saying 'sent'. Anyone else had
this issue?
Jewel
--
Jewel wrote:
>I have one list which won't display online the archives. I don't
>receive any web page error, it's just blank. I also have confirmed the
>archives are listed in the directory and that I can view them from the
>command line. I have the correct permissions.
What is the content of
On 11/13/08 12:33, Brad Knowles wrote:
There's your problem. Somehow your watermark got set ridiculously high,
or the news server decided to re-number all their articles into a much
lower range, and from now until the end of eternity, you're not going to
find any "new" articles to pull out of
On 11/13/08 11:53, Mark Sapiro wrote:
You may have never seen this because it may be a one-time transient
error. Or, if it did show up from cron, it would probably be emailed
as output from the cron, which would be sent to 'mailman' unless you
have a MAILTO in the crontab, and depending on how
I have one list which won't display online the archives. I don't
receive any web page error, it's just blank. I also have confirmed the
archives are listed in the directory and that I can view them from the
command line. I have the correct permissions.
--
Jewel r
On 11/13/08 13:22, Taylor, Grant wrote:
I do believe that sounds completely plausible and is exactly the type of
problem that I was thinking was going on. Well very close. It does
appear to be related to the ""remembered messages not being correct (as
opposed to being corrupted).
I just rec
Petersen, Kirsten J wrote:
>I'm looking for some help finding out why a message was not delivered to
>one of our lists.
>
>We're running Mailman 2.1.10 on Debian.
>
>I tracked the message from our postfix relays to the Mailman server,
>where I see the following in the smtp log:
>
>smtp.1:Nov 12
I'm looking for some help finding out why a message was not delivered to
one of our lists.
We're running Mailman 2.1.10 on Debian.
I tracked the message from our postfix relays to the Mailman server,
where I see the following in the smtp log:
smtp.1:Nov 12 17:27:08 2008 (6917)
<[EMAIL PROTECTE
It's fixed! Once I changed the permissions on my private directory using:
chmod o+x private
I was able to access the public archives.
Thanks!
Jewel
Mark Sapiro wrote:
drwxrws--- 202 mailman mailman 12288 Nov 14 09:15 private
drwxrwsr-x 2 mailman mailman 4096 Nov 14 09:15 public
At
[EMAIL PROTECTED] wrote:
>I have a few lists which are public and they are not accessible, which I
>cannot figure out why. I have several thread which talk about this
>exact problem but their solutions have not helped.
>
>Here is what's in my httpd.conf file:
>ScriptAlias /mailman/ /usr/local/m
I have a few lists which are public and they are not accessible, which I
cannot figure out why. I have several thread which talk about this
exact problem but their solutions have not helped.
Here is what's in my httpd.conf file:
ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/
Alias /pipermail
22 matches
Mail list logo
