flist: Couldn't exec procmail
I am attempting to move an existing list from one server to another. I get the following error, which is new to me, and I can't figure out how to fix it: ----- The following addresses had permanent fatal errors ----- "|flist listname" (reason: Service unavailable) (expanded from: <listname@domain.com>) ----- Transcript of session follows ----- flist: Couldn't exec "../.bin/procmail" 554 5.0.0 Service unavailable System is using procmail v3.22 Sendmail 8.12.11 flist is linked from /etc/smrsh to /home/slist/.bin/flist Thank you for any help you can provide. Kim
flist: Couldn't exec "../.bin/procmail"
In SmartList's .bin directory (in your case, /home/slist/.bin), there is usually a symbolic link to the location where procmail is installed on your system. Since you're migrating from one system to another, it seems likely that you've copied over the linnk from your old system, and that procmail is installed in a different location on the new system. Do you have shell access to your smartlist installation? If not, you'll need to have the system administrator fix this. If you do, type "which procmail" (or "whence procmail" if you use ksh). That should tell you where procmail is located, provided it's in your PATH. Now type the following: cd /home/slist/.bin ls -l procmail If this is a symbolic link, the result will look something like this: lrwxr-xr-x 1 slist users 23 Jul 10 1999 procmail@ -> /usr/local/ bin/procmail If it is a symbolic link, and it points to the wrong place, or if there is no procmail in the .bin directory at all, you simply need to replace the link, and point it to the location you found above: rm procmail ln -s `which procmail` procmail If you see something like this instead: -rwxr-xr-x 1 slist users 73728 Apr 3 2004 procmail* you probably built a custom version of procmail with your smartlist installation (probably because the system version was too old or because your old system didn't have one). If the new system is a different processor or OS, the old executable probably won't work on your new system. In this case, I'd move it aside (rather than remove it), and try the system's procmail to see if it works: mv procmail procmail.orig ln -s `which procmail` procmail -cary
participants (2)
-
Cary Coutant
-
Kim Ridenour