Arthur Moyer writes:
I've had reason to add another mailing list recently, so I went throught the normal procedure as directed. However, when I send an email to help or subscribe, I get the following (I've changed the email addresses to protect the guilty):Aug 13 10:50:44 localhost courierlocal: id=0054210E.4A831329.0000406E,from=<[email protected]>,addr=<[email protected]>: /home/MailLists/omniphil: No such file or directory. Aug 13 10:50:44 localhost courierlocal: id=0054210E.4A831329.0000406E,from=<[email protected]>,addr=<[email protected]>,status: deferred
There were other log entries for the same delivery. You need to show all log records for this delivery attempt, all log records with the same unique id.
Now, the directory IS there, it was created with couriermlm, the permissions are globally accessable (777)
No permission on any directory should be 777. That really means that you thought you have some permission-related misconfiguration, and you thought that you had to do this to fix it.
Well, if you cannot figure out a permission-related problem, setting the permissions on a directory or a file to 777 will never fix your real problem. Your problem is not that the directory's or the file's permission isn't 777. Therefore, changing it to 777 does not really fix anything.
as the other list directories are, the aliases
are set correctly (identical to the other 6 mailing lists barring the
directory name).
You say that they are set correctly. It may very well be that something is not right, but if you think you have everything set correctly, saying that will not help anyone figure out what the problem is.
Rather than paraphrasing or describing your configuration, you need to actually show it. You probably have a typo in your .courier file, but since you did not show the actual contents of your .courier file,you merely stated that everything is set correctly, nobody can really know if you really have an unintentional typo there, and what it is.
The trick to obtaining the best chance of getting help is to post sufficient detail, but not too much. Dumping entire logs, and all contents of all configuration files leaves an impression that the posted doesn't care enough to try to figure it out himself. The correct approach is to leave out clearly irrelevant stuff, and show everything else. In your case, for example, this clearly has nothing to do with SSL, or with other messages, so there's no need to post the contents of all the ssl-related configuration files, or logs of other delivery attempts, unless there's some clearly related data there. In your case, you should show
* All log records for two or three failed delivery attempts. Select a couple of delivery failures, and show all of their records.
* Show the contents of the relevant configuration files. That means the alias-related configuration files, also their file attributes -- the output of ls -al on them. Same thing for the .courier files.
* The directory listing of the account's home directory, and maildir (if applicable), again with "ls -al".
This kind of information shows exactly what's going with you, rather than just that everything is presumably set correctly.
pgpyoaQO8WepX.pgp
Description: PGP signature
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
