When I send a file attachment in Pegasus -- like a PDF file,
it goes as an attachment, but when the file is in Ascii format,
Pegasus sometuimes seems to incorporate the attachment into the
message, instead of as a file attachment.
Is there a setting where I can change this behaviour, so that
it will not incorporate such attachments into the message?
When I send a file attachment in Pegasus -- like a PDF file, it goes
as an attachment, but when the file is in Ascii format, Pegasus
sometuimes seems to incorporate the attachment into the message,
instead of as a file attachment.
Is there a setting where I can change this behaviour, so that it will
not incorporate such attachments into the message?
Steve Hayes wrote:
When I send a file attachment in Pegasus -- like a PDF file,
it goes as an attachment, but when the file is in Ascii format,
Pegasus sometuimes seems to incorporate the attachment into the
message, instead of as a file attachment.
Is there a setting where I can change this behaviour, so that
it will not incorporate such attachments into the message?
Check these two settings:
Tools > Options
Outgoing mail > Messages and replies
Use these settings...
Use MIME features [x] On
Tools > Options
Outgoing mail > Sending mail
Advanced settings
[] Enable text-file autodetection...
On 02 Apr 2016, Steve Hayes <hayesstw@telkomsa.net> wrote in >comp.mail.pegasus-mail.ms-windows:
When I send a file attachment in Pegasus -- like a PDF file, it goes
as an attachment, but when the file is in Ascii format, Pegasus
sometuimes seems to incorporate the attachment into the message,
instead of as a file attachment.
Is there a setting where I can change this behaviour, so that it will
not incorporate such attachments into the message?
I think I recall this problem from years ago, and that the solution was >adding a line to one of PMail's configuration files, but I'll have to
do some investigation to find out which.
One possibility is FILETYPE.PM . Do you have this line in yours?
Text,0,X,0,.TXT
Text,0,X,0,.TXT
Yes, that line is there. I'm not sure what it does, though, or how
to change it.
One of the biggest problems occurs when I send GEDCOM files
(GEnealogy Data COMmunications) files to non-savvy computer users.
These are genealogy data files in Ascii format, which can be
imported into most genealogy programs.
When it is sent as an attachment, anyone can simply tell their
genealogy program to import the attached file with no problems.
But when Pegasus incorporates it into a message, most non-savvy
computer users do not know how to mark the text, save it as a file
with a GED extension, and then import it.
On 10 Apr 2016, Steve Hayes <hayesstw@telkomsa.net> wrote in >comp.mail.pegasus-mail.ms-windows:
Text,0,X,0,.TXT
Yes, that line is there. I'm not sure what it does, though, or how
to change it.
You would change it by editing the file with a text editor while
Pegasus is shut down. But if you have that line and it's not commented
out, and that line is what controls the behavior, there would be no
need to alter it.
The FILETYPE.PM file is documented at the top. It tells Pegasus to
check either the first x bytes of a file or the file extension to
determine how to deal with attaching a file of that type. In this case, >Pegasus should see that the file extension is .txt and deal with it in
a consistent way. Are you sure the files you're attaching always have a
.txt extension?
My Pegasus setup handles *.txt files as attachments rather than
inclusions, as you and I prefer. I don't know why yours acts
differently. Maybe FILETYPE.PM isn't the file that controls it. By the
way I do NOT have the "Enable text-file autodetection when sending >attachments" option turned on.
Not always. As I noted elsewhere, some of them are Gedcom files
that have a .GED extension. I could not understand from the
documentation what the FILETYPE.PM file actually does with the
files, apart from telling you what kind of file the attachment
contains.
I see that it defines files with the .DOC extension as MS Word
files, but I have a number of text files with the DOC extention,
before Microsoft laid claim to it.
Is there a setting where I can change this behaviour, so that it will
not incorporate such attachments into the message?
On article <q7t0gb9l4in4broj77ro9jp9d79167pim1@4ax.com>, Steve Hayes
wrote:
Is there a setting where I can change this behaviour, so that it will
not incorporate such attachments into the message?
Try modifying Filetype.pm. Here is what I use:
;Text,0,X,0,.TXT
binary,0,R,0,\032,R,0,\013 >\010,R,0,e,R,0,E,R,0,t,R,0,T,R,0,n,R,0,N,R,0,r,R,0,R,R,0,i,R,0,I,R,0, >o,R,0,O,R,0,a,R,0,A,R,0,s,R,0,S,R,0,d,R,0,D,R,0,h,R,0,H,R,0,l,R,0,L,R >,0,c,R,0,C,R,0,f,R,0,F,R,0,p,R,0,P,R,0,u,R,0,U,R,0,m,R,0,M
Note that the ordinary .TXT line was commented. The following line
that starts with "binary" goes all the way through "R,0,M". It's a
single line. I'm using this ever since, and it never failed me.
Thanks very much.
Try modifying Filetype.pm. Here is what I use:
;Text,0,X,0,.TXT
binary,0,R,0,\032,R,0,\013 \010,R,0,e,R,0,E,R,0,t,R,0,T,R,0,n,R,0,N,R,0,r,R,0,R,R,0,i,R,0,I,R,
0,
o,R,0,O,R,0,a,R,0,A,R,0,s,R,0,S,R,0,d,R,0,D,R,0,h,R,0,H,R,0,l,R,0,L
,R ,0,c,R,0,C,R,0,f,R,0,F,R,0,p,R,0,P,R,0,u,R,0,U,R,0,m,R,0,M
Note that the ordinary .TXT line was commented. The following line
that starts with "binary" goes all the way through "R,0,M". It's a
single line. I'm using this ever since, and it never failed me.
On 11 Apr 2016, Euler German <rstrezna.hfrarg@znvyahyy.invalid>
wrote in comp.mail.pegasus-mail.ms-windows:
Try modifying Filetype.pm. Here is what I use:
;Text,0,X,0,.TXT
binary,0,R,0,\032,R,0,\013
\010,R,0,e,R,0,E,R,0,t,R,0,T,R,0,n,R,0,N,R,0,r,R,0,R,R,0,i,R,0,I,R,
0,
o,R,0,O,R,0,a,R,0,A,R,0,s,R,0,S,R,0,d,R,0,D,R,0,h,R,0,H,R,0,l,R,0,L
,R ,0,c,R,0,C,R,0,f,R,0,F,R,0,p,R,0,P,R,0,u,R,0,U,R,0,m,R,0,M
Note that the ordinary .TXT line was commented. The following line
that starts with "binary" goes all the way through "R,0,M". It's a
single line. I'm using this ever since, and it never failed me.
Does that "binary" line affect text files? I really don't know and I
don't understand how to parse that line, but I see that I added that
same line in 2002, then later commented it out again. I've been running
it that way since, and text files have been handled the way I prefer,
as attachments rather than inclusions.
On 11 Apr 2016, Euler German <rstrezna.hfrarg@znvyahyy.invalid>
wrote in comp.mail.pegasus-mail.ms-windows:
Try modifying Filetype.pm. Here is what I use:
;Text,0,X,0,.TXT
binary,0,R,0,\032,R,0,\013 \010,R,0,e,R,0,E,R,0,t,R,0,T,R,0,n,R,0,N,R,0,r,R,0,R,R,0,i,R,0,I,R,
0,
o,R,0,O,R,0,a,R,0,A,R,0,s,R,0,S,R,0,d,R,0,D,R,0,h,R,0,H,R,0,l,R,0,L
,R ,0,c,R,0,C,R,0,f,R,0,F,R,0,p,R,0,P,R,0,u,R,0,U,R,0,m,R,0,M
Note that the ordinary .TXT line was commented. The following line
that starts with "binary" goes all the way through "R,0,M". It's a
single line. I'm using this ever since, and it never failed me.
Does that "binary" line affect text files? I really don't know and I
don't understand how to parse that line, but I see that I added that
same line in 2002, then later commented it out again. I've been running
it that way since, and text files have been handled the way I prefer,
as attachments rather than inclusions.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 50:00:50 |
| Calls: | 6,649 |
| Calls today: | 1 |
| Files: | 12,200 |
| Messages: | 5,330,189 |