Home > Archive > SQL Anywhere database replication > August 2005 > Re: Exchange 2003 messages are corrupt









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Re: Exchange 2003 messages are corrupt
Reg Domaratzki

2005-08-03, 7:23 am

Jim, could you post a few message that weren't deleted as well?

--
Reg Domaratzki, Sybase iAnywhere Solutions
Certified SQL Anywhere Associate
Please reply only to the newsgroup

ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL and click "GO"


"Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
news:42ee8191$1@foru
ms-2-dub...
> Sybase SQL Remote Message Agent Version 6.0.3.2747
>
> When retrieving messages from a Microsoft Exchange Server 2003 POP3 server
> version 6.5.7226.0 dbremote is deleting all messages. Has anyone had this
> problem? A copy of some messages which were deleted are attached.
>
> Debug log file as follows:
> I. 07/13 18:27:58. +OK User successfully logged on.
> I. 07/13 18:27:58. STAT
> I. 07/13 18:27:58. +OK 16 105428
> I. 07/13 18:27:58. TOP 1 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 2 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 3 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 4 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 5 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 6 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 7 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 8 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 9 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 10 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 11 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 12 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 13 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 14 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 15 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. TOP 16 0
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 4
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 4
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 5
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 5
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 6
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 6
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 7
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 7
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 8
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 8
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 10
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 10
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 9
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 9
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 12
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 12
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 11
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 11
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 13
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 13
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 14
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 14
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 15
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 15
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. RETR 16
> I. 07/13 18:27:58. +OK
> E. 07/13 18:27:58. Deleting corrupt message
> I. 07/13 18:27:58. DELE 16
> I. 07/13 18:27:58. +OK
> I. 07/13 18:27:58. QUIT
> I. 07/13 18:27:58. +OK Microsoft Exchange Server 2003 POP3 server version
> 6.5.7226.0 signing off.
>
>
>
>



Jim Diaz

2005-08-03, 11:23 am

OK Getting them now
"Reg Domaratzki" <nospam.please@sympatico.ca> wrote in message
news:42f0b0f3@forums
-2-dub...
> Jim, could you post a few message that weren't deleted as well?
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Certified SQL Anywhere Associate
> Please reply only to the newsgroup
>
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL and click "GO"
>
>
> "Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
> news:42ee8191$1@foru
ms-2-dub...
>
>



Jim Diaz

2005-08-03, 1:24 pm

Reg:

I figured this out the problem isn't Exchange 2003 it was in another
server which messages were being routed through. One item to note is don't
look at the messages from a client it may hide the corruption. We ended up
looking at it with telnet.

We believe the problem is with "Content-Transfer-Encoding: quoted-printable"
this was changing the normal message start line to
=3D=3D=3D=3D=3DABCD=
3D=3D=3D=3DMessageSt
art01

an interesting link to this is http://www.freesoft.org/CIE/RFC/1521/6.htm

Our messages that are applying look like this
=====ABCD====Message
Start01
MEEwMTAwMDAwMDAwMDQz
RDg0MDAwMDAwMDAwQUZF
NTgxNTI4MDAwMDAwMEFG
RTU4NDAyRjAwMDAw
MDAwMDAwMVoAAABTDX/ aeJwLDXb09bUPMoAARzd
XUwsTAyM3e197AFecBkU
=
=====DCBA====Message
End

The corrupt messages look like this
=3D=3D=3D=3D=3DABCD=
3D=3D=3D=3DMessageSt
art01
MEEwMTAwMDAwMDAwMDQz
RDg0MDAwMDAwMDAwQUZF
NTg0MDJGMDAwMDAwMEFG
RTU4NDAyRjAwM=
DAw
MDAwMDAwMUYAAABLDbrb
eJwLDXb09bUHAAZnAcM=
3D
=3D=3D=3D=3D=3DDCBA=
3D=3D=3D=3DMessageEn
d

If you could verify that this type of change would cause dbRemote to
identify the message as corrupt I would appreciate it.

Thanks for everything

Jim



"Reg Domaratzki" <nospam.please@sympatico.ca> wrote in message
news:42f0b0f3@forums
-2-dub...
> Jim, could you post a few message that weren't deleted as well?
>
> --
> Reg Domaratzki, Sybase iAnywhere Solutions
> Certified SQL Anywhere Associate
> Please reply only to the newsgroup
>
> ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
> -> Choose SQL Anywhere Studio
> -> Set "Platform Preview" and "Time Frame" to ALL and click "GO"
>
>
> "Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
> news:42ee8191$1@foru
ms-2-dub...
>
>



Reg Domaratzki \(iAnywhere Solutions\)

2005-08-03, 1:24 pm

dbremote will definitely view messages starting with
" =3D=3D=3D=3D=3DABCD=
3D=3D=3D=3DMessageSt
art01" as corrupt.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
news:42f10377@forums
-1-dub...
> Reg:
>
> I figured this out the problem isn't Exchange 2003 it was in another
> server which messages were being routed through. One item to note is

don't

> look at the messages from a client it may hide the corruption. We ended

up
> looking at it with telnet.
>
> We believe the problem is with "Content-Transfer-Encoding:

quoted-printable"
> this was changing the normal message start line to
> =3D=3D=3D=3D=3DABCD=
3D=3D=3D=3DMessageSt
art01
>
> an interesting link to this is http://www.freesoft.org/CIE/RFC/1521/6.htm
>
> Our messages that are applying look like this
> =====ABCD====Message
Start01
>

MEEwMTAwMDAwMDAwMDQz
RDg0MDAwMDAwMDAwQUZF
NTgxNTI4MDAwMDAwMEFG
RTU4NDAyRjAwMDAw[col
or=darkred]
> MDAwMDAwMVoAAABTDX/ aeJwLDXb09bUPMoAARzd
XUwsTAyM3e197AFecBkU
=
> =====DCBA====Message
End
>
> The corrupt messages look like this
> =3D=3D=3D=3D=3DABCD=
3D=3D=3D=3DMessageSt
art01
> MEEwMTAwMDAwMDAwMDQz
RDg0MDAwMDAwMDAwQUZF
NTg0MDJGMDAwMDAwMEFG
RTU4NDAyRjAwM=
> DAw
> MDAwMDAwMUYAAABLDbrb
eJwLDXb09bUHAAZnAcM=
3D
> =3D=3D=3D=3D=3DDCBA=
3D=3D=3D=3DMessageEn
d
>
> If you could verify that this type of change would cause dbRemote to
> identify the message as corrupt I would appreciate it.
>
> Thanks for everything
>
> Jim
>
>
>
> "Reg Domaratzki" <nospam.please@sympatico.ca> wrote in message
> news:42f0b0f3@forums
-2-dub...
version
>
>



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com