Thatīs what I thought....
I had the same problem.
In my case, after the migration, the mail files for certain users were
filled with garbage; for example, I had a similar error, and what I did was
to go to the user that appeared in the "(expanded from: <xxxx (at mark) xxx.com>)",
and saw that the .forward file had this garbage:
"|/usr/local/majordomo/wrapper resend -l atritest -r XXX (at mark) XXX.XXX.org -C
/usr/local/majordomo/sites/siteXXX/majordomo.cf 3207-atritest-list, nobody".
I just delete the contents of the .forward, and the problem was solved.
Try it and let me know if it fixed the problem.
Good luck!
-----Original Message-----
From: Ken Marcus - Precision Web Hosting, Inc.
[mailto:kenmarcus (at mark) precisionweb.net]
Sent: Wednesday, March 29, 2006 9:14 PM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:04417] Re: majordomo problem solved
>> I seem to be getting the error below when I try to send to a mailing
>> list on a BQ server.
>> I changed out something.org in place of the actual domain.
>> Anyone have a quick fix?
>>
>>
>> ----- The following addresses had permanent fatal errors -----
>> "|/usr/local/majordomo/wrapper resend -l atritest -r
>> test (at mark) www.something.org -C
>> /usr/local/majordomo/sites/site100/majordomo.cf
>> 3207-atritest-list, nobody"
>> (reason: Service unavailable)
>> (expanded from: <test (at mark) something.org>)
>>
>> ----- Transcript of session follows ----- Message delivered to
>> mailing list <test (at mark) something.org>
>> smrsh: "wrapper" not available for sendmail programs (stat failed)
>> 554 5.0.0 Service unavailable
>>
>>
>
>
> I went to the /usr/local/majordomo and most of the files were missing.
>
> Then I did a
> yum install majordomo.i386
>
> And all the files are there now:
> -rwxr-x--- 1 mail daemon 5234 Mar 4 2005 archive2.pl
> drwxr-x--- 2 mail daemon 4096 Jan 7 10:07 bin
> -rwxr-x--- 1 mail daemon 2795 Mar 4 2005 bounce-remind
> -rwxr-x--- 1 mail daemon 49882 Mar 4 2005 config_parse.pl
> -rwxr-x--- 1 mail daemon 10671 Mar 4 2005 config-test
> -rwxr-x--- 1 mail daemon 13031 Mar 4 2005 digest
> drwxr-s--- 2 mail daemon 4096 Mar 4 2005 digests
> drwxr-s--- 2 mail daemon 4096 Mar 4 2005 files
> drwx------ 2 mail daemon 4096 Mar 4 2005 lists
> -rw-rw---- 1 mail daemon 0 Mar 4 2005 log
> -rw-r----- 1 mail daemon 21734 Mar 29 03:37 logs
> -rwxr-x--- 1 mail daemon 64259 Mar 4 2005 majordomo
> -rw-r----- 1 mail daemon 10945 Mar 4 2005 majordomo.cf
> -rw-r----- 1 mail daemon 9700 Mar 4 2005 majordomo.cf.template
> -rwxr-x--- 1 mail daemon 23763 Mar 4 2005 majordomo.pl
> -rwxr-x--- 1 mail daemon 137 Mar 4 2005 majordomo_version.pl
> -rwxr-x--- 1 mail daemon 3532 Mar 4 2005 request-answer
> -rwxr-x--- 1 mail daemon 29520 Mar 4 2005 resend
> -rw-r----- 1 mail daemon 10462 Mar 4 2005 sample.cf
> -rwxr-x--- 1 mail daemon 8060 Mar 4 2005 shlock.pl
> drwx------ 75 mail daemon 4096 Mar 28 13:40 sites
> drwxr-x--- 2 mail daemon 4096 Jan 7 10:07 Tools
> -rwsr-xr-x 1 root daemon 10059 Mar 4 2005 wrapper
>
>
>
>
> Then I deleted the re-added the lists from the GUI.
>
> It works now.
>
>
>
>Diego Lo Giudice says:
>>Ken, did you make a migration of sites before this error??
I did migrate some sites.
I don't know if it was working before I migrated the sites or not. The site
that I migrated had a list that stopped working so that is how I found out.
----
Ken Marcus
Precision Web Hosting, Inc.
http://www.precisionweb.net