How to attach a file to the same posting as the text body?
Ulf Meinhardt
I clicked in the editor window on the "Attachments..." button and attached the file.
However after sending it to the usenet group realized that two (!) postings were
created with the subjects
....blahblah...(0/1)
and
....blahblah...(1/1)
How can I put the attachment into the same positing and avoid separate postings for
actual text and attachment?
Ulf
Nick Spalding
<4af54fac$0$6723$9b4e...@newsspool2.arcor-online.net>
on 07 Nov 2009 10:45:00 GMT:
You don't say what version you are using and have suppressed the
X-Newsreader header which in these circumstances is a very silly thing
to do.
In 5.0 go to:
Folder | Default Properties | Posting Messages
then either
Email Attachments
or
Usenet Attachments
as appropriate and uncheck:
[ ] Send text as prefix (0/N) section
This may be overridden in Property Schemes and further in individual
folder Properties.
I think it is in the same place in versions back to 3.0 and somewhere
very similar in older ones.
--
Nick Spalding
Agent 5.0/32.1171 IE8
Vista Home Premium SP2, Intel Viiv dual core E6300 (1.86Ghz, 1066MHz FSB),
2GB RAM, 320GB NTFS HD, Video Nvidia GeForce 7900GS LCD 1024x768x75Hz
Ulf Meinhardt
version is 1.93
So your suggestion for v5.0 is not applicable
How does it work in v1.93?
Ulf
On Sat, 07 Nov 2009 11:08:26 +0000, Nick Spalding <spal...@iol.ie>
wrote:
Nick Spalding
on Sun, 08 Nov 2009 12:09:47 +0100:
Group | Default Properties | Send Files
Which may be overridden by individual Group | Properties.
Ulf Meinhardt
But just another question about this.
Which option is commonly used for "format": UUencoded or MIME ?
And what should the user normally choose for Attachment placement:
- Inline MIME section
or
- Insert into text body?
Ulf
On Sun, 08 Nov 2009 11:35:22 +0000, Nick Spalding <spal...@iol.ie>
Nick Spalding
on Sun, 08 Nov 2009 13:49:15 +0100:
> Ahh, thank you.
>
> But just another question about this.
>
> Which option is commonly used for "format": UUencoded or MIME ?
For 1.93 I think the choice should be MIME for email and UUencoded for
usenet, though the latter is less usual these days than yEnc which 1.93
can't do.
> And what should the user normally choose for Attachment placement:
> - Inline MIME section
> or
> - Insert into text body?
My preference is for neither, make it just Attachment.
Stephen Wolstenholme
wrote:
>Nick Spalding
>Agent 5.0/32.1171 IE8
Nick,
Why do you have X-Newsreader: Forte Agent 6.00/32.1178 in your
headers?
Steve
--
Neural Planner Software Ltd www.NPSL1.com
Nick Spalding
<2uhdf5lk6mil6n5rg...@4ax.com>
on Sun, 08 Nov 2009 13:30:15 +0000:
> On Sun, 08 Nov 2009 13:14:07 +0000, Nick Spalding <spal...@iol.ie>
> wrote:
>
> >Nick Spalding
> >Agent 5.0/32.1171 IE8
>
> Nick,
>
> Why do you have X-Newsreader: Forte Agent 6.00/32.1178 in your
> headers?
NDA
--
Nick Spalding
Agent 5.0/32.1171 IE8
Stephen Wolstenholme
wrote:
>Stephen Wolstenholme wrote, in
><2uhdf5lk6mil6n5rg...@4ax.com>
> on Sun, 08 Nov 2009 13:30:15 +0000:
>
>> On Sun, 08 Nov 2009 13:14:07 +0000, Nick Spalding <spal...@iol.ie>
>> wrote:
>>
>> >Nick Spalding
>> >Agent 5.0/32.1171 IE8
>>
>> Nick,
>>
>> Why do you have X-Newsreader: Forte Agent 6.00/32.1178 in your
>> headers?
>
>NDA
But you have disclosed it by the header :)
Nick Spalding
<lkidf51ohkc8c06ug...@4ax.com>
on Sun, 08 Nov 2009 13:42:34 +0000:
> On Sun, 08 Nov 2009 13:36:56 +0000, Nick Spalding <spal...@iol.ie>
> wrote:
>
> >Stephen Wolstenholme wrote, in
> ><2uhdf5lk6mil6n5rg...@4ax.com>
> > on Sun, 08 Nov 2009 13:30:15 +0000:
> >
> >> On Sun, 08 Nov 2009 13:14:07 +0000, Nick Spalding <spal...@iol.ie>
> >> wrote:
> >>
> >> >Nick Spalding
> >> >Agent 5.0/32.1171 IE8
> >>
> >> Nick,
> >>
> >> Why do you have X-Newsreader: Forte Agent 6.00/32.1178 in your
> >> headers?
> >
> >NDA
>
> But you have disclosed it by the header :)
That much is permitted!
--
Nick Spalding
Agent 5.0/32.1171 IE8
Nick Spalding
on Sun, 08 Nov 2009 14:06:49 -0500:
> Nick Spalding wrote:
>
> > For 1.93 I think the choice should be MIME for email and UUencoded for
> > usenet, though the latter is less usual these days than yEnc which 1.93
> > can't do.
>
> It can too do yEnc. So can version 1.91.
>
> From the 1.91 help file:
>
> "Agent fully supports yEnc for both sending and receiving Usenet
> messages. At present Agent can receive email messages containing yEnc
> attachments, but does not support the sending of yEnc-formatted email.
> We chose to disable yEnc in email messages that you send, because yEnc
> has not been generally accepted as an encoding standard for email.
>
> There is nothing you have to do to configure Agent to receive yEnc
> messages. Agent automatically detects and decodes yEnc messages the
> same way that it handles uuencoded and MIME messages."
My mistake, I thought it came in with 2.0.