I also face such type of issues with my mailing list very often these days.
Then what I do is, I ask my mail service provider to refresh everything on
the server, they do this and it starts working. But is there any permanent
solution for this?
Can we hope to not have such problems in upcoming version mailman 3.0 in the
future? When this updated version is finally going to be launched?
Regards,
Amit Bhatt
----- Original Message -----
From: "Mark Sapiro" <m...@msapiro.net>
To: "Seun Ojedeji" <seun.ojed...@gmail.com>
Cc: <mailman-users@python.org>
Sent: Friday, April 27, 2012 3:05 AM
Subject: Re: [Mailman-Users] {Disarmed} Re: Mailman stop
working...help!(Progress?)
Seun Ojedeji wrote:
>Hi,
>Perhaps i should provide my details maybe i could get help here....i
really
>wish to keek the vpostmaster frontend(because of the ease of
>account//domain creation) and still needs my mailman. below is the url
>to
>my /etc/mailman/mm_cfg.py and /etc/postfix/main.cf . Kindly help!
>
>http://pastebin.ca/2139462
If I understand correctly what the situation is, your list mail is
being rejected by the incoming MTA at SMTP time and never being
delivered to Mailman. Thus, your mm_cfg.py is not relevant at this
point.
Yes exactly that is the problem and thank you for telling me tht
mm_cfy.py
is not the issue
Also, the output of 'postconf -n' is generally much easier for those
who would help you than is the entire main.cf.
Here is the output below:
admin@mydomain:~$ postconf -n
alias_database = hash:/var/lib/mailman/data/aliases
alias_maps = hash:/var/lib/mailman/data/aliases
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
html_directory = /usr/share/doc/postfix/html
inet_interfaces = all
mail_name = mydomain MAIL SERVER
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
mydestination = lists.mydomain.net, localhost, localhost.localdomain
myhostname = mail.mydomain.net
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
relayhost =
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_recipient_restrictions = permit_mynetworks
permit_sasl_authenticate d
permit_auth_destination check_policy_service unix:private/vpm-pfpolicy
r eject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_use_tls = yes
virtual_alias_maps = hash:/var/lib/mailman/data/virtual-mailman
virtual_mailbox_domains = pgsql:/etc/postfix/vpm-domains
virtual_transport = vpm-pftransport
That said, there is nothing much in main.cf that would indicate a
problem except that the vPostMaster stuff beginning at line 48 in the
pastebin is probably the issue, but exactly what the issue is can't be
determined without knowing what's in /etc/postfix/vpm-domains and
probably what's in master.cf for the vpm-pftransport.
Here is output of /etc/postfix/vpm-domains
user=postfix
password=fd483c8dc339ea19188aa69e8ae668a3
hosts=127.0.0.1
dbname=vpostmaster
table=domains
select_field='X'
where_field=name
additional_conditions = and active = 't'
There's probably an entry in the 'domains' table for the lists....
domain which needs to be removed.
Here is the master.cf.vpostmaster : http://pastebin.ca/2140584 However i
think its using the default master.cf as it wrote some vpostmaster stuffs
there. Here is the master.cf http://pastebin.ca/2140584
Those are the same URL. I note however tahe there is a mailman
transport defined using postfix_to_mailman.py. Is this how you were
delivering to Mailman. Is ther (or was there before) an entry in
transport maps (possibly /etc/postfix/transport) mapping the lists...
domain to the mailman transport? Your current postconf -n shows no
entry for transport_maps
If in fact, you want to use postfix_to_mailman.py, adding
transport_maps = hash:/path/to/transport
making sure that transport contains an entry like
lists.mydomain.net mailman:
and running
postmap /path/to/transport
may solve your porblem.
Based on your prior post, I would guess that mail to the
"lists.mydomain.net" domain is being routed to vPostMaster and
vPostMaster doesn't know how to deliver to Mailman.
Exactly! how do i get to route to the right domain??
Ask the right question on the vPostMaster list.
The response you got from a vpostermaster list said:
> You'll have to make sure that the domain that is used for the list
> e-mail
> is not managed by vPostMaster; without the vPostMaster integration, I
> don't know of a way to get Postfix to deliver both to regular accounts
> and lists in the same domain.
That says that your lists should be in the "lists.mydomain.net" domain
and only list mail should be addressed to that domain, i.e. no local
user addresses in that domain, and that domain should not be managed
by vPostMaster, i.e. it should not be in /etc/postfix/vpm-domains.
Yes the domain is not there at all, but and that is why in the error i
get
no such domain message
I can't help with any vPostMaster specific configuration.
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
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/misterbhatt%40gmail.com
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
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
