Bingo! That solved it.

Thanks a million.

Rick

I had the very same experience when I started using SmartList that was presented by my web host provider. I too, do not have telnet access and suspected that perhaps the MSDOS editor was not compatible or inserted

extra

characters. Fortunately, I had another PC loaded with Linux OS, so I

FTP'd

the rc.custom file to my Linux machine. I used VI to massage the

rc.custom

file and FTP'd it back to Smartlist. It worked!

At 10:10 AM -0400 8/29/00, Rick May is rumored to have typed:

X-Diagnostic: Mail coming from a daemon, ignored

Im not sure what that means. Anyone have any advice on what I can do to make this work?

I can guess; I bet you're using an address like postmaster@, admin@, etc. Try using a different address to send the X-Command from. (Please see the recent discussion about the FROM_DAEMON macro, subjected "Sub and Unsub problems.")

Charlie

Quoting Rick May rick@toonstruck.com:

No, that doesnt fit me at all..

If you don't provide enough information help is impossible. You should also ask your provider at first to give you the necessary help or sufficient access rights. If you can't get it, change your provider.

Another related question.. After reading some of the list archives, it appears that I should be able to send an email from the maintaining

list

account with "X-command email@mydomain.com password showdist" and

expect it

to work?

You need to prepend a colon after "X-command". Please read the Smartlist Manual and don't rely on messages send to this list.

Werner -- Pure NetworX GmbH voice: +41 78 6047538 Viktoriastr. 15 http://www.pure.ch CH-8057 Zurich

At 12:18 PM -0400 8/29/00, Rick May is rumored to have typed:

I provided all the information in an earlier message. I dont know what else I can provide. Im hoping someone had a similiar problem and can point me in the right direction.

No, sir, you did NOT provide all the information...you provided darned little info, which is forcing us to guess that yours is one of the routine newbie mistakes. When I suggest you are using a DAEMON address, you _say,_ "No, that doesnt fit me at all," but don't bother to mention exactly what address you _ARE_ using (there are a bunch of addresses that will get caught in the FROM_DAEMON macro). You told us what the X-Diagnostic: header said, but did _not_ give us any additional information. You didn't tell us what address you _are_ using, nor did you exerpt the log, nor did you even bother to copy the message you received with the X-Diagnostic: header, which might have allowed us to figure out what you're doing wrong. (And I'm betting you ARE doing something wrong.)

You are asking us to help you while not telling us everything we need to know. Did you set VERBOSE and check the log? Did you check the log at all? Do you even know you HAVE a log?

As far as my provider, I also previously stated that they provide no tech support for smartlist. Changing providers at this time is not an option.

That's fine...but you are going to have to do _some_ of this yourself before coming to the list for help; that's all Werner was telling you. We are not to replace the paid support staff - we all have jobs, businesses, and lives of our own, and so need you to do at least _some_ of the trouble-shooting yourself.

I did try with a colon after the X-command. Unfortunately I forgot to put that in my email to this mailing list.

How were we to know that? (And why do I have the feeling you're not adding a new X-Command: header field, but just dropping it in the body of an email message without applying the .examples/rc.local.r00 recipe...better question - do you even understand what an X-Command header field is?)

As far as the manual, all links to it from various FAQs dont seem to work.

(*sigh*) There is a file in the .etc directory of the standard distribution named Manual...you don't need "links...from various FAQs," it's part of the distribution. (But since you didn't tell us what your provider installed for you, or even whether your provider supplies you a list under their install or provides you one of your own, we can't be a lot of help here, either. Honest, we can't read minds, nor divine the structure of your install.)

Please read the Manual file first, and if this doesn't help feel free to ask specific questions giving us the information we need to avoid playing 20-questions and guessing at each step of the way.

Charlie

At 3:08 PM -0400 8/29/00, Rick May is rumored to have typed:

Obviously I have struck a nerve with more than one person.

It happens; you say your provider doesn't supply support, yet you expect us to do so, and when we are forced to guess based on the scanty available information, we get incomplete replies. It can get...frustrating somedays.

It works fine when I comment out the reply-to line in rc.custom. Why would it work commented out, but stop working when it isnt commented out?

Not a clue; set VERBOSE=yes, and run one X-Command: with the reply-to munged. Provide both the complete mail returned to the maintainer (feel free to munge the list password, but don't muck with anything else!) and the relevant section of log file (which will be considerably larger than that available without VERBOSE).

Oh, yeah...you've referenced the Reply-To: a couple of times, but you never did get around to telling us the value of $listaddr...

Charlie

First Id like to thank everyone who has been helping with my issues. Second Id like to apologize for the continuing questions. (I will be out of your hair shortly.. :)

Im having continuing problems with Smartlist. But after a ton of trial and error, I have narrowed down the problems.

1) I can issue X-Commands from the web based form that is supplied from my hosting company ONLY if I comment out the "reply-to" in rc.custom

Another words. X-commands work just fine until I try to change the reply-to so that replies go back to the mailing list. As soon as I do this (reply-to goes back mailing list), x-command starts giving me the following errors in the header

X-Diagnostic: Mail coming from a daemon, ignored

Im not sure what is causing this, and why it would make a difference if I had the reply-to set (I have it set to Reply-To: $listaddr) as it is.

Any ideas?

Thanks