Hi, Mark,
Maybe i am wrong but I think something is not correct and I am still confused.

Let roll back to the beginning stage before Mailman installed. My mail server using mysql as backend to handle virtual domain. Let say I have domain1 and domain2 exist. I also have user table in MySQL. For example: [email protected], [email protected]... (for now let's just focus on domain1.)

So far my mail server handles mail correctly. I sent an email to [email protected], postfix use "relay=virtual": /Aug 9 13:47:33 mail postfix/virtual[2501]: B34C642F01CA: to=<[email protected]>, relay=virtual, delay=1.5, delays=1.3/0.06/0/0.06, dsn=2.0.0, status=sent (delivered to maildir)/

Then, as you recommended, I add domain1.com as mydestination on main.cf, reload Postfix:
/[r...@mail postfix]# postconf -n | grep mydestination
mydestination = mail.domain1.com, domain1.com, localhost, localhost.localdomain/

Then I test by sending email to the same [email protected], maillog shows:
/Aug 9 13:55:21 mail postfix/local[2751]: 1953942F01CE: to=<[email protected]>, relay=local, delay=2.2, delays=2.1/0.03/0/0.03, dsn=5.1.1, status=bounced (unknown user: "tester")/

What I see now is Postfix no longer looking for virtual domain. In stead, it try to deliver the mail use /"relay=local"/. Since I don't have a real tester user account on the server, so Postfix failed to deliver.

All above has nothing to do with Mailman. I was configuring and testing Mailman then suddenly I realized my email server is broken. So I restored the system (I have a clonezilla image backup) and did the above test.

Is this means that I should not put "domain1.com" in "mydestination="?

Jian


 10-08-09 12:53 PM, Mark Sapiro wrote:
Jian Gao wrote:
Here are some of information:

There is a non-critical issue.


-------------------------------------------------------------------------------------------------------------------------------------------
[r...@mail in]# postconf -n
[...]
mydestination = mail.mydomain.com, mydomain.com, localhost,
localhost.localdomain

Your list domain 'mydomain.com' is now local per the above.


[...]
-------------------------------------------------------------------------------------------------------------------
/etc/mailman/mm_cfg.py

#from socket import *
#try:
#    fqdn = getfqdn()
#except:
#    fqdn = 'mm_cfg_has_unknown_host_domains'

DEFAULT_URL_HOST   = 'mail.mydomain.com'
DEFAULT_EMAIL_HOST = 'mydomain.com'

# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)


##############################################################
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values.            #

# Note - if you're looking for something that is imported from mm_cfg,
but you
# didn't find it above, it's probably in Defaults.py.

MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mydomain.com']

Thus, the above is unnecessary. It causes Mailman to create
virtual-mailman which isn't referenced in your Postfix config anyway.
The fact that you added 'mydomain.com' to mydestination in Postfix
makes it a local domain to Postfix.


------------------------------------------------------------------------------------------------------
[r...@mail mailman]# ll
total 52
-rw-r----- 1 root mailman    41 Aug  6 10:23 adm.pw
-rw-rw---- 1 root mailman  1132 Aug  6 12:55 aliases
-rw-r----- 1 root mailman 12288 Aug  6 12:55 aliases.db
lrwxrwxrwx 1 root mailman    34 Aug  6 10:12 mm_cfg.py ->
/usr/lib/mailman/Mailman/mm_cfg.py
-rw-r--r-- 1 root mailman 14114 May 24  2008 sitelist.cfg
-rw-rw---- 1 root mailman  1155 Aug  6 12:55 virtual-mailman
-rw-r----- 1 root mailman 12288 Aug  6 12:55 virtual-mailman.db

The virtual-mailman* files aren't needed or used.


[r...@mail mailman]# cat aliases
[...]
[r...@mail mailman]# cat virtual-mailman
# This file is generated by Mailman, and is kept in sync with the binary
hash
# file virtual-mailman.db.  YOU SHOULD NOT MANUALLY EDIT THIS FILE
unless you
# know what you're doing, and can keep the two files properly in sync.
If you
# screw it up, you're on your own.
#
# Note that you should already have this virtual domain set up properly in
# your Postfix installation.  See README.POSTFIX for details.

# LOOP ADDRESSES START
[email protected]    mailman-loop
# LOOP ADDRESSES END

# STANZA START: mailman
# CREATED: Fri Aug  6 12:55:44 2010
[email protected]              mail...@localhost
[email protected]        mailman-ad...@localhost
[email protected]      mailman-boun...@localhost
[email protected]      mailman-conf...@localhost
[email protected]         mailman-j...@localhost
[email protected]        mailman-le...@localhost
[email protected]        mailman-ow...@localhost
[email protected]      mailman-requ...@localhost
[email protected]    mailman-subscr...@localhost
[email protected]  mailman-unsubscr...@localhost
# STANZA END: mailman


The above is intended to be used in virtual_alias_maps in Postfix if
mydomain.com is a virtual_alias_domain, but it is not. It is a local
domain in Postfix so this isn't needed

Remove

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mydomain.com']

from mm_cfg.py and remove the data/virtual-mailman* files as none of
that is needed/used by Postfix.


--
Jian Gao
IT Administrator
SJ Geophysics Ltd. <http://www.sjgeophysics.com>
[email protected] <mailto:[email protected]>
Tel: (604)582-1100
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to