Mailman stop working...help!
Hi,
I was using mailman with postfix, then reading nice things about vpostmaster, i decided set it up to manage my user mail accounts. After setup, my mailman stopped delivering mails. Its returns with the error message below:
Delivery to the following recipient failed permanently:
I have overhauled and reinstall from scratch(a very painful one as i lost my achieve) even after re-installing i still could not get my mailman to work again. How can i get this fixed please.
Regards PS: I tried the proceeds in the url below with no luck: http://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-... http://en.gentoo-wiki.com/wiki/Mailman_with_Postfix_and_Dovecot
*Seun Ojedeji, Federal University Oye Ekiti web: http://www.fuoye.edu.ng Mobile: +2348035233535 **alt email: seun.ojedeji@fuoye.edu.ng** <http://idlelo.net/node/18>*
Seun Ojedeji wrote:
So you replaced your Postfix MTA with some other MTA and you didn't teach the new MTA how to deliver to Mailman.
Fixing this is a question for vPostMaster. It is not a Mailman issue per se, and various HowTo documents relating to configuring Mailman with Postfix are not going to help as long as you are using vPostMaster as your incoming MTA.
Whatever MTA is listening on port 25 of your Mailman server has to be configured to deliver list mail to Mailman. I'd be surprised if anyone on this list is using vPostMaster as an MTA, thus it is unlikely you can get help here.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Apr 22, 2012, at 7:31 PM, Mark Sapiro wrote:
It looks like vPostMaster is actually a package with management front end for installing/configuring Postfix and other stuff like ClamAV and SpamAssassin. Since he apparently had a working Postfix configuration, I suspect vPostMaster clobbered the configuration with something that knows nothing about Postfix.
-- Larry Stone lstone19@stonejongleux.com http://www.stonejongleux.com/
hi,
I've ben admistering mailman for several years now. But ran into an odd issue today. I had a customer come to me and they have a mailing list blah@blah.com
when they have people use blah-subscribe@blah.com the people are getting access denied errors i've checked all the settings am i over looking something?
"mike" wrote:
What is your MTA? How does it deliver to Mailman? Does it use aliases and if so, do you have all 9 of the blah-*@blah.com aliases as well as the blah@blah.com one?
What exactly do you mean by an "access denied" error? Do you mean they mail to blah-subscribe@blah.com, get a confirmation message and then get an http 401 when attempting to visit the URL in the confirmation message? If so, is this different than from a subscribe attempt from the form on the listinfo page.
Does this work for other lists?
Can they visit other list web pages like the listinfo, admin and admindb pages and if so, is the domain in the URLs they use for those pages the same as in the confirmation URL?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, 22 Apr 2012, Seun Ojedeji wrote:
That's not a mailman issue.
Did some research, and RFC 1893 notes this about this type of error (the clue is the 5.7.1 error):
X.7.1 Delivery not authorized, message refused
The sender is not authorized to send to the destination.
This can be the result of per-host or per-recipient
filtering. This memo does not discuss the merits of any
such filtering, but provides a mechanism to report such.
This is useful only as a permanent error.In short, it isn't Mailman, it's the MTA. Focus there.
-Dennis
Seun Ojedeji wrote:
So you replaced your Postfix MTA with some other MTA and you didn't teach the new MTA how to deliver to Mailman.
Fixing this is a question for vPostMaster. It is not a Mailman issue per se, and various HowTo documents relating to configuring Mailman with Postfix are not going to help as long as you are using vPostMaster as your incoming MTA.
Whatever MTA is listening on port 25 of your Mailman server has to be configured to deliver list mail to Mailman. I'd be surprised if anyone on this list is using vPostMaster as an MTA, thus it is unlikely you can get help here.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Apr 22, 2012, at 7:31 PM, Mark Sapiro wrote:
It looks like vPostMaster is actually a package with management front end for installing/configuring Postfix and other stuff like ClamAV and SpamAssassin. Since he apparently had a working Postfix configuration, I suspect vPostMaster clobbered the configuration with something that knows nothing about Postfix.
-- Larry Stone lstone19@stonejongleux.com http://www.stonejongleux.com/
hi,
I've ben admistering mailman for several years now. But ran into an odd issue today. I had a customer come to me and they have a mailing list blah@blah.com
when they have people use blah-subscribe@blah.com the people are getting access denied errors i've checked all the settings am i over looking something?
"mike" wrote:
What is your MTA? How does it deliver to Mailman? Does it use aliases and if so, do you have all 9 of the blah-*@blah.com aliases as well as the blah@blah.com one?
What exactly do you mean by an "access denied" error? Do you mean they mail to blah-subscribe@blah.com, get a confirmation message and then get an http 401 when attempting to visit the URL in the confirmation message? If so, is this different than from a subscribe attempt from the form on the listinfo page.
Does this work for other lists?
Can they visit other list web pages like the listinfo, admin and admindb pages and if so, is the domain in the URLs they use for those pages the same as in the confirmation URL?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Sun, 22 Apr 2012, Seun Ojedeji wrote:
That's not a mailman issue.
Did some research, and RFC 1893 notes this about this type of error (the clue is the 5.7.1 error):
X.7.1 Delivery not authorized, message refused
The sender is not authorized to send to the destination.
This can be the result of per-host or per-recipient
filtering. This memo does not discuss the merits of any
such filtering, but provides a mechanism to report such.
This is useful only as a permanent error.In short, it isn't Mailman, it's the MTA. Focus there.
-Dennis
participants (5)
-
Dennis Carr -
Larry Stone -
Mark Sapiro -
mike -
Seun Ojedeji