Text file for use by PMAIL

Michael

posted Oct 22 '11 at 3:29 pm

[quote user="Fews"]

Weekly Report

TO: xxx@gmail.com, xxx@mail.edu

BC: xxx@email.edu

SU: Subject

AT: C:\Reporting\Rprt.pdf,unknown,0

Good morning all,

BODY OF TEXT

Thanks.

signed.[/quote]

By comparing the PMW file resulting from your above script to one created by Pegasus Mail you could have figured it out (although I must say Pegasus Mail is overly strict here, IMO): The two letter code mustn't be followed by a blank space, i.e. a working version of the above should look like this:

Weekly Report
TO:xxx@gmail.com, xxx@mail.edu
BC:xxx@email.edu
SU:Subject
MI:1
AT:C:\Reporting\Rprt.pdf,unknown,0

Good morning all,

BODY OF TEXT

Thanks.

signed.

But there's another important issue: Please note the line containing MI:1, if you do not add this line it won't create a legal MIME message and the attachment will be sent as an UU encoded enclosure instead.

<p>[quote user="Fews"]</p> <div>Weekly Report</div> <div>TO: xxx@gmail.com, xxx@mail.edu</div> <div>BC: xxx@email.edu</div> <div>SU: Subject</div> <div>AT: C:\Reporting\Rprt.pdf,unknown,0</div> <div><div> </div><div>Good morning all,</div><div>&nbsp;</div><div>BODY OF TEXT</div><div>&nbsp;</div><div>Thanks.</div><div>&nbsp;</div><div>signed.[/quote]</div><div>By comparing the PMW file resulting from your above script to one created by Pegasus Mail you could have figured it out (although I must say Pegasus Mail is overly strict here, IMO): The two letter code mustn't be followed by a blank space, i.e. a working version of the above should look like this:</div><div> </div></div><div> <blockquote><div> Weekly Report </div><div>TO:xxx@gmail.com, xxx@mail.edu</div><div>BC:xxx@email.edu</div><div>SU:Subject</div><div>MI:1</div><div>AT:C:\Reporting\Rprt.pdf,unknown,0</div><div> </div><div>Good morning all,</div><div>&nbsp;</div><div>BODY OF TEXT</div><div>&nbsp;</div><div>Thanks.</div><div>&nbsp;</div><div>signed.&nbsp;</div></blockquote> But there's another important issue: Please note the line containing <i>MI:1</i>, if you do not add this line it won't create a legal MIME message and the attachment will be sent as an UU encoded enclosure instead.</div>

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Fews

posted Oct 20 '11 at 7:00 pm

I scanned through the first 10 pages of this forum and dropped a few searches but could not get to the specific issue I am having.

I am using PMAIL as my autoemailer program which is run out of some SAS code. Basically, the SAS code drops into the command prompt and runs pmail.

Command line: x 'C:\pmail\programs\winpm-32.exe -J "C:\Reporting\Email.txt"';

Now then, this line calls a text file in the folder that reads:

**********************************************************************

Weekly Report

TO: xxx@gmail.com, xxx@mail.edu

BC: xxx@email.edu

SU: Subject

AT: C:\Reporting\Rprt.pdf,unknown,0

Good morning all,

BODY OF TEXT

Thanks.

signed.

*******************************************************************

I then get the error: The file 'Rprt.pdf' which has been attached to a message in your outgoing mail queue, cannot be located. Please edit and re-attach the file, or remove it prior to sending.

The path is correct and has been checked by myself and my supervisor. Removing the attachment statement in the text file pushes the email through just fine and everyone listed receives the mail sans PDF report.

I have attempted to remove the 'unknown' and '0' from the attachment statement, which sends the email through without the attachment obviously. I have also attempted quotes to enclose the name of the attachment, etc. Anyone have a similar issue or something close that I can try a work around?

<p>I scanned through the first 10 pages of this forum and dropped a few searches but could not get to the specific issue I am having.</p><p>I am using PMAIL as my autoemailer program which is run out of some SAS code. Basically, the SAS code drops into the command prompt and runs pmail.</p><p>Command line: &nbsp;x 'C:\pmail\programs\winpm-32.exe -J &nbsp;"C:\Reporting\Email.txt"';</p><p>Now then, this line calls a text file in the folder that reads:</p><p>**********************************************************************</p><div><div>Weekly Report</div><div>TO: xxx@gmail.com, xxx@mail.edu</div><div>BC: xxx@email.edu</div><div>SU: Subject</div><div>AT: C:\Reporting\Rprt.pdf,unknown,0</div><div> </div><div>Good morning all,</div><div>&nbsp;</div><div>BODY OF TEXT</div><div>&nbsp;</div><div>Thanks.</div><div>&nbsp;</div><div>signed.&nbsp;</div><div> </div></div><div>*******************************************************************</div><div>&nbsp;</div><div>I then get the error: The file 'Rprt.pdf' which has been attached to a message in your outgoing mail queue, cannot be located. Please edit and re-attach the file, or remove it prior to sending.</div><div>The path is correct and has been checked by myself and my supervisor. Removing the attachment statement in the text file pushes the email through just fine and everyone listed receives the mail sans PDF report.</div><div>I have attempted to remove the 'unknown' and '0' from the attachment statement, which sends the email through without the attachment obviously. I have also attempted quotes to enclose the name of the attachment, etc. Anyone have a similar issue or something close that I can try a work around?&nbsp;</div>

Michael

posted Oct 20 '11 at 7:30 pm

[quote user="Fews"]Anyone have a similar issue or something close that I can try a work around? [/quote] Did you try to create a similar message from within Pegasus Mail (using the same attached file) and send it? Does it throw the same error? And if not, is there any significant difference in the resulting PMW file that you can duplicate in your script to work around the error?

If all this doesn't work out you might want to try Pegasus Mail's DDE interface (see winpmdde.txt in Pegasus Mail's Resource subdirectory).

<p>[quote user="Fews"]Anyone have a similar issue or something close that I can try a work around? [/quote] Did you try to create a similar message from within Pegasus Mail (using the same attached file) and send it? Does it throw the same error? And if not, is there any significant difference in the resulting PMW file that you can duplicate in your script to work around the error?</p><p>If all this doesn't work out you might want to try Pegasus Mail's DDE interface (see <em>winpmdde.txt</em> in Pegasus Mail's <em>Resource</em> subdirectory).</p>

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Fews

posted Oct 20 '11 at 7:59 pm

Ahh yes - always seem to leave out a detail or two.

I could send the email manually with the attached PDF without a problem. The only differences I could see is when sending through the command prompt, the attachment in Pegasus (through the attachments tab) on that email is set to size 0.0k. Setting up the email manually and attaching the PDF populates with a size 120k.

This leads me to believe the AT: part of the text file is in error in that it keeps the "0" file size. I have also attempted to bump that to the size of the file found when manually attaching the PDF as well with the same errors.

I will check out the DDE stuff after lunch. Thanks for the input.

<p>Ahh yes - always seem to leave out a detail or two. </p><p>I could send the email manually with the attached PDF without a problem. The only differences I could see is when sending through the command prompt, the attachment in Pegasus (through the attachments tab) on that email is set to size 0.0k. Setting up the email manually and attaching the PDF populates with a size 120k. </p><p>This leads me to believe the AT: part of the text file is in error in that it keeps the "0" file size. I have also attempted to bump that to the size of the file found when manually attaching the PDF as well with the same errors. </p><p>&nbsp;I will check out the DDE stuff after lunch. Thanks for the input.&nbsp;</p>

Michael

posted Oct 20 '11 at 8:35 pm

[quote user="Fews"]I will check out the DDE stuff after lunch. Thanks for the input. [/quote]

Before wasting too much time try the following first: Use double backslashes like this: C:\\Reporting\\Rprt.pdf (don't ask me why, I'm doing something similar with my MiniDump extension for creating crash dumps (it uses DDE); I don't remember how I figured it out).

<p>[quote user="Fews"]I will check out the DDE stuff after lunch. Thanks for the input. [/quote]</p><p>Before wasting too much time try the following first: Use double backslashes like this: C:\\Reporting\\Rprt.pdf (don't ask me why, I'm doing something similar with my MiniDump extension for creating crash dumps (it uses DDE); I don't remember how I figured it out).</p>

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

Thomas R. Stephenson

posted Oct 20 '11 at 8:47 pm

> I am using PMAIL as my autoemailer program which is run out of some SAS code. Basically, the SAS code drops into the command prompt and
> runs pmail.
>
> Command line: x 'C:\pmail\programs\winpm-32.exe -J "C:\Reporting\Email.txt"';

I have no solution for this other than to forget about using Pegasus Mail for this, this commandline option is like using a sledge hammer to kill a fly. Try Blat! instead.to send your file.

BLAT http://sourceforge.net/projects/blat

DESCRIPTION:

Blat is a Public Domain Windows NT console utility that sends the contents of a file in an e- mail message using the SMTP protocol. Blat is useful for creating scripts where mail has to be sent automatically (CGI, backups, etc.) To use Blat you must have access to a SMTP server via TCP-IP. Blat uses the a DLL ("gensock" or "gwinsock") from WinVN, the public domain usenet newsreader for windows. Blat can store a default SMTP server address and a default "From:" field in the registry. The server's address can be overriden using the -server flag, and the "From:" address using the -f flag. Input from the console (stdin) can be used instead of a disk file (if the special filename '-' is specified). Blat can also "carbon copy" and "blind carbon copy" the message. Impersonation can be done with the -i flag which puts the value specified in the "From:" line, however when this is done the real senders address is stamped in the "Reply-To:" and "Sender:" lines. This feature can be useful when using the program to send messages from NT users that are not registered on the SMTP host. Optionally, blat can also attach multiple binary files to your message.

You could also have your application write a message in final form directly to the queue. Here's a sample, the message body only needs the required data. This will be sent the next time Pegasus Mail sends the mail just like using the commandline mail option.

------------------------ spam.101 ----------------------------
$$ cslaw@indirect.com
tstephen@mtshasta.lmms.lmco.com
support@tstephenson.com

From: swallace@cyberpromo.com (Sanford Wallace)
Organization: Ambulance Chasing, Inc.
To: "Laurence A Canter" <spamford@wilhelp.com>
Date: Fri, 17 Oct 2003 12:55:34 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Test Message
Reply-to: "Taylor Jimenez" <taylor@wilhelp.com>
CC: "Martha S Siegel" <Martha@smartbotpro.net>
Priority: normal
Message-id: <399917090.3123.1066456430@persephone.pmail.gen.nz>
X-mailer: Pegasus Mail for Win32 (v3.12c)

This is a test of the mail servers settings for spammers.

Here's a little text file that you can use to test Mercury/32
or Pegasus Mail. With Mercury or Mercury/32 you save the
file in the Mercury queue with the 101 extension. With Pegasus
Mail you save the message in the HOME mail directory with the
PMX file extension.

This is a file in "Glue" headers format, the $$ line is the
SMTP MAIL FROM: address, the next two lines are RCPT TO:
addresses and the blank line is the separator from the RFC 2822
message body. You can delete the Date: or Message-ID line in
the message body, the SMTP relay host is expected to add these
to the file. Copy and paste the file to Notepad and then save
it with the correct extension it the correct queue. Modify the
RCPT TO: "Glue" headers to use your own addresses.
---------------------------- cut here ----------------------------

<p>&gt; I am using PMAIL as my autoemailer program which is run out of some SAS code. Basically, the SAS code drops into the command prompt and &gt; runs pmail. &gt; &gt; Command line:&nbsp; x 'C:\pmail\programs\winpm-32.exe -J&nbsp; "C:\Reporting\Email.txt"'; I have no solution for this other than to forget about using Pegasus Mail for this, this commandline option is like using a sledge hammer to kill a fly.&nbsp; Try Blat! instead.to send your file. BLAT&nbsp; http://sourceforge.net/projects/blat DESCRIPTION: Blat is a Public Domain&nbsp; Windows NT console utility that sends the contents of a file in an e- mail message using the SMTP protocol. Blat is useful for creating scripts where mail has to be sent automatically (CGI, backups, etc.) To use Blat you must have access to a SMTP server via TCP-IP. Blat uses the a DLL ("gensock" or "gwinsock") from WinVN, the public domain usenet newsreader for windows. Blat can store a default SMTP server address and a default "From:" field in the registry. The server's address can be overriden using the -server flag, and the "From:" address using the -f flag. Input from the console (stdin) can be used instead of a disk file (if the special filename '-' is specified). Blat can also "carbon copy" and "blind carbon copy" the message. Impersonation can be done with the -i flag which puts the value specified in the "From:" line, however when this is done the real senders address is stamped in the "Reply-To:" and "Sender:" lines. This feature can be useful when using the program to send messages from NT users that are not registered on the SMTP host.&nbsp;&nbsp; Optionally, blat can also attach multiple binary files to your message.</p><p>You could also have your application write a message in final form directly to the queue.&nbsp; Here's a sample, the message body only needs the required data.&nbsp; This will be sent the next time Pegasus Mail sends the mail just like using the commandline mail option. </p><p>------------------------&nbsp;&nbsp; spam.101 ---------------------------- $$ cslaw@indirect.com tstephen@mtshasta.lmms.lmco.com support@tstephenson.com From: swallace@cyberpromo.com (Sanford Wallace) Organization: Ambulance Chasing, Inc. To: "Laurence A Canter" &lt;spamford@wilhelp.com&gt; Date: Fri, 17 Oct 2003 12:55:34 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Test Message Reply-to: "Taylor Jimenez" &lt;taylor@wilhelp.com&gt; CC: "Martha S Siegel" &lt;Martha@smartbotpro.net&gt; Priority: normal Message-id: &lt;399917090.3123.1066456430@persephone.pmail.gen.nz&gt; X-mailer: Pegasus Mail for Win32 (v3.12c) This is a test of the mail servers settings for spammers. Here's a little text file that you can use to test Mercury/32 or Pegasus Mail.&nbsp;&nbsp; With Mercury or Mercury/32 you save the file in the Mercury queue with the 101 extension.&nbsp; With Pegasus Mail you save the message in the HOME mail directory with the PMX file extension. &nbsp; This is a file in "Glue" headers format, the $$ line is the SMTP MAIL FROM: address, the next two lines are RCPT TO: addresses and the blank line is the separator from the RFC 2822 message body.&nbsp; You can delete the Date: or Message-ID line in the message body, the SMTP relay host is expected to add these to the file.&nbsp; Copy and paste the file to Notepad and then save it with the correct extension it the correct queue.&nbsp; Modify the RCPT TO: "Glue" headers to use your own addresses. ---------------------------- cut here ---------------------------- &nbsp;</p><p>&nbsp; </p>

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history