(August 2001)
|
|
Majordomo-Users (August 2001) |
Since I can't just sit back and wait for someone to help/tell me whats wrong, I have been pokeing around on my box and here is what I have learn that may help someone else help me. The problem has something to do with the resend feature. If I change my aliases file to not use the resend it will send mail to the list but then i lose all the features in the confg file. But when i change it to use the resend i get the mail error. Here is wat i am using for both configurations (taken from aliases file) testlist: :include:/usr/lib/majordomo/lists/testlist testlist: "|/home/majordom/runtime/wrapper @/home/majordom/lists/testlist.resend" How can I test that resend has the write premission or that its setup correctly? also on another note, How do you get majordomo to make the listname.conf file? Jeremy Wesley Web Designer-Flasher-ASP MCP I, MCSE I, MCDBA Cherbonnier Mayer & Associates Office 225.927.9200 X334 Pager 225.660.8778 www.cmaontheweb.com ----- Forwarded by Jeremy Wesley/CMA on 08/13/2001 02:22 PM -----
My system Intel p3 450mhx:::256 ram:::IDE HDD:::3com nic RH 6.2 linux, SENDMAIL, Majordomo My Aliases file owner-cmatest: jwesley,nobody cmatest: "|/home/majordom/runtime/wrapper resend @ /home/majordom/lists/cmatest.resend" cmatest-approval: cmatest-owner cmatest-doit: :include:/home/majordom/lists/cmatest cmatest-request: "|/home/majordom/runtime/wrapper request-awnser cmatest" owner-cmatest-request: owner-cmatest ****YES I ran newaliases on the box after editing the aliases file What I am trying to do: Send to the list cmatest. I tried emailing the list from our production mail servers, and from the box itself. It sends a Delivery Failure Report to the root of the box(which is actually routed back to the production mail servers to my email account). I am new to majordomo and i do not have to much experience with sendmail and linux, but i can get around pretty good. I looked up the error and here is what i found: 5.X.X Permanent Failure A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery. X.5.X Mail Delivery Protocol Status The mail delivery protocol status codes report failures involving the message delivery protocol. These failures include the full range of problems resulting from implementation errors or an unreliable connection. Mail delivery protocol issues may be controlled by many parties including the originating system, destination system, or intermediate system administrators. X.5.0 Other or undefined protocol status Something was wrong with the protocol necessary to deliver the message to the next hop and the problem cannot be well expressed with any of the other provided detail codes. So that wasn't too helpful for me, but maybe someone else can tell me what's really wrong with my system. Thanks Jeremy Wesley Web Designer-Flasher-ASP MCP I, MCSE I, MCDBA Cherbonnier Mayer & Associates Office 225.927.9200 X334 Pager 225.660.8778 www.cmaontheweb.com Follow-Ups:
|