A list is rejected by email server after migration
![](https://secure.gravatar.com/avatar/5f036530e215ad8fe28271583a16c3fc.jpg?s=120&d=mm&r=g)
After an upgrade last night all our lists can send email except one. It is rejected by the smtp server it says that address does not exist. The mailman page for the list exists, the mbox file exists Any thoughts on what went wrong and how to fix it? (just happens to be the iss-directors list)
-- Thank you, Frank Bell Application Systems Admin ISS 785-670-2334
1 Cor 15:10 "By the grace of God I am what I am, and His grace toward me was not in vain . . .."
![](https://secure.gravatar.com/avatar/334b870d5b26878a79b2dc4cfcc500bc.jpg?s=120&d=mm&r=g)
Frank Bell writes:
While this is probably not the best place to get help for this problem -- it's almost surely *not* a *Mailman* problem -- we will give it a try. But we need to know what exactly was upgraded and migrated, from where to where? Especially, which MTA(s) is (are) used at your site by hosts involved in list post distribution. And what address is being rejected by what server. (Feel free to post the entire rejection message. That's best. If necessary you can redact information that needs to be private, but that may make diagnosis inaccurate.)
Specifically, if the SMTP server says the address doesn't exist, the problem is in the MTA configuration. The first thing to do is to check for a typo in the aliases for the MTA. The second is that some MTAs (Exim, for one) support "automatic" aliases based on certain conditions that can include the presence of config files and the like. Perhaps a prerequisite for auto-aliasing is missing for that list. There are other possibilities but those are the first ones off the top of my head.
![](https://secure.gravatar.com/avatar/5f036530e215ad8fe28271583a16c3fc.jpg?s=120&d=mm&r=g)
All, within the last ten minutes my linux sysadmin discovered that the mailman-aliases file at /etc/mail did not for some reason contain one or two entries. (yes after migration I ran genaliases )
Solution was: He brought the old mailman-aliases from the old server, copied the missing entries into the new mailman-aliasesand then ran newaliases
Thanks for the response!!
Thank you, Frank Bell Application Systems Admin ISS 785-670-2334
1 Cor 15:10 "By the grace of God I am what I am, and His grace toward me was not in vain . . .."
On 2/29/2012 11:13 AM, Stephen J. Turnbull wrote:
![](https://secure.gravatar.com/avatar/0d67da306b00861e781dbdafd331dfea.jpg?s=120&d=mm&r=g)
On 2/29/2012 11:21 AM, Frank Bell wrote:
If you ran genaliases, and the alias file in use was incomplete, then I assume that genaliases is updating an alias file that is different than the alias file that your MTA is using.
--Barry Finkel
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
Frank Bell wrote:
What is your MTA? How does it know about lists? Does it use aliases? Are aliases installed for the failing list? Does mail to the list get delivered? What is the exact error message from the SMTP server?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/334b870d5b26878a79b2dc4cfcc500bc.jpg?s=120&d=mm&r=g)
Frank Bell writes:
While this is probably not the best place to get help for this problem -- it's almost surely *not* a *Mailman* problem -- we will give it a try. But we need to know what exactly was upgraded and migrated, from where to where? Especially, which MTA(s) is (are) used at your site by hosts involved in list post distribution. And what address is being rejected by what server. (Feel free to post the entire rejection message. That's best. If necessary you can redact information that needs to be private, but that may make diagnosis inaccurate.)
Specifically, if the SMTP server says the address doesn't exist, the problem is in the MTA configuration. The first thing to do is to check for a typo in the aliases for the MTA. The second is that some MTAs (Exim, for one) support "automatic" aliases based on certain conditions that can include the presence of config files and the like. Perhaps a prerequisite for auto-aliasing is missing for that list. There are other possibilities but those are the first ones off the top of my head.
![](https://secure.gravatar.com/avatar/5f036530e215ad8fe28271583a16c3fc.jpg?s=120&d=mm&r=g)
All, within the last ten minutes my linux sysadmin discovered that the mailman-aliases file at /etc/mail did not for some reason contain one or two entries. (yes after migration I ran genaliases )
Solution was: He brought the old mailman-aliases from the old server, copied the missing entries into the new mailman-aliasesand then ran newaliases
Thanks for the response!!
Thank you, Frank Bell Application Systems Admin ISS 785-670-2334
1 Cor 15:10 "By the grace of God I am what I am, and His grace toward me was not in vain . . .."
On 2/29/2012 11:13 AM, Stephen J. Turnbull wrote:
![](https://secure.gravatar.com/avatar/0d67da306b00861e781dbdafd331dfea.jpg?s=120&d=mm&r=g)
On 2/29/2012 11:21 AM, Frank Bell wrote:
If you ran genaliases, and the alias file in use was incomplete, then I assume that genaliases is updating an alias file that is different than the alias file that your MTA is using.
--Barry Finkel
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
Frank Bell wrote:
What is your MTA? How does it know about lists? Does it use aliases? Are aliases installed for the failing list? Does mail to the list get delivered? What is the exact error message from the SMTP server?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (4)
-
Barry S, Finkel
-
Frank Bell
-
Mark Sapiro
-
Stephen J. Turnbull