LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
"Dorn, Jeffrey T. Jr." <[log in to unmask]>
Fri, 26 Oct 2001 10:06:59 -0400
text/plain (65 lines)
Well, I consider myself pretty well-versed in the art of DISTRIBUTE jobs
now, and I have to say that I really love the whole mechanism. It has vastly
expanded what I've been able to do with LISTSERV. Long live mail-merge.

Now, however, I have been testing a list using the
*Mail-Merge= Yes
header keyword. Every job I send gets rejected for security reasons:

[log in to unmask] sent a DISTRIBUTE job that was rejected for
the  following  reason:  "Job  did  not  pass  security  checks".  Job  3538
("MMTEST-L MAILDIST") transferred to [log in to unmask]

I have searched the archives of this list and LSTOWN-L and I did find
someone having similar problems. They were instructed that their lines were
too long, and to use the comma-escape-continuation format. That must have
worked for them because they didn't post anymore after that. I tried the
same thing, and it didn't work. I knew it wouldn't, too, because I could
send the exact same job directly to the LISTSERV@*      address and it gets
distributed just fine. Here is a sample of one of my test jobs:

//Plain_Text JOB
// DISTRIBUTE MAIL-MERGE DBMS=LIST(mmtest-l) ,
[log in to unmask] PW=my_passwd
//to DD " "
//Data DD *,EOF
To: &*TO;
From: <[log in to unmask]>
Return-Path: <[log in to unmask]>
Subject: Test: &*DATE
Date: &*DATE;
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1

Hello world :P

I tried sending this directly to LISTSERV@, as I mentioned above, and to
MMTEST-L@, which is the list I am testing. I get the error message when I
send it to the list.

Now here's another twist: I also get this response simultaneously:

Your message dated Fri, 26 Oct 2001 09:53:41 -0400 with no subject has been
successfully distributed to the MMTEST-L list (3 recipients).

! However, the message is not actually distributed to the list subscribers,
but it does show up in the archive.

Can someone tell me what I'm doing wrong? And for the record, I have changed
my header several times, trying everything I could think of, including using
the list creation password instead of my personal password, to no avail.

Thanks all--

Jeff


*************************************
Jeff Dorn
GPO LISTSERV Site Administrator

Computer Specialist, Network Services
US GPO ESDD Network Systems Branch
202-512-2010 x32953
[log in to unmask]

ATOM RSS1 RSS2