[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
RE: POP3 connector (Floorplan 1.5 Device not updating)
------=_NextPart_000_0001_01C92B8E.FC4FAC00
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thanks for the information. I've just installed the POP3 connector and can
confirm that it's not you doing anything wrong, the connector does indeed
send the wrong line end characters. The connector was originally written by
Stuart Booth for the first version of the .Net Framework. Stuart is no
longer working on this but I do have the source code for this app. I'll
take
a look and see what I can find out. It's odd because this is not a
behaviour
that the other v1 framework app exhibit (if my memory serves me correctly).
The fix may either be a simple configuration change or something deeper. If
it's the latter then I'll probably take the opportunity to re-work this app
against the latest xAP Framework - that may take a little more time.
I'm interested to know how may people are using this app and if there are
any outstanding feature requests.
Also, can I dispel one urban myth: Viewer does not dissemble/re-assemble
messages on receive/re-transmit. It keeps all messages in the exact byte
binary format that it was received at the socket. Same is true for hub.
There was a version of viewer that did this but Stuart retired that years
ago (it was easy to spot because it also re-ordered the parameter lines in
each block).
From: xap_automation@xxxxxxx [mailto:xap_automation@xxxxxxx]
On Behalf Of PLefneski@xxxxxxx
Sent: 09 October 2008 05:12
To: xap_automation@xxxxxxx
Subject: Re: [xap_automation] Floorplan 1.5 Device not updating
Thanks for the response James,
I tried running the new hub and the problem persisted. I also played with
your idea regarding the line endings on my interface a bit but I still
could
not get it to work.
My Ocelot Message
78 61 70 2d 68 65 61 64 65 72 0d 0a 7b 0d 0a 76 xap-header { v
3d 31 32 0d 0a 68 6f 70 3d 31 0d 0a 75 69 64 3d =12 hop=1 uid=
46 46 31 32 33 34 30 30 0d 0a 63 6c 61 73 73 3d FF123400 class=
4f 63 65 6c 6f 74 2e 44 61 74 61 0d 0a 73 6f 75 Ocelot.Data sou
72 63 65 3d 52 6f 63 6b 65 74 2e 42 72 69 64 67 rce=Rocket.Bridg
65 2e 4f 6e 65 0a 0a 7d 0d 0a 53 65 72 69 61 6c e.One } Serial
2e 52 65 63 65 69 76 65 64 0d 0a 7b 0d 0a 50 6f .Received { Po
72 74 3d 31 0d 0a 44 61 74 61 3d 32 0a 7d 0a rt=1 Data=2 }
The POP3 Message
78 61 70 2d 68 65 61 64 65 72 0d 0a 7b 0d 0a 76 xap-header { v
3d 31 32 0d 0a 68 6f 70 3d 31 0d 0a 75 69 64 3d =12 hop=1 uid=
46 46 30 34 45 32 30 30 0d 0a 63 6c 61 73 73 3d FF04E200 class=
4d 61 69 6c 2e 49 6e 63 6f 6d 69 6e 67 0d 0a 73 Mail.Incoming s
6f 75 72 63 65 3d 4b 43 53 6f 66 74 2e 50 4f 50 ource=KCSoft.POP
33 2e 68 61 0d 0a 7d 0d 0a 53 74 61 74 75 73 0d 3.ha } Status
0a 7b 0d 0a 74 6f 74 61 6c 3d 31 34 0d 0a 7d 0d { total=14 }
0a
----- Original Message ----
From: James <james.traynor@xxxxxxx>
To: xap_automation@xxxxxxx
Sent: Tuesday, October 7, 2008 1:10:06 PM
Subject: Re: [xap_automation] Floorplan 1.5 Device not updating
Hi,
The only times i've seen this kind of thing happening is when the
application is sending xAP messages with incorrect line endings. They
should
be chr(10) but some apps end with CRLF. When Viewer picks up the message
the message is getting broken apart then rebuilt correctly, this is why
re-sent message work. Now in theory the intranet ocx, which is the xAP
receiver used in Floorplan, converts odd line endings but it's not abe to
correct them in this case. Two things to try. 1, Make sure you are using
one of the latest hubs from http://www.edjo.
<http://www.edjo.pwp.blueyonder.co.uk/edward/xAP/>
pwp.blueyonder.
co.uk/edward/ xAP/ on the PC running Floorplan 2, In viewer there is an
option to view the raw message in hex, this should show up what is
happening . If you could post the hex here it would help to see what is
happening.
James
On 7 Oct 2008, at 01:35, Paul Lefneski wrote:
Hi - I am relatively new to this so forgive me if this is a stupid
question.
I am trying to use Floorplan to display status information about my
house and control my household X10 devices. I have a number of BSC
devices on Floorplan for the X10 Devices and they are all working
properly. I also have a number of Raw devices displaying the current
weather from xAP Weather that work properly. I have 2 raw devices that
do not update properly on Floorplan when the a new message is sent. If
I go to xAP Message Viewer, select the message in question and press
the send message button a new message will be sent and Floorplan will
update properly. One of these is trying to get the total number of
emails from the xAP POP3 service. The other is via a homemade serial
interface to an Ocelot controller. I could understand the serial
message not working because I may have a poorly formed message or
something but the email service is an established service.
Does anyone know what could be causing this?
------=_NextPart_000_0001_01C92B8E.FC4FAC00
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: 7bit
<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml";
xmlns="http://www.w3.org/TR/REC-html40";>
<head>
<meta http-equiv=Content-Type content="text/html;
charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered
medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.left
{mso-style-name:left;}
span.bld
{mso-style-name:bld;}
p.ad, li.ad, div.ad
{mso-style-name:ad;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad1, li.ad1, div.ad1
{mso-style-name:ad1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad2, li.ad2, div.ad2
{mso-style-name:ad2;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad3, li.ad3, div.ad3
{mso-style-name:ad3;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:7.5pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";}
p.bld1, li.bld1, div.bld1
{mso-style-name:bld1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
p.replbq, li.replbq, div.replbq
{mso-style-name:replbq;
margin:3.0pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.left1, li.left1, div.left1
{mso-style-name:left1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ct, li.ct, div.ct
{mso-style-name:ct;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.cat, li.cat, div.cat
{mso-style-name:cat;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad4, li.ad4, div.ad4
{mso-style-name:ad4;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ad5, li.ad5, div.ad5
{mso-style-name:ad5;
mso-margin-top-alt:auto;
margin-right:0cm;
margin-bottom:7.5pt;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.left2, li.left2, div.left2
{mso-style-name:left2;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.ct1, li.ct1, div.ct1
{mso-style-name:ct1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
text-align:right;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:#FF7900;
font-weight:bold;}
p.cat1, li.cat1, div.cat1
{mso-style-name:cat1;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
p.ad6, li.ad6, div.ad6
{mso-style-name:ad6;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle41
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:33234543;
mso-list-template-ids:-242867566;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks for the information. I’ve just installed
the POP3
connector and can confirm that it’s not you doing anything wrong,
the
connector does indeed send the wrong line end characters. The connector was
originally written by Stuart Booth for the first version of the .Net
Framework.
Stuart is no longer working on this but I do have the source code for this
app.
I’ll take a look and see what I can find out. It’s odd
because this
is not a behaviour that the other v1 framework app exhibit (if my memory
serves
me correctly). The fix may either be a simple configuration change or
something
deeper. If it’s the latter then I’ll probably take the
opportunity to
re-work this app against the latest xAP Framework – that may take
a
little more time.<o:p></o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I’m interested to know how may people are using
this app
and if there are any outstanding feature
requests.<o:p></o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Also, can I dispel one urban myth: Viewer does not
dissemble/re-assemble
messages on receive/re-transmit. It keeps all messages in the exact byte
binary
format that it was received at the socket. Same is true for hub. There was
a version
of viewer that did this but Stuart retired that years ago (it was easy to
spot
because it also re-ordered the parameter lines in each
block).<o:p></o:p></span></p>
<p class=MsoNormal><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm
4.0pt'>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm
0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US
style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span
lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'>
xap_automation@xxxxxxx
[mailto:xap_automation@xxxxxxx]
<b>On Behalf Of </b>PLefneski@xxxxxxx<br>
<b>Sent:</b> 09 October 2008 05:12<br>
<b>To:</b> xap_automation@xxxxxxx<br>
<b>Subject:</b> Re: [xap_automation] Floorplan 1.5 Device not
updating<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div id=ygrp-mlmsg>
<div id=ygrp-msg>
<div id=ygrp-text>
<div>
<div>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thanks
for
the response James,<o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>I
tried
running the new hub and the problem persisted. I
also played
with your idea regarding the line endings on my interface
a bit but I
still could not get it to
work.<o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>My
Ocelot
Message<o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>78
61 70 2d
68 65 61 64 65 72 0d 0a 7b 0d 0a 76
xap-header
{ v<br>
3d 31 32 0d 0a 68 6f 70 3d 31 0d 0a 75 69 64
3d
=12 hop=1 uid=<br>
46 46 31 32 33 34 30 30 0d 0a 63 6c 61 73 73
3d
FF123400 class=<br>
4f 63 65 6c 6f 74 2e 44 61 74 61 0d 0a 73 6f
75
Ocelot.Data sou<br>
72 63 65 3d 52 6f 63 6b 65 74 2e 42 72 69 64
67
rce=Rocket.Bridg<br>
65 2e 4f 6e 65 0a 0a 7d 0d 0a 53 65 72 69 61
6c
e.One } Serial<br>
2e 52 65 63 65 69 76 65 64 0d 0a 7b 0d 0a 50
6f
.Received { Po<br>
72 74 3d 31 0d 0a 44 61 74 61 3d 32 0a 7d
0a rt=1 Data=2
} <o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The
POP3
Message<o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'>78
61 70 2d
68 65 61 64 65 72 0d 0a 7b 0d 0a 76
xap-header
{ v<br>
3d 31 32 0d 0a 68 6f 70 3d 31 0d 0a 75 69 64
3d
=12 hop=1 uid=<br>
46 46 30 34 45 32 30 30 0d 0a 63 6c 61 73 73
3d
FF04E200 class=<br>
4d 61 69 6c 2e 49 6e 63 6f 6d 69 6e 67 0d 0a
73
Mail.Incoming s<br>
6f 75 72 63 65 3d 4b 43 53 6f 66 74 2e 50 4f
50
ource=KCSoft.POP<br>
33 2e 68 61 0d 0a 7d 0d 0a 53 74 61 74 75 73
0d
3.ha } Status <br>
0a 7b 0d 0a 74 6f 74 61 6c 3d 31 34 0d 0a 7d
0d
{ total=14 } <br>
0a
<o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<p><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <o:p></o:p></span></p>
<div>
<p class=MsoNormal><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
</div>
<div>
<p class=MsoNormal><span
style='font-size:10.0pt;font-family:"Arial","sans-serif"'><o:p> </o:p></span></p>
<div style='border:none;border-left:solid #1010FF 1.5pt;padding:0cm 0cm
0cm 0cm'>
<p class=MsoNormal style='margin-bottom:12.0pt'>----- Original
Message ----<br>
From: James <james.traynor@xxxxxxx><br>
To: xap_automation@xxxxxxx<br>
Sent: Tuesday, October 7, 2008 1:10:06 PM<br>
Subject: Re: [xap_automation] Floorplan 1.5 Device not
updating<o:p></o:p></p>
<div id=ygrp-text>
<p>Hi, <o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>The only times i've seen this kind of thing
happening is
when the application is sending xAP messages with incorrect line endings.
They
should be chr(10) but some apps end with CRLF. When
Viewer picks up
the message the message is getting broken apart then rebuilt correctly,
this is
why re-sent message work. Now in theory the intranet ocx, which
is the
xAP receiver used in Floorplan, converts odd line endings but it's not abe
to
correct them in this case. Two things to try. 1, Make sure you
are using
one of the latest hubs from <a
href="http://www.edjo.pwp.blueyonder.co.uk/edward/xAP/";
target="_blank">http://www.edjo.
pwp.blueyonder. co.uk/edward/ xAP/</a> on the PC running Floorplan 2,
In viewer
there is an option to view the raw message in hex, this should
show up
what is happening . If you could post the hex here it would help
to see
what is happening.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>James<o:p></o:p></p>
<div>
<div>
<p class=MsoNormal>On 7 Oct 2008, at 01:35, Paul Lefneski
wrote:<o:p></o:p></p>
</div>
<p class=MsoNormal><br>
<br>
<o:p></o:p></p>
<div>
<div id=ygrp-mlmsg>
<div id=ygrp-msg>
<div id=ygrp-text>
<p style='margin-bottom:12.0pt;background:white'><span
style='font-size:10.0pt;
font-family:"Georgia","serif";color:black'>Hi - I am
relatively new to this so
forgive me if this is a stupid<span
class=apple-converted-space> </span><br>
question.<br>
<br>
I am trying to use Floorplan to display status information about my<span
class=apple-converted-space> </span><br>
house and control my household X10 devices. I have a number of BSC<span
class=apple-converted-space> </span><br>
devices on Floorplan for the X10 Devices and they are all working<span
class=apple-converted-space> </span><br>
properly. I also have a number of Raw devices displaying the
current<span
class=apple-converted-space> </span><br>
weather from xAP Weather that work properly. I have 2 raw devices
that<span
class=apple-converted-space> </span><br>
do not update properly on Floorplan when the a new message is sent.
If<span
class=apple-converted-space> </span><br>
I go to xAP Message Viewer, select the message in question and
press<span
class=apple-converted-space> </span><br>
the send message button a new message will be sent and Floorplan
will<span
class=apple-converted-space> </span><br>
update properly. One of these is trying to get the total number of<span
class=apple-converted-space> </span><br>
emails from the xAP POP3 service. The other is via a homemade
serial<span
class=apple-converted-space> </span><br>
interface to an Ocelot controller. I could understand the serial<span
class=apple-converted-space> </span><br>
message not working because I may have a poorly formed message or<span
class=apple-converted-space> </span><br>
something but the email service is an established service.<span
class=apple-converted-space> </span><br>
<br>
Does anyone know what could be causing
this?<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class=MsoNormal><span style='color:white'></span>
<o:p></o:p></p>
</div>
</div>
<span width="1" style="color:
white;"/>__._,_.___</span>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9674343/grpspId=1705007709/msgId=4119/stime=1223718595";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xap_automation/join;_ylc=X3oDMTJmYTRpaDNjBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyMjM3MTg1OTU-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xap_automation-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xap_automation-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xap_automation;_ylc=X3oDMTJkanV0dnNiBF9TAzk3NDc2NTkwBGdycElkAzk2NzQzNDMEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjIzNzE4NTk1";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xap_automation-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<span style="color: white;"/>__,_._,___</span>
</body>
</html>
------=_NextPart_000_0001_01C92B8E.FC4FAC00--
xAP_Automation Main Index |
xAP_Automation Thread Index |
xAP_Automation Home |
Archives Home
|