Hi

I have problem with sending .dbf file as attachment. Sendig file is ok, but 
when I receive this file, dbf file is corrupted. When I compare binary 
sended and received files I see that all 0a character are replaced with 
0d,0a sequence. I use 1.82.294 version of Asinet.


Could anyone help me?

Best regards,
Dariusz Bajszczak

Dariusz,

> I have problem with sending .dbf file as attachment. Sendig file is ok, but 
> when I receive this file, dbf file is corrupted. When I compare binary 
> sended and received files I see that all 0a character are replaced with 
> 0d,0a sequence. I use 1.82.294 version of Asinet.
> 
> 
> Could anyone help me?

Yes.  The attachment is being added with a mime-type of text/plain, and you
need to assert it as Application/Octet-stream.

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

Go ahead, jump. 100,000 lemmings can't be wrong.

Dariusz,

>I have problem with sending .dbf file as attachment. Sendig file is ok, but 
>when I receive this file, dbf file is corrupted. When I compare binary 
>sended and received files I see that all 0a character are replaced with 
>0d,0a sequence. I use 1.82.294 version of Asinet.

This is caused by the wrong QP (quoted-printable) encoding of ASINET, 
combined with the fact that the encoding for "unknown" files (with 
unrecognized extensions, like "dbf") defaults to QP. Those problems are 
covered by several PDRs, including 109-5363. The result is that most binary 
files (as well as many text files) will be corrupted, when they are attached 
to an email with ASINET.

The main solution is to upgrade to Xbase++ 1.82.306, using the freely 
available PFL from Alaska. This PFL does not completely fix the QP problems, 
but replaces the default encoding for unknown files with the more 
appropriate base64 encoding (which has also been fixed with that PFL).

If you want to stay with 1.82.294, you can either change the extension of 
your file to something like ZIP or actually zip the file. Otherwise, only 
the PFL will give you uncorrupted database file attachments.

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas@Aerospace-History.net
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---

Andreas and Phil,
this problem is NOT at all specific to ASINET!
It happens with many normal mailers as well! Whenever my customers want to 
send me one of their dbf (most of them are using Outlook), I always make 
sure they are ziping it first!

Regards,
Martin

Martin,

>this problem is NOT at all specific to ASINET!

Yes, it is. ASINET does not allow you, the programmer, to select what type 
of encoding you want to use for an attached file -- it decides that for you. 
Other (email) programming tools/add-ons, like See4XB, do not have such 
unnecessary restrictions and limitations.

>It happens with many normal mailers as well! Whenever my customers want to 
>send me one of their dbf (most of them are using Outlook), I always make 
>sure they are ziping it first!

You can't really compare a (poorly written Microsoft) email application, 
like Outlook or Outlook Express, with a programming tool! Those are two 
completely different things, IMNSHO.

-- Andreas

---                                                                      ---
  Andreas Gehrs-Pahl              E-Mail: GPahl@CharterMI.net
  415 Gute Street                     or: Andreas@DDPSoftware.com
  Owosso, MI 48867-4410               or: Andreas@Aerospace-History.net
  Tel: (989) 723-9927           Web Site: http://www.Aerospace-History.net
---                                                                      ---

Martin Altmann wrote:

> this problem is NOT at all specific to ASINET!
> It happens with many normal mailers as well! Whenever my customers want to 
> send me one of their dbf (most of them are using Outlook), I always make 
> sure they are ziping it first!

Well, this only proves that Outlook (or the programmer at M$) has the same
problem... 

Thomas Braun

Hi,

     As Phil says the data shouild be asserted as
     Content-Type : Application / Octet-Stream with the option to let the
user save the data to a chosen file name.
     This then is pure binary representation  of the dbf data, rather than
Content-Type : Text / Plain which is for ascii text.

Regards Mark

"Dariusz Bajszczak" <b_darek@poczta.onet.pl> wrote in message
news:qZAQz9NvEHA.6512@S15147418...
> Hi
>
> I have problem with sending .dbf file as attachment. Sendig file is ok,
but
> when I receive this file, dbf file is corrupted. When I compare binary
> sended and received files I see that all 0a character are replaced with
> 0d,0a sequence. I use 1.82.294 version of Asinet.
>
>
> Could anyone help me?
>
> Best regards,
> Dariusz Bajszczak
>
>
>
>

Thank's all for reply.
After installing  ASInet PFL306 everything is ok.

Best regards,
Dariusz Bajszczak

Uytkownik "Dariusz Bajszczak" <b_darek@poczta.onet.pl> napisa w wiadomoci 
news:qZAQz9NvEHA.6512@S15147418...
> Hi
>
> I have problem with sending .dbf file as attachment. Sendig file is ok, 
> but when I receive this file, dbf file is corrupted. When I compare binary 
> sended and received files I see that all 0a character are replaced with 
> 0d,0a sequence. I use 1.82.294 version of Asinet.
>
>
> Could anyone help me?
>
> Best regards,
> Dariusz Bajszczak
>
>
>
>