550 Recipient Address Rejected Error
After creating a new list with a (clearly not properly setup) new install of mailman, when sending a message to the list address I get the following error back:
This is an automatically generated Delivery Status Notification
Delivery to the following recipient failed permanently:
testlist@mydomain.comTechnical details of permanent failure: PERM_FAILURE: SMTP Error (state 9): 550 <testlist@mydomain.com>: Recipient address rejected: User unknown in local recipient table
I pulled my actual domain out of this error. Oddly enough all messages regarding subscribing etc work just fine. Users simply cannot post messages. Any ideas? Thanks.
Phelps Williams wrote:
Delivery to the following recipient failed permanently:
testlist@mydomain.comTechnical details of permanent failure: PERM_FAILURE: SMTP Error (state 9): 550 <testlist@mydomain.com>: Recipient address rejected: User unknown in local recipient table
I pulled my actual domain out of this error. Oddly enough all messages regarding subscribing etc work just fine. Users simply cannot post messages. Any ideas? Thanks.
I don't know if this is it or not, but have you checked your aliases or whatever this MTA uses to deliver to Mailman. From your description, it seems as though maybe mail to the testlist-subscribe and testlist-owner works or maybe not depending on what you mean by "all messages regarding subscribing etc work just fine", but mail to testlist doesn't.
See section 2) in <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.014.htp>.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I continued to play with this and I came across the postfix-to-mailman script. The description of what this script provides fits my application perfectly, serving as a postfix to mailman transport pipe. Within the script is a description of how to set it up, I followed this and after restarting the runtimes involved I get the following error in /var/log/mail.log right after I send the mailing list a message:
Mar 29 21:45:32 localhost postfix/trivial-rewrite[4633]: fatal: open database /etc/postfix/transport.db: No such file or directory Mar 29 21:45:33 localhost postfix/master[4613]: warning: process /usr/lib/postfix/trivial-rewrite pid 4633 exit status 1 Mar 29 21:45:33 localhost postfix/master[4613]: warning: /usr/lib/postfix/trivial-rewrite: bad command startup -- throttling
I believe it has to do with the configuration guidelines in postfix-to-mailman which specify:
# /etc/postfix/main.cf: # relay_domains = ... lists.example.com # transport_maps = hash:/etc/postfix/transport # mailman_destination_recipient_limit = 1 # # /etc/postfix/transport: # lists.example.com mailman:
I created the /etc/postfix/transport file just for this purpose, as in it was not in existence before. As you might expect there is not a /etc/postfix/transport.db file. Is this generated a certain way. Anybody see what I am missing? Thanks.
-Phelps
On 3/29/06, Mark Sapiro <msapiro@value.net> wrote:
Phelps Williams wrote:
Delivery to the following recipient failed permanently:
testlist@mydomain.comTechnical details of permanent failure: PERM_FAILURE: SMTP Error (state 9): 550 <testlist@mydomain.com>:
Recipient
address rejected: User unknown in local recipient table
I pulled my actual domain out of this error. Oddly enough all messages regarding subscribing etc work just fine. Users simply cannot post messages. Any ideas? Thanks.
I don't know if this is it or not, but have you checked your aliases or whatever this MTA uses to deliver to Mailman. From your description, it seems as though maybe mail to the testlist-subscribe and testlist-owner works or maybe not depending on what you mean by "all messages regarding subscribing etc work just fine", but mail to testlist doesn't.
See section 2) in <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.014.htp>.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Phelps Williams wrote:
I created the /etc/postfix/transport file just for this purpose, as in it was not in existence before. As you might expect there is not a /etc/postfix/transport.db file. Is this generated a certain way.
You need to do the postfix command
postmap /etc/postfix/transport
in order to generate the /etc/postfix/transport.db file.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Phelps Williams