<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1056667503;
mso-list-type:hybrid;
mso-list-template-ids:-1734062366 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</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 lang=EN-US link=blue vlink=blue><DIV>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I looked at that and in general it should
work but I had two thoughts:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<ol style='margin-top:0in' start=1 type=1>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo1'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>host()
matches the hostname field in the message so if that isn’t
configured then it will be missed. I suppose that’s something that
should be fixed on a case by case basis though.<o:p></o:p></span></font></li>
<li class=MsoNormal style='color:navy;mso-list:l0 level1 lfo1'><font size=2
color=navy face=Arial><span style='font-size:10.0pt;font-family:Arial'>I’d
prefer to use a wildcard for the netmask but there are other non-cisco
devices on the same subnet.<o:p></o:p></span></font></li>
</ol>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
syslog-ng-bounces@lists.balabit.hu [mailto:syslog-ng-bounces@lists.balabit.hu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Clayton Dukes<br>
<b><span style='font-weight:bold'>Sent:</span></b> Friday, October 30, 2009
7:22 AM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">Syslog-ng
users' and developers' mailing list</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [syslog-ng] Syslog-NG
interpreting Cisco message'count'numberas$Program</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>I'm not a syslog-ng expert, but:<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>netmask(192.168.10.9)<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>You can use wildcards (or regex) here, also, shouldn't that be host and
not netmask?<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br>
<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Fri, Oct 30, 2009 at 12:14 AM, Patrick Smith <<a
href="mailto:patrick@paypros.com">patrick@paypros.com</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Now that my mysql pipe issues are sorted out thought I'd post back with
my hackaround for this issue. I did find an old post with an explanation
as to where the numbers come from: <a
href="https://lists.balabit.hu/pipermail/syslog-ng/2007-December/011057.html"
target="_blank">https://lists.balabit.hu/pipermail/syslog-ng/2007-December/011057.html</a>
So, trusting that is true, they are event numbers, not count or sequence
numbers. I haven't found any documentation on event numbers yet, maybe
it's just another term for sequence numbers, but if that were the case I should
have been able to turn them off.<br>
<br>
Don't have a lot of time to look for a better fix so for now I just did the
following, if it helps anyone.<br>
<br>
# Local file destination sorted by host, program<br>
destination d_localfiles {<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
file("/var/log/syslog-ng/$HOST/$PROGRAM-$YEAR-$MONTH-$DAY.log");<br>
};<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'># Local file destination sorted by host, program (currently only
used by Cisco switches)<br>
destination d_localfiles-noProgram {<br>
file("/var/log/syslog-ng/$HOST/$YEAR-$MONTH-$DAY.log");<br>
};<br>
<br>
# Filter listing all cisco switches (could be a pain to manage in large
environments)<br>
filter f_ciscosw { netmask(192.168.10.8) or<br>
netmask(192.168.10.9) or<br>
netmask(192.168.10.10) or<br>
netmask(192.168.10.11) or<br>
netmask(192.168.10.12) or<br>
netmask(192.168.10.13) or<br>
netmask(192.168.10.12) or<br>
netmask(192.168.10.24); };<br>
<br>
# Filter for all other hosts<br>
filter f_allsystem {
facility(local0,local1,local2,local3,local4,local5,local6,local7) and not
filter(f_ciscosw); };<br>
<br>
# Pipe to mysql, putting Cisco switch messages through same pipe seems to work
fine. i.e.does not write the event number in the program field. *
Pipe is the default used in the logzilla 2.9.9n wiki install guide)<br>
log { source(s_remote); filter(f_allsystem); destination(d_mysql); };<br>
log { source(s_remote); filter(f_ciscosw); destination(d_mysql); };<br>
<br>
# Log declarations, one for Cisco switches, the other for everything else.<br>
log { source(s_remote); filter(f_allsystem); destination(d_localfiles); };<br>
log { source(s_remote); filter(f_ciscosw); destination(d_localfiles-noProgram);
};<br>
<br>
Cheers.<br>
<br>
________________________________<br>
<br>
From: <a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>
on behalf of Clayton Dukes<br>
Sent: Wed 10/21/2009 3:06 PM<o:p></o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>To: <st1:PersonName w:st="on">Syslog-ng users' and developers' mailing
list</st1:PersonName><br>
Subject: Re: [syslog-ng] Syslog-NG interpreting Cisco message'count'numberas
$Program<br>
<br>
<br>
<br>
Not that this helps, but your timestamps aren't configured on that switch :-)<br>
If you're using the latest version of php-syslog-ng (2.9.9x) then you<br>
can tell it to skip showing the sequence numbers in the config.php<br>
file.<br>
Also, the new version allows you to rewrite fields in the <a
href="http://db_insert.pl/" target="_blank">db_insert.pl</a><br>
script so you could leave them off alltogether if you wanted to.<br>
If you need help with php-syslog-ng just let me know - it's my project :-)<br>
<br>
<br>
On Wed, Oct 21, 2009 at 5:52 PM, Patrick Smith <<a
href="mailto:patrick@paypros.com">patrick@paypros.com</a>> wrote:<br>
> If I can't stop the switches from sending it then I'll just make
additional source/destination statement to deal with them and leave the
$program part out. I do find it handy when searching through logs
directly on the filesystem to have them broken down by origin (snmp or
wherever). I haven't started piping them to my new php-syslog-ng install
but I'm sure in the present format I'd flood the Program fields with those
numbers in the current state.<br>
><br>
> I am sure the sequence/count numbers are coming from the switches.
Tcpdump shows a Msg number which matches the number prepended on the
file.<br>
><br>
> tcpdump -nvv host 2960switch04<br>
> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96
bytes<br>
> 14:44:32.013692 IP (tos 0x0, ttl 254, id 69, offset 0, flags [none],
proto: UDP (17), length: 131) <src_ip>.57127 > <syslog-ng host
ip>.syslog: SYSLOG, length: 103<br>
> Facility local7 (23), Severity notice (5)<br>
> Msg: 119: 1d04h: %LINK-5-CHANGED: Interface
GigabitEth[|syslog]<br>
><br>
> Results in a file on the syslog-ng server called 119-2009-10-21.log<br>
><br>
> Thanks for your time,<br>
> Patrick<br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>
[mailto:<a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>]
On Behalf Of Clayton Dukes<br>
> Sent: Wednesday, October 21, 2009 2:30 PM<br>
> To: <st1:PersonName w:st="on">Syslog-ng users' and developers' mailing
list</st1:PersonName><br>
> Subject: Re: [syslog-ng] Syslog-NG interpreting Cisco message
'count'numberas $Program<br>
><br>
> Hmm, then I'm not sure...maybe one of the other guru's on here will<br>
> have some input :-)<br>
> Have you tried not using the program field or do you really need it?<br>
><br>
><br>
> On Wed, Oct 21, 2009 at 5:06 PM, Patrick Smith <<a
href="mailto:patrick@paypros.com">patrick@paypros.com</a>> wrote:<br>
>> Thought that might be it but doesn't seem to be. The sequence
number is not present in the logs sent to the console or the buffer and not
present when I open the files that are created on the syslog-ng side.
They are only present in the filename that gets created for logs coming
from the Cisco switches.<br>
>><br>
>> I tried the 'no service sequence-numbers' on one of the access
switches to be sure and did a shut/no shut on an unused port. Still
logged the same way on the syslog-ng server.<br>
>><br>
>> Patrick Smith | Systems Administrator | Payment Processing, Inc.<br>
>> 604.609.0619 x7023 ofc | 604.609.0619 fx<br>
>> <a href="http://www.paypros.com/" target="_blank">www.paypros.com</a><br>
>><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>
[mailto:<a href="mailto:syslog-ng-bounces@lists.balabit.hu">syslog-ng-bounces@lists.balabit.hu</a>]
On Behalf Of Clayton Dukes<br>
>> Sent: Wednesday, October 21, 2009 1:08 PM<br>
>> To: <st1:PersonName w:st="on">Syslog-ng users' and developers' mailing
list</st1:PersonName><br>
>> Subject: Re: [syslog-ng] Syslog-NG interpreting Cisco message 'count'
numberas $Program<br>
>><br>
>> Those are sequence numbers - you can disable them on the switch by<br>
>> typing "no service sequence-numbers" in global config mode.<br>
>><br>
>><br>
>> On Wed, Oct 21, 2009 at 4:01 PM, Patrick Smith <<a
href="mailto:patrick@paypros.com">patrick@paypros.com</a>> wrote:<br>
>>> Hi all, wondering if anyone is familiar with this issue.
Have several Cisco<br>
>>> switches logging to a syslog-ng server. The syslog-ng server
creates a new<br>
>>> file for every message as it is interpreting the 'count' item
added by the<br>
>>> switch as the $program. My configs as follows to demonstrate
what I mean:<br>
>>><br>
>>><br>
>>><br>
>>> Syslog-ng.conf:<br>
>>><br>
>>><br>
>>><br>
>>> destination d_all {<br>
>>><br>
>>> file("/var/log/syslog-ng/$HOST/$PROGRAM-$YEAR-$MONTH-$DAY.log");<br>
>>><br>
>>> };<br>
>>><br>
>>><br>
>>><br>
>>> This has always worked for me before and creates logs for each
host with the<br>
>>> program prefixed (e.g. snmp-date..., ssl_access_log-date...)<br>
>>><br>
>>><br>
>>><br>
>>> But for Cisco switches it writes a new logfile for every message,
with the<br>
>>> Cisco message number (i.e. log count #) prepended. E.g., for
a 6509 switch:<br>
>>><br>
>>><br>
>>><br>
>>> -rw-r--r-- 1 syslog-ng wheel 165 Oct 21 11:51
1655156-2009-10-21.log<br>
>>><br>
>>> -rw-r--r-- 1 syslog-ng wheel 168 Oct 21 11:51
1655157-2009-10-21.log<br>
>>><br>
>>> -rw-r--r-- 1 syslog-ng wheel 147 Oct 21 11:51
1655158-2009-10-21.log<br>
>>><br>
>>> -rw-r--r-- 1 syslog-ng wheel 150 Oct 21 11:51
1655159-2009-10-21.log<br>
>>><br>
>>> -rw-r--r-- 1 syslog-ng wheel 154 Oct 21 11:52 1655160-2009-10-21.log<br>
>>><br>
>>> * where 16551xx is the count of the log message on the switch<br>
>>><br>
>>><br>
>>><br>
>>> And each of those files contains one log message, e.g.<br>
>>><br>
>>><br>
>>><br>
>>> syslog-ng # cat 1655156-2009-10-21.log<br>
>>><br>
>>> Oct 21 11:51:15 6509switch1 1655156: Oct 21 18:51:14.922:
%LINK-5-CHANGED:<br>
>>> Interface GigabitEthernet3/35, changed state to administratively
down<br>
>>><br>
>>><br>
>>><br>
>>> For reference the logging on the switches are set as:<br>
>>><br>
>>> 6509s:<br>
>>><br>
>>> service timestamps log datetime msec<br>
>>><br>
>>> logging buffered 20000 debugging<br>
>>><br>
>>> logging rate-limit 1000<br>
>>><br>
>>> log-adjacency-changes<br>
>>><br>
>>> logging <syslog host IP><br>
>>><br>
>>> logging synchronous<br>
>>><br>
>>><br>
>>><br>
>>> 2960s:<br>
>>><br>
>>> service timestamps log uptime<br>
>>><br>
>>> logging buffered 20000<br>
>>><br>
>>> logging <syslog host IP><br>
>>><br>
>>> logging synchronous<br>
>>><br>
>>><br>
>>><br>
>>> I'm thinking I could have a separate destination statement to
properly deal<br>
>>> with these but I'm wondering if there's any other steps I can take
to<br>
>>> mitigate it. I have several Cisco firewalls logging to
syslog-ng and they<br>
>>> do not have the same issue.<br>
>>><br>
>>><br>
>>><br>
>>> Thanks for any help.<br>
>>><br>
>>><br>
>>><br>
>>> IMPORTANT NOTICE<br>
>>><br>
>>> THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any
attachments are<br>
>>> proprietary and confidential information intended only for the use
of the<br>
>>> recipient(s) named above. If you are not the intended recipient,
you may not<br>
>>> print, distribute, or copy this message or any attachments. If you
have<br>
>>> received this communication in error, please notify the sender by
return<br>
>>> e-mail and delete this message and any attachments from your
computer. Learn<br>
>>> more about Payment Processing's services at <a
href="http://www.paypros.com/" target="_blank">www.paypros.com</a>.<br>
>>> ______________________________________________________________________________<br>
>>> Member info: <a
href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
>>> Documentation:<br>
>>> <a
href="http://www.balabit.com/support/documentation/?product=syslog-ng"
target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
>>> FAQ: <a href="http://www.campin.net/syslog-ng/faq.html"
target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
>>><br>
>>><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> ______________________________________________________________<br>
>><br>
>> Clayton Dukes<br>
>> ______________________________________________________________<br>
>>
______________________________________________________________________________<br>
>> Member info: <a
href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
>> Documentation: <a
href="http://www.balabit.com/support/documentation/?product=syslog-ng"
target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
>> FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
>> IMPORTANT NOTICE<br>
>><br>
>> THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments
are proprietary and confidential information intended only for the use of the
recipient(s) named above. If you are not the intended recipient, you may not
print, distribute, or copy this message or any attachments. If you have
received this communication in error, please notify the sender by return e-mail
and delete this message and any attachments from your computer. Learn more
about Payment Processing's services at <a href="http://www.paypros.com/"
target="_blank">www.paypros.com</a>.<br>
>> ______________________________________________________________________________<br>
>> Member info: <a
href="https://lists.balabit.hu/mailman/listinfo/syslog-ng" target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
>> Documentation: <a
href="http://www.balabit.com/support/documentation/?product=syslog-ng"
target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
>> FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
>><br>
>><br>
><br>
><br>
><br>
> --<br>
> ______________________________________________________________<br>
><br>
> Clayton Dukes<br>
> ______________________________________________________________<br>
>
______________________________________________________________________________<br>
> Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng"
target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
> Documentation: <a
href="http://www.balabit.com/support/documentation/?product=syslog-ng"
target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
> FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
> IMPORTANT NOTICE<br>
><br>
> THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are
proprietary and confidential information intended only for the use of the
recipient(s) named above. If you are not the intended recipient, you may not
print, distribute, or copy this message or any attachments. If you have
received this communication in error, please notify the sender by return e-mail
and delete this message and any attachments from your computer. Learn more
about Payment Processing's services at <a href="http://www.paypros.com/"
target="_blank">www.paypros.com</a>.<br>
> ______________________________________________________________________________<br>
> Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng"
target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
> Documentation: <a
href="http://www.balabit.com/support/documentation/?product=syslog-ng"
target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
> FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
><br>
><br>
<br>
<br>
<br>
--<br>
______________________________________________________________<br>
<br>
Clayton Dukes<br>
______________________________________________________________<br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng"
target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a
href="http://www.balabit.com/support/documentation/?product=syslog-ng"
target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
IMPORTANT NOTICE<br>
<br>
THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are
proprietary and confidential information intended only for the use of the
recipient(s) named above. If you are not the intended recipient, you may not
print, distribute, or copy this message or any attachments. If you have
received this communication in error, please notify the sender by return e-mail
and delete this message and any attachments from your computer. Learn more
about Payment Processing's services at <a href="http://www.paypros.com/"
target="_blank">www.paypros.com</a>.<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><br>
______________________________________________________________________________<br>
Member info: <a href="https://lists.balabit.hu/mailman/listinfo/syslog-ng"
target="_blank">https://lists.balabit.hu/mailman/listinfo/syslog-ng</a><br>
Documentation: <a
href="http://www.balabit.com/support/documentation/?product=syslog-ng"
target="_blank">http://www.balabit.com/support/documentation/?product=syslog-ng</a><br>
FAQ: <a href="http://www.campin.net/syslog-ng/faq.html" target="_blank">http://www.campin.net/syslog-ng/faq.html</a><br>
<br>
<o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br clear=all>
<br>
-- <br>
______________________________________________________________ <br>
<br>
Clayton Dukes<br>
______________________________________________________________<o:p></o:p></span></font></p>
</div>
</DIV>
<DIV style="font-family:Courier New; font-size:9pt">IMPORTANT NOTICE<br> <br>THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. Learn more about Payment Processing's services at www.paypros.com.</DIV></BODY></HTML>