I got a bunch of errors like following in my Smarlist log file:
../.bin/subscribe: line 1: ./cat: Permission denied
../.bin/subscribe: line 112: ./cat: Permission denied
../.bin/subscribe: line 123: ./cat: Permission denied
../.bin/subscribe: line 140: ./cat: Permission denied
../.bin/subscribe: line 142: ./cat: Permission denied
../.bin/arch_retrieve: line 1: ./cat: Permission denied
../.bin/arch_retrieve: line 312: ./cat: Permission denied
../.bin/procbounce: line 142: ./cat: Permission denied
while the list still works on distributing group mails and take
sub/unsub requests.
I checked all possible file permissions and folder/file ownership
-- everything seem fine: /bin/cat - 755; ~slist/.bin/subscribe - 755;
the target files to read have 664 and user:group=slist:slist
One odd thing is every successfully posted mail is saved into a
file called "cat" in the list directory.
Any suggestion where to look further?
Zhiliang
> Maybe you could help me! I have installed procmail and smartlist
> on top of
> sendmail
> on the Solaris 8 server. I can created a mailing list (called:
> mylist), I
> can subscribe
> and unsubscribe to mailing list and they are working fine, but when
> I send a
> regular email
> message to the list (mylist(a)abc.com), the email was never forward
> to any
> member of the list.
> Neither one of the member have received my email. But, I can see the
> message in the log
> (mylist/log).
Sorry, but there are too many things that could be going wrong to
speculate without more information. Did the message show up in the
archive/latest directory? What did you see in the log file?
Try editing the rc.custom file for your list and uncomment the
"VERBOSE=yes" line. Then send another test message and look again at
the log file for clues. If that doesn't tell you right away what's
wrong, post the log entries to this list for help.
-cary
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(a)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
Hello,
For reasons I don't understand, Smartlist sometimes removes a different
address than the one that sent the unsubscription request. This problem
also occurs with 'procbounce' where a full functional email address
will be accidently removed instead of the address that was actually
bouncing.
An example from the log file looks like:
unsubscribe: attempt 75 address1 6946 address2 by: address2 Mon Jun
6 01:31:00 EDT 2005
What do the numbers ('75' and '6946') mean?
The relevant entries from rc.custom are:
#maxhist = 32 # bounce history limit
#minbounce = 4 # no. of bounces before removal
#cutoff_bounce = 256 # lines to keep in bounce processing
#match_threshold= 30730 # for close matches to the list
#medium_threshold= 28672 # for not so close matches to the list
#loose_threshold= 24476 # for loosely finding your name
I assume that since these are not uncommented, the defaults will be
used.
Have anyone else seen this? Any solutions?
Thanks,
- Harshal
__________________________________
Discover Yahoo!
Get on-the-go sports scores, stock quotes, news and more. Check it out!
http://discover.yahoo.com/mobile.html