Next: Deliveries fail ‘<samp><span class="samp">temporary qmail-queue error</span></samp>’, Previous: The last line of a <samp><span class="file">DIR/text/</span></samp> file is ignored, Up: Possible error conditions in ezmlm lists
Assuming that the user initiated the subscribe request, got a ‘confirm’ request, and replied correctly, there are two possible causes for the problem: Either the list is not subscription moderated (in this case the user is subscribed and received a note saying so) or the list is subscription moderated but no moderators have been added (ezmlm-manage(1) sends out the request and doesn't mind that there are no recipients).
Check that the list is subscription moderated:
% cat DIR/modsub
If this fails the list is not subscription moderated. If it succeeds with a directory name with a leading ‘/’, this is your ‘moddir’. If not:
% cat DIR/remote
If this succeeds with a directory name with a leading ‘/’, this is your moddir, otherwise the moddir is ‘DIR/mod/’.
Check for moderators:
% ezmlm-list moddir
If there are none, this is your problem. If there are some, check the mail log to see what happened when the CONFIRM requests was supposed to have gone out. Assure correct ownerships for the moderator db:
% chown -R user moddir
# chown -R alias moddir
Another possible problem is that you are trying to use the remote admin feature to subscribe a user, but you get no CONFIRM request. Usually, this is due to your SENDER address not being in the moderator database. The CONFIRM request went to the target address instead, since as far as ezmlm is concerned, you are a regular user.