mailman

[Peter Holm]

Hi,

I am new to mailman and after apt-get install mailman following the
INSTALL doc I tried a check_perms, that gave me lots of errors. Trying
to fix these with -f gave even more errors. 

Is this normal? Did I something wrong? 
Are there any special things I have to do to get it running?

Thanks for your attention!




debian:/usr/lib/mailman/bin$ ./check_perms
/var/lib/mailman/archives bad gid (has: list, expected anon gid 38)
/var/lib/mailman/lists bad gid (has: list, expected anon gid 38)
/var/lib/mailman/qfiles bad gid (has: list, expected anon gid 38)
/var/lib/mailman/data bad gid (has: list, expected anon gid 38)
/var/lib/mailman/spam bad gid (has: list, expected anon gid 38)
/var/lib/mailman/icons bad gid (has: list, expected anon gid 38)
/var/lib/mailman/templates bad gid (has: list, expected anon gid 38)
/var/lib/mailman/logs bad gid (has: list, expected anon gid 38)
/var/lib/mailman/locks bad gid (has: list, expected anon gid 38)
/var/lib/mailman/Mailman bad gid (has: list, expected anon gid 38)
/var/lib/mailman/bin bad gid (has: list, expected anon gid 38)
/var/lib/mailman/cron bad gid (has: list, expected anon gid 38)
/var/lib/mailman/filters bad gid (has: list, expected anon gid 38)
/var/lib/mailman/mail bad gid (has: list, expected anon gid 38)
/var/lib/mailman/scripts bad gid (has: list, expected anon gid 38)
/var/lib/mailman/mailman bad gid (has: list, expected anon gid 38)
/var/lib/mailman/archives/private bad gid (has: list, expected anon
gid 38)
/var/lib/mailman/archives/public bad gid (has: list, expected anon
gid 38)
/var/lib/mailman/data/pending_subscriptions.db bad gid (has: list,
expected anon gid 38)
/var/lib/mailman/data/last_mailman_version bad gid (has: list,
expected anon gid 38)
Problems found: 20
Re-run as uid 38 (or root) with -f flag to fix

debian:/usr/lib/mailman/bin$ ./check_perms -f
/var/lib/mailman/archives bad gid (has: list, expected anon gid 38)
(fixing)
Traceback (most recent call last):
  File ./check_perms, line 277, in ?
checkall()
  File ./check_perms, line 137, in checkall
os.path.walk(d, checkwalk, STATE)
  File /usr/lib/python2.1/posixpath.py, line 269, in walk
func(arg, top, names)
  File ./check_perms, line 100, in checkwalk
os.chown(path, -1, MAILMAN_GID)
OSError: [Errno 1] Operation not permitted:
'/var/lib/mailman/archives'




Have a nice thread,
Peter


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Exim (v3) - How to configure a backup MX?

[Dominik Schulz]

Hi,
I'm wondering how it's possible to configure Exim as a Backup-MX for my
Primary-MX. The Backup-MX should recieve all Mails adressed to him and
try every x Minutes (let x be 5) to forward them to the primary MX. In case
this fails it should keep on trying for an unlimited time.

The background:
My Primary-MX is going to have a scheduled downtime of about 12 to 36
hours and since there is relatively high mail traffic it'd be very  inconvenient
to lose some of them. Since I've got another spare server in the same
data center I'd like to use this as a primary MX as described above.
I've got no problems setting up the DNS-stuff or installing Exim -  since
it runs very well on the primary mx - but I just don't know how I can
get it working like described above.

Any help would be greatly appreciated.

Mit freundlichen Gruessen / Best regards
Dominik Schulz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Exim (v3) - How to configure a backup MX?

[Dale E Martin]

 I'm wondering how it's possible to configure Exim as a Backup-MX for my
 Primary-MX. The Backup-MX should recieve all Mails adressed to him and
 try every x Minutes (let x be 5) to forward them to the primary MX. In
 case this fails it should keep on trying for an unlimited time.

All you do is add the primary's domain to the domains you'll relay for.
Say the domain you want a secondary for is primary.com, and the secondary
MX will be on mail.secondary.com.  Then in your exim config in
mail.secondary.com, you'd put:

relay_domains = primary.com

Now, when mail flows in for primary.com, you'll queue it and attempt to
deliver it as per the normal rules.

Later,
Dale
-- 
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
[EMAIL PROTECTED]
http://www.cliftonlabs.com
pgp key available


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]