Thanks Ben.

The strange thing is why is the SAME job processed differently?  The

Prod server processes it as a GIVE command, where the QA processes it as

a DISTRIBUTE job.

Also, I can't have the recipient be a POSTMASTER or DIST_ALLOWED_USER --

we have a TON of users who are allowed to do this, and it DOES work on

production without them having those privileges.

Thanks,

Jim



-----Original Message-----

From: LISTSERV site administrators' forum

[mailto:[log in to unmask]] On Behalf Of Ben Parker

Sent: Wednesday, April 26, 2006 7:37 PM

To: [log in to unmask]

Subject: Re: Question about bounce processing





On Wed, 26 Apr 2006 13:21:42 -0400, "Gartner, James"

<[log in to unmask]> wrote:



>To: [log in to unmask]

>Subject: STATUS REQUEST FOR NOLIST-20060426094314791.CHANGELOG TO 

>James.Gart [log in to unmask]

>

>// GIVE NOLIST-20060426094314791.CHANGELOG ,

>TO [log in to unmask] ,

>PW=xxxxxx



OK, that is the correct "long-line" command wrapping syntax.



But I would do it a different way, using the GET command:



To: [log in to unmask]

From: [log in to unmask]



GET NOLIST-20060426094314791.CHANGELOG



The requesting address ([log in to unmask]) will probably need to

be either a POSTMASTER= or a DIST_ALLOWED_USER=.





-----------------------------------------

The information contained in this e-mail message, and any

attachment thereto, is confidential and may not be disclosed

without our express permission. If you are not the intended

recipient or an employee or agent responsible for delivering this

message to the intended recipient, you are hereby notified that you

have received this message in error and that any review,

dissemination, distribution or copying of this message, or any

attachment thereto, in whole or in part, is strictly prohibited. If

you have received this message in error, please immediately notify

us by telephone, fax or e-mail and delete the message and all of

its attachments. Thank you. Every effort is made to keep our

network free from viruses. You should, however, review this e-mail

message, as well as any attachment thereto, for viruses. We take no

responsibility and have no liability for any computer virus which

may be transferred via this e-mail message.