Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Prevent spam in exchange

Network Sharing , TCP/IP, Internet, Wireless, Exchange, IIS, ISA and Print

Prevent spam in exchange

Postby guest » Sun Oct 19, 2008 9:26 pm

Some of our users need to enable relay in our Exchange server to send email from one application. So we enabled relay for internal IP range only.
As my previous post, we got over 100,000 NDR in the queues.

1. Can spammers take advantage of the enabled internal relay to send spam?
2. If one of our computers is used to send spam, how do you find it? Any tools?

From your problem description, I understand that you have configured Exchange 2003 server to allow an application to relay e-mails. Then, you noticed over 100,000 NDR messages are stuck in the queues. You would like to know:

1. You would like to know how to remove all NDR messages without going to each queue to remove them?
2. Can spam sender relay spam e-mails through your Exchange server because internal relay is enabled?
3. If an internal client computer is used to send spam e-mails, how can you locate this client computer?

If my understanding is not correct, please feel free to let me know.

Before we go further, I would like to whether the sender of the spam e-mails is an internal or external sender. Are the senders of the spam e-mails different or the spam e-mails are sent from the same sender?

To troubleshoot this issue, I suggest you perform the following steps to, remove NDR messages stuck in the queue:

Step 1: Remove NDR messages. Please refer to the steps in the following KB to clean up queues:

In Exchange Server 2003 or in Exchange 2000 Server, the Exchange Server queues are filled with many non-delivery reports from the postmaster account because of a reverse non-delivery report attack
http://support.microsoft.com/kb/909005

Note: Please perform the steps in the "Step 3: Clean up the Exchange Server queues" section.

By performing those steps, all spam e-mails will be routed to a single queue. Then, you can remove all NDR messages from this queue rather than going to different queues to remove NDR messages.

After that, please proceed with the following steps to disable Open Relay and enable related anti-spam filters:

Step 2: Disable Open Relay
======================

[Check SMTP virtual server]

1. Click Start, click All Programs, click Microsoft Exchange, and then click System Manager.
2. Expand Servers, expand Servername, expand Protocols, and then expand SMTP.
3. Right-click Default SMTP Virtual Server and then click Properties.
4. Click the Access tab.
5. Click the Relay button at the bottom.
6. Modify the following settings:

- Select Only the list below.
- Ensure only the IP address of the internal application is listed.
- Make sure that "Allow all computers which successfully authenticate to relay, regardless of the list above" is selected. Click OK.

7. Click OK.

[Check SMTP connector]

1. In the Exchange System Manager, expand Connectors, and then locate the SMTP Connector.
2. Right-click the SMTP connector, and then click Properties.
3. Click the Address Space tab.
4. Modify the following settings:

- Type: SMTP
- Address: *
- Cost: 1
- The Connector Scope is Entire Organization.
- "Allow messages to be routed to these domains" is cleared (not selected).

5. Click OK.

After that, please restart the SMTP service.

Step 3: Configure Sender and Recipient Filter
===================================
1. Start the Exchange System Manager tool.
2. Expand Global Settings, right-click Message Delivery, and then click Properties.
3. Click the Recipient Filtering tab, click to select the "Filter recipients who are not in the Directory" check box.
4. Click the Sender Filtering tab, and mark the check box next to "Filter messages with blank sender".
5. Expand Servers, expand your computer, expand Protocols, expand SMTP, right-click Default SMTP Virtual Server, and then click Properties.
6. On the General tab, click Advanced.
7. Click Edit, click to select the Apply Recipient Filter check box, and then click OK three times.
8. Restart the SMTP service.

As to your second question, I would like to let you know that if relay is configured correctly, external spam sender will not be able to take advantage of your Exchange server to relay spam e-mails.

As to your third question, we can analyze the spam e-mails in the queue, SMTP log or Message Tracking information to see whether the spam e-mails are submitted from an internal client computer. At this stage, I suggest you first perform the above steps to clean up queues and verify the configurations.
Last edited by guest on Wed Dec 31, 2008 2:38 pm, edited 1 time in total.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Postby guest » Sun Oct 19, 2008 9:26 pm

Before I posted, I have checked this article http://support.microsoft.com/kb/909005/. However, I can't follow this steps:

1. Start the Server Management tool.
2. Expand Advanced Management, expand the Exchange organization, and then click Connectors.

Where is the Server Management tool?
The steps included in this KB is incorrect as those steps are for Windows
Small Business Server 2003. The Server Management tool is the main snap-in
for managing SBS 2003.

The correct steps to locate the Connectors container on Exchange 2003
server should be:

1. Open Exchange System Manager.
2. Navigate to the following object:

Administrative Groups -> <AG_name> -> Routing Groups -> <RG_name> ->
Connectors

Then, please proceed with other steps to clean up the queue.

Also, thank you for your feedback. I will make a summary and forward it to
the relevant team to modify this KB article.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Postby guest » Sun Oct 19, 2008 9:27 pm

Thank you for the email. Following your instruction, I can delete the queues. After checking each queue, I found only some NDR is postmaster@domain.name, but most of queues (over 90%) are from sender name united nation (info@unitednation.tk). Where does this sender come from?

By the way, we did setup the Open relay and Recipient Filter as your suggestions.

I understand that the e-mails stuck in the queue can be deleted. When
checking the queue, you noticed that some NDR messages are sent from
postmaster@domain.com, while most NDR messages are sent from
info@unitednation.tk

At this point, I would like to confirm whether the e-mails submitted by
info@unitednation.tk is sent to an external or internal recipient.

I assume those e-mails are sent to external recipients. If this is the
case, I believe Open Relay was enabled and the external sender
(info@unitednation.tk) was attempting to relay e-mails through your
Exchange server.

Based on the current situation, I suggest you enable SMTP log via the
following steps and then keep monitoring the queue to see whether the issue
still occurs:

Enable SMTP logging
==================
Note: Please enable SMTP logging on the Exchange 2003 front-end server.

1. Please open Exchange System Manager.
2. Right click on "Default SMTP Virtual Server" and click Properties.
3. On the General tab, please check the option "Enable logging".
4. Select W3C Extended Log File Format from the list below.
5. Click the Properties button. In the General tab, please confirm the
following settings:

- Check the option Daily
- Check the option "Use local time for file naming and rollover"
- Confirm the setting for "Log file directory" to be
"C:\Windows\System32\LogFiles"

6. Switch to the Advanced tab, please mark the check box next to all
options.
7. Click OK twice.

Meanwhile, please let me know the following info so that I am able to
perform test from my side to verify whether Open Relay is completely
disabled:

- FQDN of the Exchange server
- name of the SMTP domain hosted by the Exchange server
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Postby guest » Sun Oct 19, 2008 9:39 pm

1. I have enabled the SMTP log yesterday. But since I disabled all open relay, we don't have suspect sender. I will send the log to you when I have one.
2. As I mentioned before, we enabled open replay allow the LAN IP addresses only. Is it possible one of our computers sent those emails? The problem is I have disabled all open relay so that I don't see info@unitednation.tk sender any more.
3. Our OWA server FQDN is cbgowa.chicagotech.net and SMTP domain name is cbgnet.chicagotech.net.

I understand that currently, no e-mails sent from problematic sender in the
queue.

Also, I have run a test from my side and I believe Open Relay is disabled.

As to your second question, I would like to let you know that it is
possible that the spam e-mails are submitted by the internal client
computer. However, we still need to check Message Tracking information,
SMTP log and Application Log to confirm.

At this point, please take your time to monitor this issue. If it occurs
again, please send the SMTP log to me.

According to your response, I understand that you have found that some e-mails with non-existent senders in the outbound queue.

I have checked the SMTP log on the front-end and back-end servers. I believe the SMTP logging has not been enabled correctly, as the sender and recipient's e-mail address has not been logged in the SMTP. Therefore, I am not able to perform a search to locate the relevant SMTP entries for the problematic e-mails.

Based on the current situation, I suggest you perform the following steps to enable SMTP logging:

Enable SMTP logging
=================
1. Please open Exchange System Manager.
2. Right click on "Default SMTP Virtual Server" and click Properties.
3. On the General tab, please check the option "Enable logging".
4. Select W3C Extended Log File Format from the list below.
5. Click the Properties button. In the General tab, please confirm the following settings:

- Check the option Daily
- Check the option "Use local time for file naming and rollover"
- Confirm the setting for "Log file directory" to be "C:\Windows\System32\LogFiles"

6. Switch to the Advanced tab, please mark the check box next to all options.
7. Click OK twice.

After that, please clear the e-mails with non-existent sender.

I checked the SMTP log and search the e-mail address
wbigprckdi@boltswitch.com. I noticed that an external server with the IP
address 79.24.43.83 sent an e-mail as from wbigprckdi@boltswitch.com to
school@chicagotech.net.

Therefore, please verify whether any internal user has the e-mail address
school@chicagotech.net. Also, please check whether the user
account who has the e-mail address school@chicagotech.net has
been configured to forward/redirect e-mail to an external contact.

From the SMTP log, I did not find the corresponding entries which indicates
that the Exchange server attempted to send e-mails to an external recipient
from wbigprckdi@boltswitch.com.

Also, I have performed a telnet against the server with the IP address
79.24.43.83. However, the connection cannot be established.

Meanwhile, I suggest you perform the following steps to collect the Message
Tracking information:

Enable Message Tracking Center
==========================
Please enable Message Tracking Center via the steps included in the
following article:

How to Enable Message Tracking Center on a Server
http://technet.microsoft.com/en-us/libr ... 24212.aspx

After enabling Message Tracking Center, please wait until the issue occurs
again and then proceed with the following steps to track the message:

Track the message:
===============
a. Open Exchange System Manager.
b. Click Tools-> Message Tracking Center.
c. In the right pane, enter the non-existent sender in the Sender box.
d. Click Server, enter the FQDN of the server, click Check Names and click
OK.
e. Enter the recipient's e-mail address in the Recipients box.
f. Set the time correctly.
g. Click Find Now.
h. In the bottom pane, the e-mail just sent appears.
i. Click it and the Message History window will pop up.
i. Take a screenshot of the Message History.

Take a screenshot
===============
a. Leave the Message History on the screen and press the Print Screen key
(PrtScn) on the keyboard.
b. Click "Start", click "Run", type "mspaint" (without quotation marks),
and click "OK".
c. In the Paint program, click the "Edit" menu, click "Paste", click the
"File" menu, and click "Save".
d. The "Save As" dialogue box will appear. Type a file name in the "File
name:" box, for example: "screenshot".
e. Make sure "JPEG (*.JPG;*.JPEG;*.JPE;*.JFIF)" is selected in the "Save as
type" box, and then click "Save".

I understand that no mail forwarding has been configured on
"school" user account.

Also, I noticed that you have submitted another post regarding the abnormal
options on the Properties of the "school" user account. I believe
two issues can be related.

Therefore, in this situation, I suggest you first dump the Active Directory
info of this user account and another user account whose Properties is
normal and send it me so that I am able to perform further analysis.

Based on my experience, I believe some Exchange attributes of this user
account is corrupted. Therefore, we may need to remove the Exchange
Attributes for this user account and mail-enable this user account again.

In the meantime, if you notice that the issue re-occurs, please collect the
Message Tracking and the SMTP log again.

According to your response, I understand that "school" attempted
to send outgoing e-mails. However, based on the screenshot of the "Message
Properties", the problematic e-mail is sent from "Mailer-Daemon" to
"school".

I have also checked SMTP log collected on the front-end server, and I found
MAILER-DAEMON@chicagotech.net is trying to send e-mails to internal
users such as bkirschn@chicagotech.net or MPlunkett@chicagotech.net
and etc.

Therefore, I would like to confirmed you have used any Mailer-Daemon
service or install any Mailer-Daemon related software on the client
computers.

Also, from the SMTP log, I noticed that some unknown external senders (e.g.
abdullah.zaki@k12.dc.us) are attempting to send e-mails to
"school". This kind of behavior occurs if the e-mail address of
"school" is captured by the spam senders when "school"
sends Internet e-mails excessively.

In this case, I suggest you change the e-mail address of "school"
as school.gardending@domain.net.

According the AD info of "school", I found the following problems:

- homeMDB attribute has not been set.
- there is an invalid entry in homeMTA attribute.

Therefore, I suggest perform the following steps to address the above
issues:

- The value of the homeMDB attribute should be the Distinguished Name of
the back-end server where the mailbox of "school" exists. You may
set the homeMDB attribute of "school" with the value of the
homeMDB attribute of a normal user.

- Please also set the homeMTA attribute of "school" with the value
of the homeMTA attribute of a normal user.

You are right. The school is recipient. I am confused.

1. We don't have MAILER-DAEMON@domain.net account. From the log, can you
tell which computer or IP use MAILER-DAEMON@domain.net to send email?

2. Why those emails queued in outbound cbgnt.domain.net. cbgnt was our old
NT 4 server. We have removed it from the network for many years. If we
don't have this server, where do those emails go?

3. We have deleted the school account. since then we don't have
many emails in queues. The question is if the school didn't send
email to outbound, who did. Why our IP address has a poor reputation?

Thank you for your update.

Actually, the e-mail sent from MAILER-DAEMON@domain.net is first received
by the front-end server from the Internet. See below:

<smtp log>

Then, it forwards to the back-end server. See below:

<smtp log>

Also, from the SMTP log, I did not find the front-end server attempted to
send e-mails to cbgnt.domain.net. As to why this behavior occurs, I believe
it can be caused the invalid entries in the homeMTA attribute. For your
reference, the invalid value is: CN=Microsoft
MTA\0ADEL:ab8d024e-d6ef-48a2-b68f-6939f5711d41,CN=Deleted
Objects,CN=Configuration,DC=domain,DC=net;

As the "school" account has been removed, I believe the e-mails
will not be forward to cbgnt.chicagotech.net again.

In the meantime, I suggest you collect the WinRoute information so that I
am able to verify the routing configuration:

WinRoute Information
==================
1. On the front-end server, please download the WinRoute tool from the
following link:
http://www.microsoft.com/downloads/deta ... a4da-45e0-
adea-6d44eb6c257b&displaylang=en

2. Start WinRoute.exe.
3. On the File menu, click New Server Query.
4. Type the server name and bind options that you want to use to connect to
an Exchange server.
5. Click File, click Save As to save the routing information to a .rte
file.
6. Send the file to me at ryanye@microsoft.com

As to your third question, I would like to confirm after removing the
"school" account, have you seen other spam e-mails stuck in the
queue? If yes, please let me know the name of the Queue where the e-mails
are stuck.

Regarding the poor reputation, it is hard to confirm this at this point.
From the symptoms, I can only tell that some spam sender is taking
advantage of your Exchange server.

First of all, thank you for your help.

1. Since the e-mail sent from MAILER-DAEMON@domain.net is first received by
the front-end server from the Internet, I feel better. Do you have guideline
for preventing spam? Or links?

2. After removing "school" account, I don't see any email in
cbgnt.chicagotech.net queue. Do you know a way to find any accounts with
the invalid entries in the homeMTA attribute? I would like to fix all of
them. I remember we had some issues when we migrating Exchange 5.5 to 2000.

I will send you WinRoute Information later.

have checked the WinRoute information and I believe the routing is
configured correctly.

As to your first question, I suggest you use Sender Filter to block the
e-mails sent from MAILER-DAEMON@domain.net. Here are the detailed steps:

Configure Sender Filter
===================================
1. Start the Exchange System Manager tool.
2. Expand Global Settings, right-click Message Delivery, and then click
Properties.
3. Click the Sender Filtering tab, and click Add.
4. Enter "@domain.net" (without quotation marks) in the Sender box and
click OK. Click OK.
5. Expand Servers, expand your computer, expand Protocols, expand SMTP,
right-click Default SMTP Virtual Server, and then click Properties.
6. On the General tab, click Advanced.
7. Click Edit, click to select the Apply Recipient Filter check box, and
then click OK three times.
8. Restart the SMTP service.

By doing this, any e-mails sent from @domain.net will be blocked.

As to the second question, I suggest you first run the following command to
query all mail-enabled user object's "homeMTA" attribute:

LDIFDE -f C:\output.txt -d "dc=domain,dc=extension" -r "(mailNickName=*)"
-l cn,homeMTA

The output will be saved in the C:\output.txt file. Please open this file
and check the user's homeMTA attribute to whether it is configured
correctly.

We have two windows 2000 DCs and two 2008 DCs. When I run the command line
on windows 2000, You receive this message;

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

H:\>LDIFDE -f C:\output.txt -d "dc=domain,dc=extension" -r
"(mailNickName=*)" -l
cn,homeMTA
Connecting to "2008dc2.chicagotech.net"
Logging in as current user using SSPI
Exporting directory to file C:\output.txt
Searching for entries...
Writing out entriesldap://domain.extension/dc=domain,dc=extension

No Entries found

The command has completed successfully

No thing logged in the output.txt.

If I run it in windows 2008, I receive this message:

H:\>LDIFDE -f C:\output.txt -d "dc=domain,dc=extension" -r
"(mailNickName=*)" -l
cn,homeMTA
Connecting to "2008DC1.chicagotech.net"
Logging in as current user using SSPI
Exporting directory to file C:\output.txt
Searching for entries...
Error opening output file.
The error code is 5
An error has occurred in the program
No log files were written. In order to generate a log file, please
specify the log file path via the -j option.

I understand that you when running the LDIFDE command, an error occurred or
no information was dumped.

I checked the command you have run and I noticed that you have not replaced
"domain" and "extension" part with the name of your domain.

In this specific case, you will need to run the following command:

LDIFDE -f C:\output.txt -d "dc=chicagotech,dc=net" -r "(mailNickName=*)"
-l cn,homeMTA

Note: The "domain" should be replaced with chicagotech, with the
"extension" should be replaced with net.

Please run the above command again and verify whether the AD info can be
dumped.

Sorry, didn't read carefully. I can't run it in windows 2008, but 2000 DC
works fine. When I search homeMTA, I find a lot. How do we know we have the
problem?

I will send you the output.

I understand that the command can be run on Windows 2000 domain controller
successfully, while it failed to run on Windows 2008 domain controller.

I checked the error code returned on Windows 2008 is "5", which means
"Access denied". Please understand that by default, UAC is enabled on
Windows 2008. Therefore, to run the LDIFDE command on Windows 2008, you
will to open Command Prompt by using the "Run as administrator". To do
this, right-click on Command Prompt and click "Run as administrator".

Also, I have checked the output.txt file and I have the following objects
have incorrect homeMTA attribute set:

dn: CN=Jeff Tamraz,CN=Users,DC=chicagotech,DC=net
dn: CN=SystemMailbox{832CAD08-4C1F-4492-A685-164CF67066A1},CN=Microsoft
Exchange System Objects,DC=chicagotech,DC=net
dn: CN=SystemMailbox{A4006661-AA6A-43F3-8CC7-9056FCFD2D9D},CN=Microsoft
Exchange System Objects,DC=chicagotech,DC=net

Note: The incorrect value is "CN=Microsoft
MTA\0ADEL:01551e0c-b715-4001-9ee8-dc27c26a5b76,CN=Deleted
Objects,CN=Configuration,DC=chicagotech,DC=net"

Please copy the value of the homeMTA attribute from another user to replace
the incorrect value.

Yes, Jeff Tamraz's Exchange Advanced is different from others.

1. I assume I need to copy "CN=Microsoft
MTA,CN=MAIL,CN=Servers,CN=NTDOMAIN,CN=Administrative Groups,CN
=cbg,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=chicagotech,DC=net" to replace
"CN=Microsoft MTA\0ADEL:01551e0c-b715-4001-9ee8-dc27c26a5b76,CN=Deleted
Objects,CN=Configuration,DC=chicagotech,DC=net". But how do you do that?
Use LDIFDE? Could you please give stem b ystep?

2. I don't see SystemMailbox in our user account.

3. What's teh value to replace these two "dn:
CN=SystemMailbox{832CAD08-4C1F-4492-A685-164CF67066A1},CN=Microsoft Exchange
System Objects,DC=chicagotech,DC=net" and

"dn: CN=SystemMailbox{A4006661-AA6A-43F3-8CC7-9056FCFD2D9D},CN=Microsoft
Exchange System Objects,DC=chicagotech,DC=net"?



4. What's different between "dn:
CN=SystemMailbox{2B0E57DF-675E-4C39-B8CB-50448AD1F2A8},CN=Microsoft Exchange
System Objects,DC=chicagotech,DC=net
changetype: add" and above two lines.

I have viewed the post history and would like to provide the following
information for your questions:

1). For your first quest, yes, we need to copy "CN=Microsoft
MTA,CN=MAIL,CN=Servers,CN=NTDOMAIN,CN=Administrative
Groups,CN=cbg,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=chicagotech,DC=net" to replace
the value
"CN=Microsoft MTA\0ADEL:01551e0c-b715-4001-9ee8-dc27c26a5b76,CN=Deleted
Objects,CN=Configuration,DC=chicagotech,DC=net"

To do this:

===========

WARNING: If using the ADSI Edit snap-in to incorrectly modify the
attributes of Active Directory objects, serious problems may occur. These
problems may require reinstalling Microsoft Windows Server, Microsoft
Exchange Server, or both. We cannot guarantee that problems that occur if
you incorrectly modify Active Directory object attributes can be solved.
Please first backup your AD information and Exchange server before trying
the following steps.

1. Start ADSiEdit snap-in. This tools is included in Windows 2003
supporting tools.

a. Install Windows 2000/2003 Support Tools from the Windows 2000/2003
Server CD if Windows 2000/2003 Support Tools is not already installed. To
do so, locate the Support folder on the CD, open the Tools folder, and then
double-click Setup.exe

b. After Windows 2000/2003 Support Tools is installed, click Start, point
to Programs, point to Windows 2000 Support Tools, and then click ADSI Edit.

2. In the CN=Domain [Your Domain Name] container, locate the following
container (where Domain is the name of your domain and OUname is the name
of the OU in which the distribution group exists):

DC=Domain,DC=COM
CN=Users

3. Highlight CN=Users, find the user "Jeff Tamraz" on the right panel

4. Open Properties of the user "Jeff Tamraz", under the Attribute Editor
tab, navigate to the homeMTA attribute.

5. Highlight the homeMTA attribute and then click Edit button

6. Set is value as the following

CN=Microsoft MTA,CN=MAIL,CN=Servers,CN=NTDOMAIN,CN=Administrative
Groups,CN=cbg,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=chicagotech,DC=net

2). For the second question,
SystemMailbox{832CAD08-4C1F-4492-A685-164CF67066A1} and
SystemMailbox{A4006661-AA6A-43F3-8CC7-9056FCFD2D9D} are located under the
following OU:

Active Directory Users and Computers (ADUC)-->Microsoft Exchange System
Objects

In ADSI, they are located under:

ADSI-->DC=Domain,DC=COM-->CN=Microsoft Exchange System Objects

3). For your third question, we can also set the two SystemMailbox homeMTA
value to the following:

CN=Microsoft MTA,CN=MAIL,CN=Servers,CN=NTDOMAIN,CN=Administrative
Groups,CN=cbg,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=chicagotech,DC=net

The steps are similar as described previously. Just remind that the two
objects are located under:

ADSI-->
DC=Domain,DC=COM-->
CN=Microsoft Exchange System Objects

4). For your fourth question, I have checked the
"SystemMailbox{2B0E57DF-675E-4C39-B8CB-50448AD1F2A8}", its homeMTA value is
correct and we do not need to change it.

The differences between
"SystemMailbox{2B0E57DF-675E-4C39-B8CB-50448AD1F2A8}" and previous two ones
are they are associated to different databases.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm


Return to Networking

Your Ad Here

Who is online

Users browsing this forum: No registered users and 5 guests

cron