Re: [Mailman-Users] maiman with postfix

2005-01-26 Thread Yassen Damyanov
I have this working but I have all my virtual domains listed here:

virtual_mailbox_domains = virt1.com, virt2.com, ..., virtn.com

Don't see your virtual_mailbox_domains = clause. Try with setting
it up. Also, you may need things like virtual_gid_maps, virtual_uid_maps

I have these things in my main.conf:

virtual_gid_maps = static:1000
virtual_uid_maps = static:1001
virtual_transport = virtual
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf

(I use mysql db for virtual users mailbox map)

Hope this helps a little (post back to let me know).

Yassen


On Wednesday 26 January 2005 13:48, Eljee wrote:
 Hi All,
 
 I got a configuration problem. I try to get postfix to work nicely with
 mailman with virtual domains. For some strange reason are the
 mailmanlists under my 'mydomain' of 'myhostnam' working as it should but
 the mailmanlists under my virtual domains are not working. For example
 [EMAIL PROTECTED] will not be processed by mailman but
 just delivered at [EMAIL PROTECTED]
 
 /var/mailman/data/virtual-mailman contains the line:
 [EMAIL PROTECTED]   list-1-subscribe
 
 and
 
 /var/mailman/data/aliases contains the line:
 list-1-subscribe: |/var/mailman/mail/mailman subscribe list-1
 
 the two files are owned by mailman (also the group)
 
 Anyone any idea??
 Regards, LJ
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] moderators' posts rejected

2005-01-24 Thread Yassen Damyanov
Trying to setup an announcement-only list following
Mailman FAQ 3.11, but got stuck:

Seems that I've done everything described there but
moderators' posts are rejected.

Checked several times and cannot find where the
configuration fails (dumped below, my email replaced for
security).

Any help would be greatly appreciated!
Thanks in advance.
Yassen Damyanov



real_name = 'Newsletter'
owner = ['[EMAIL PROTECTED]']
moderator = ['[EMAIL PROTECTED]']
description = ''
info = ''
subject_prefix = '[Newsletter] '
anonymous_list = False
first_strip_reply_to = False
reply_goes_to_list = 0
reply_to_address = ''
umbrella_list = False
umbrella_member_suffix = '-owner'
send_reminders = 1
welcome_msg = ''
send_welcome_msg = True
goodbye_msg = ''
send_goodbye_msg = True
admin_immed_notify = True
admin_notify_mchanges = False
respond_to_post_requests = 1
emergency = 0
new_member_options = 256
administrivia = True
max_message_size = 40
host_name = 'my.domain'
include_rfc2369_headers = 1
include_list_post_header = 1
preferred_language = 'en'
available_languages = ['de', 'en']
encode_ascii_prefixes = 0
nondigestable = True
personalize = 1
msg_header = ''
msg_footer = ___
%(real_name)s Mailingliste
%(real_name)[EMAIL PROTECTED](host_name)s
Um sich von der Liste abzumelden schicken Sie eine eMail an %%(real-name)[EMAIL 
PROTECTED](host_name)s und antworten sie auf die Best?tigungs-eMail.
digestable = 0
digest_is_default = False
mime_is_default_digest = False
digest_size_threshhold = 30
digest_send_periodic = True
digest_header = ''
digest_footer = ___
%(real_name)s mailing list
%(real_name)[EMAIL PROTECTED](host_name)s
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
digest_volume_frequency = 1
advertised = 1
subscribe_policy = 2
unsubscribe_policy = 0
ban_list = []
private_roster = 2
obscure_addresses = 1
default_member_moderation = 1
member_moderation_action = 1
member_moderation_notice = Es tut uns leider aber diese Mailingliste erlaubt 
es den einzelnen eMail-Empf?ngern nicht eine Nachricht an die Mailingliste zu 
schicken.
Ihr media C Team
accept_these_nonmembers = []
hold_these_nonmembers = []
reject_these_nonmembers = []
discard_these_nonmembers = []
generic_nonmember_action = 2
forward_auto_discards = 1
require_explicit_destination = 1
acceptable_aliases = ''
max_num_recipients = 10
header_filter_rules = []
bounce_matching_headers = 
to: friend@public.com
message-id: relay.comanche.denmark.eu
from: [EMAIL PROTECTED]
from: [EMAIL PROTECTED]
bounce_processing = True
bounce_score_threshold = 5.0
bounce_info_stale_after = 7
bounce_you_are_disabled_warnings = 3
bounce_you_are_disabled_warnings_interval = 7
bounce_unrecognized_goes_to_list_owner = True
bounce_notify_owner_on_disable = True
bounce_notify_owner_on_removal = True
archive = True
archive_private = 0
archive_volume_frequency = 1
nntp_host = ''
linked_newsgroup = ''
gateway_to_news = 0
gateway_to_mail = 0
news_moderation = 0
news_prefix_subject_too = 1
autorespond_postings = 0
autoresponse_postings_text = ''
autorespond_admin = 0
autoresponse_admin_text = ''
autorespond_requests = 0
autoresponse_request_text = ''
autoresponse_graceperiod = 90
filter_content = False
filter_mime_types = ''
pass_mime_types = multipart/mixed
multipart/alternative
text/plain
convert_html_to_plaintext = True
filter_action = 0
topics_enabled = 0
topics_bodylines_limit = 5
topics = []



Here's the returned mail:

Return-Path: [EMAIL PROTECTED]
 X-Original-To: [EMAIL PROTECTED]
 Delivered-To: [EMAIL PROTECTED]
 Received: from localhost (localhost.localdomain [127.0.0.1]) 
by mx.my.domain (Postfix) with ESMTP id 9D35063E14 
for [EMAIL PROTECTED]; Mon, 24 Jan 2005 11:35:00 +0100 (CET)
 Received: from mx.my.domain ([127.0.0.1]) 
 by localhost (prodo.my.domain [127.0.0.1]) (amavisd-new, port 10024) 
 with ESMTP id 12597-10 for [EMAIL PROTECTED]; 
 Mon, 24 Jan 2005 11:34:57 +0100 (CET)
 Received: from prodo.my.domain (localhost.localdomain [127.0.0.1]) 
by mx.my.domain (Postfix) with ESMTP id BEE0763E13 
for [EMAIL PROTECTED]; Mon, 24 Jan 2005 11:34:57 +0100 (CET)
 Subject: testting a post from a moderator
 From: [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 MIME-Version: 1.0
 Content-Type: multipart/mixed;
  boundary0548399100==
 Message-ID: [EMAIL PROTECTED]
 Date: Mon, 24 Jan 2005 11:34:56 +0100
 Precedence: bulk
 X-BeenThere: [EMAIL PROTECTED]
 X-Mailman-Version: 2.1.5
 List-Id: newsletter.my.domain
 X-List-Administrivia: yes
 Sender: [EMAIL PROTECTED]
 Errors-To: [EMAIL PROTECTED]
 X-Virus-Scanned: by amavisd-new-20030616:clamav-0.80 at prodo.my.domain
 X-Spam-Status: No, hits=0.4 tagged_above=-99.0 required=4.8 
 tests=NO_REAL_NAME, TW_KZ, TW_RK
 X-Spam-Level: 
 X-UID: 3086
 
You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being

Re: [Mailman-Users] SOLVED: moderators' posts rejected

2005-01-24 Thread Yassen Damyanov
Just solved this myself:

On Monday 24 January 2005 12:57, Yassen Damyanov wrote:
 Trying to setup an announcement-only list following
 Mailman FAQ 3.11, but got stuck:
 
 Seems that I've done everything described there but
 moderators' posts are rejected.

Not really; here's what I have missed:

One final step is needed so that the moderator can post
 to the list without doing tend administrative requests.
 Go to the admin webpage for the list and UNCHECK the
 mod button for the moderator ONLY. All subscribers to
 the list should have the mod button turned ON, except
 for the moderator. This assumes that the moderator is
 also subscribed to the list.

Yassen Damyanov
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] good reading for multiple MM installations?

2005-01-20 Thread Yassen Damyanov
Trying to find a good reading about multiple MM installations
with no success. Anyone to point me to something helpful?

Need this in the context of handling virtual domain mailing
lists with separate list name spaces.

Thanks in advance!
Yassen
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] Identical list names on milti-virtual-domains host

2005-01-14 Thread Yassen Damyanov
On Tuesday 11 January 2005 08:06, you wrote:
 On Jan 10, 2005, at 17:42, Yassen Damyanov wrote:
 
  Unfortunately, it didn't work. No change in the behavior in case of
  identical list names for different domains. Thus I am in a big trouble:
  I was told mailman supports virtual domains so without a second thought
  I migrated tens of domains to a machine running postfix 2.1 / apache2 /
  mailman 2.1.5. Several mailing lists have the same name and differ only
  by domain. Really bad ...
 
 Another alternative is to run multiple instances of Mailman on the 
 machine.  That can have advantages if you need different defaults for 
 different domains, want different list creator passwords, etc.

Jim, thank you for your suggestion. Seem like my last resort...

Unfortunately I stumble in many problems with the second patch
(as already reported in another thread but didn't get response).

For example:

[EMAIL PROTECTED] mailman $ bin/withlist -l [EMAIL PROTECTED]
Loading list [EMAIL PROTECTED] (locked)
Unknown list: [EMAIL PROTECTED]
The variable `m' is the [EMAIL PROTECTED] MailList instance

[EMAIL PROTECTED] mailman $ bin/withlist -l newsletter
Loading list newsletter (locked)
Unknown list: newsletter
The variable `m' is the newsletter MailList instance


Both don't work. The web interface also doesn't work (at least
some pages don't).

Generally, maintaining tens of mailman instances seemed a bad idea,
but that remains my last resort (ohh if I knew earlier for this
limitation..)

Can anybody point me to a good reading about setting up multiple
mailman instances on the same machine?

Thanks in advance!
Yassen
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] true-virtual patch mailfunction: need help

2005-01-12 Thread Yassen Damyanov
After appliying a patch that was essentially what I found at
http://sourceforge.net/tracker/index.php?func=detailaid=943827group_id=103atid=300103

when trying to edit the general preferences of a list at
https://mydomain.com/mailman/admin/mylist/general

I get:
Error: real_name attribute not changed! It must differ from the list's name by 
case only

So the new attributes are not saved. When I change the real name of the lits
from 'test' to 'test-mudomain.com' the page data is saved but the whole thing
breaks afterwards.

Can anyone suggest a fix to this or a workaround?
Thanks in advance!

Yassen



The differences of the code I run against 2.1.5 original code:

--- ./bin/newlist.ORIG  2005-01-11 18:20:23.0 +0100
+++ ./bin/newlist   2005-01-12 20:41:20.0 +0100
@@ -126,7 +126,7 @@
 host_name = None
 web_page_url = None
 if '@' in listname:
-listname, domain = listname.split('@', 1)
+firstname, domain = listname.split('@', 1)
 host_name = mm_cfg.VIRTUAL_HOSTS.get(domain, domain)
 web_page_url = mm_cfg.DEFAULT_URL_PATTERN % domain

--- ./Mailman/MailList.py.ORIG  2005-01-11 18:25:09.0 +0100
+++ ./Mailman/MailList.py   2005-01-12 20:43:38.0 +0100
@@ -183,9 +183,16 @@
 return self._full_path

 def getListAddress(self, extra=None):
-if extra is None:
-return '[EMAIL PROTECTED]' % (self.internal_name(), self.host_name)
-return '[EMAIL PROTECTED]' % (self.internal_name(), extra, 
self.host_name)
+ posting_addr = self.internal_name()
+ try:
+ posting_addr = self.real_name
+ except:
+ pass
+ if extra is None:
+ #   return '[EMAIL PROTECTED]' % (self.internal_name(), 
self.host_name)
+ #return '[EMAIL PROTECTED]' % (self.internal_name(), extra, 
self.host_name)
+ return '[EMAIL PROTECTED]' % (posting_addr, self.host_name)
+ return '[EMAIL PROTECTED]' % (posting_addr, extra, self.host_name)

 # For backwards compatibility
 def GetBouncesEmail(self):
@@ -434,8 +441,6 @@
 #
 def Create(self, name, admin, crypted_password,
langs=None, emailhost=None):
-if Utils.list_exists(name):
-raise Errors.MMListAlreadyExistsError, name
 # Validate what will be the list's posting address.  If that's
 # invalid, we don't want to create the mailing list.  The hostname
 # part doesn't really matter, since that better already be valid.
 # the admin's email address, so transform the exception.
 if emailhost is None:
 emailhost = mm_cfg.DEFAULT_EMAIL_HOST
-postingaddr = '[EMAIL PROTECTED]' % (name, emailhost)
+firstname = name
+domain = mm_cfg.DEFAULT_EMAIL_HOST
+   # we set a special name for virtual hosted lists
+if '@' in name:
+   firstname, domain = name.split('@', 1)
+name = %s-%s % (firstname, domain)
+   # but we keep a sensible posting address
+postingaddr = '[EMAIL PROTECTED]' % (firstname, domain)
 try:
 Utils.ValidateEmail(postingaddr)
 except Errors.MMBadEmailError:
 raise Errors.BadListNameError, postingaddr
 # Validate the admin's email address
 Utils.ValidateEmail(admin)
+if Utils.list_exists(name):
+raise Errors.MMListAlreadyExistsError, name
 self._internal_name = name
 self._full_path = Site.get_listpath(name, create=1)
 # Don't use Lock() since that tries to load the non-existant config.pck
 self.__lock.lock()
 self.InitVars(name, admin, crypted_password)
+   # this is for getListAddress
+self.list_address = postingaddr
+self.real_name = firstname
+self.subject_prefix = mm_cfg.DEFAULT_SUBJECT_PREFIX % self.__dict__
 self.CheckValues()
 if langs is None:
 self.available_languages = [self.preferred_language]
@@ -1279,7 +1297,7 @@
 to or cc addrs.
 # BAW: fall back to Utils.ParseAddr if the first test fails.
 # this is the list's full address
-listfullname = '[EMAIL PROTECTED]' % (self.internal_name(), 
self.host_name)
+listfullname = self.getListAddress()
 recips = []
 # check all recipient addresses against the list's explicit addresses,
 # specifically To: Cc: and Resent-to:


--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] Configuration question

2005-01-11 Thread Yassen Damyanov
On Monday 10 January 2005 22:32, [EMAIL PROTECTED] wrote:
 What do I set to insure that it is a closed list?  That is, the list can
 only be sent to by administrators and not reply to all on the list.

Take a look here:

http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.htp

Seems that this is what you need.
Yassen
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] Identical list names on milti-virtual-domains host

2005-01-11 Thread Yassen Damyanov
On Monday 10 January 2005 18:48, Mark Sapiro wrote:
 
 There is a similar patch (mentioned in FAQ article 4.47) at
 http://sourceforge.net/tracker/index.php?func=detailaid=943827group_id=103atid=300103
 
 You might look at this too in case you haven't already. It also patches
 bin/newlist which cPanel may not use.

Exactly. Thank you Mark for your patient reminder to try this patch as well.
I did and it seems to WORK!! I think so and I DO HOPE so, as this will be
a real relief in a difficult situation.

I noticed some mailfunctions but I think that all I could see so far are
acceptable and we can live with them. Examples:

-- command line tools like list_lists ot list_members do not recognize
   identically named lists (but newlist and rmlist seem to work fine)
-- I can go directly to list member profile page without being asked
   for authentication
-- I could even enter arbitrary email with non-existent domain to request
   an unsubscribe action and the system told me that a confirmation of
   unsubscribal has been sent to the user

I look forward for a mailman version that has this all fixed and working
fine...

Thanks again to everybody who was willing to help!

(If anyone's interested, I can post the patch as it is against 2.1.5.)
Yassen
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] Identical list names on milti-virtual-domains host

2005-01-10 Thread Yassen Damyanov
On Friday 07 January 2005 19:48, Todd wrote:
 
 I submitted some questions to
 the folks at cPanel asking for the modifications and it took a long
 while before I finally got a link where the changes were posted:
 
 http://koston.org/mailman-patches/
 
 I don't know how current the patch there is, it says it's for 2.1.3,
 though I know from working with some people that have cPanel installed
 on their servers that cPanel has mailman 2.1.5 included at this point.

Thanks a lot, Todd!

I tried that patch against 2.1.5. It was relatively easy to apply -- all
lines a subject to change are exactly the same as in 2.1.3 (which does not
mean that the patch is correct against 2.1.5).

Unfortunately, it didn't work. No change in the behavior in case of
identical list names for different domains. Thus I am in a big trouble:
I was told mailman supports virtual domains so without a second thought
I migrated tens of domains to a machine running postfix 2.1 / apache2 /
mailman 2.1.5. Several mailing lists have the same name and differ only
by domain. Really bad ...

(BTW, this patch seems not very serious: there are about 5 lines or so
changed, excluding the crontab files and  the configuration changes.)

If anyone has any futher idea on this subject -- it will be very much
appreciated.

Yassen

--

Yassen Damyanov
Troyer Information Systems

email: [EMAIL PROTECTED]
ICQ# : 169382108
web  : www.troyer-is.com
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] Identical list names on milti-virtual-domains host

2005-01-07 Thread Yassen Damyanov
Hi, list!

A multi-virtual-domain host running mailman/postfix/apache2.

The bin/newlist script tells me that I can specify the web host
that is associated with the list:

You can specify the domain to create your new list in by spelling
the listname like so:
[EMAIL PROTECTED]

So far so good... but doing so does not seem to let mailman distinguish
between [EMAIL PROTECTED] and [EMAIL PROTECTED] ...

Is there a way to have two lists with idential names and different
domains?

Your help would be greatly appreciated!
Yassen

--

Yassen Damyanov
Troyer Information Systems

email: [EMAIL PROTECTED]
ICQ# : 169382108
web  : www.troyer-is.com
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] Identical list names on milti-virtual-domains host

2005-01-07 Thread Yassen Damyanov
On Friday 07 January 2005 16:56, you wrote:

Mark, thanks so much!

From the Mailman FAQ Section 4.47:

The modified version of Mailman, shipped by Cpanel as part of their 
commercial hosting product for ISPs, adopts a different, 
list-name-munging solution to the problem but Cpanel have not made the
modified source code generally available in the public domain.

Isn't this a violation of the GPL-2 or do I miss something?

Yassen

 Yassen Damyanov wrote:
 
 Is there a way to have two lists with idential names and different
 domains?
 
 See
 Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
 article 4.47.
 
 Note that the FAQ article refers to a patch on sourceforge that may
 help.
 
 --
 Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


[Mailman-Users] How to set up a READ-ONLY list?

2004-12-15 Thread Yassen Damyanov
Hi all,

I need to urgently setup a Mailman read-only mailing list.
It appears to be not-so-obvious a task (my first contact
with Mailman).

Could anyone send me directions and/or documents to read?

Thanks in advance!

Yassen

P.S. This is an example of how the
   [EMAIL PROTECTED]
list reacts to posts of subscribed users. I need exactly this
behavior:

 This is an announcement-only mailing list. Only the Mailman
 developers are allowed to post announcements to this list. Your
 message has been automatically rejected by the Mailman system.
 
 If you think this rejection is in error, or if you have a legitimate
 announcement that you think the Mailman community would be interested
 in, please contact the list admins at
 [EMAIL PROTECTED]
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] SOLVED: How to set up a READ-ONLY list?

2004-12-15 Thread Yassen Damyanov
On Thursday 16 December 2004 01:27, you wrote:
 Sorry Yassen
 
 You need help more than I.  What platform are you on?
 
 -evan


Dan: thanks for the link with that really nice guide!

 See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.htp


Evan: thanks for caring!

I just followed that guide and I have it all up and running --
my read-only, one-way mailing list!

 What platform are you on?

Gentoo Linux box, postfix 2.1 + amavisd-new + SpamAssassin + Mailman 2.5.1.

I am sorry that I cannot be of much use regarding the issues you
sent in your direct mail to me. I quote them here for attracting
attention of people who can help, although it seems more appropriate
to open a new thread (which I recommend to you).

I _do wish you_ to get that all running fine.

Yassen


--  Original Message  --

Subject: Re: Have you got postfix and mailman work together?
Date: Thursday 16 December 2004 01:11
From: DJ Freak [EMAIL PROTECTED]
To: Yassen Damyanov [EMAIL PROTECTED]

Hi Yassen

Thank you very much for  asking.

Yes I have gotten Postfix and Mailman working together.

However, I have two very stubborn problems which I'm still trying to 
work out.

1.  I am unable to edit the HTML page that users are taken to when they 
hit the confirm link in their confirmation email.  It's NOT 
subscribe.html and I cannot find a file called confirm.html anywhere.  
There must be a script somewhere compiling the HTML but I cannot find 
it.

2.  Confirmation and invitation mails are getting junked by my 
recipients becuase confirm djafdjkdas;jfdkljdfsakl;7847474477 is 
considered junk by many email programs so I have

Begin paste here-
 Here's what I have done:

 1.  Added

 VERP_CONFIRMATIONS = Yes

 to Defaults.py

 2.  Added

 VERP_CONFIRMATIONS = Yes

 to mm_cfg.py

 3.  Added

 default_verp_delimiters = +=
 verp_delimiter_filter = -+=
 authorized_verp_clients = $mynetworks

 to /etc/postfix/main.cf


 Anything scream wrong there?  Am I forgetting a step?  Restarted
 mailman and Postfix but still confirmations and invites come in with
 all that junk in the replies.
-End Paste

Any thoughts on those two issues?

Thanks a lot Yassen I really appreciate it.

-Evan

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/