Self send spam Black berry.
Hi, I have Exchange 2007 SP2 RU5 with all roles on a single server except EDGE on a different server on DMZ separated by an ISA. Lately users are getting as lot of self send spam. So after googling, I removed Ms-Exch-SMTP-Accept-Any-Recipient from the EDGE server using the below command. The spam stopped. But users using Black Berry started complaining. How can I strike a balance between both stopping self send spam and allowing users to use Black Berry to send their mails. We don't have a BIS. Any help appreciated. Get-ReceiveConnector Receive Connector Name | Remove-ADPermission -User NT AUTHORITY\ANONYMOUS LOGON -ExtendedRights Ms-Exch-SMTP-Accept-Any-Recipient Regards Liby Philip Mathew | ICT Consultant Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Self send spam Black berry.
You have to accept email from everyone if its your corporate mail server. That's how Email works.. Now to filter those connections.. You need to turn on RBL Block lists and use Zen.spamhaus.org Bl.spamcop.net (optional) Here is a good place to start with the built in mail filtering tools for Exchange 2007 http://www.msexchange.org/articles_tutorials/exchange-server-2007/security-message-hygiene/exchange-server-2007-spam-filtering-features-without-using-exchange-server-2007-edge-server.html Otherwise you need to look at spam filtering on the server or hosted. The list server host has a good program, but it takes resources and loads directly onto your server. Search the archives there are lots of posts on the subject. Greg Sweers CEO ACTS360.comhttp://www.acts360.com/ P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax From: Liby Philip Mathew [mailto:lmat...@path-solutions.com] Sent: Monday, January 03, 2011 3:35 AM To: MS-Exchange Admin Issues Subject: Self send spam Black berry. Hi, I have Exchange 2007 SP2 RU5 with all roles on a single server except EDGE on a different server on DMZ separated by an ISA. Lately users are getting as lot of self send spam. So after googling, I removed Ms-Exch-SMTP-Accept-Any-Recipient from the EDGE server using the below command. The spam stopped. But users using Black Berry started complaining. How can I strike a balance between both stopping self send spam and allowing users to use Black Berry to send their mails. We don't have a BIS. Any help appreciated. Get-ReceiveConnector Receive Connector Name | Remove-ADPermission -User NT AUTHORITY\ANONYMOUS LOGON -ExtendedRights Ms-Exch-SMTP-Accept-Any-Recipient Regards Liby Philip Mathew | ICT Consultant Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Self send spam Black berry.
And never ever put yourself in your own contacts! John W. Cook System Administrator Partnership For Strong Families 5950 NW 1st Place Gainesville, Fl 32607 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4 From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Monday, January 03, 2011 9:28 AM To: MS-Exchange Admin Issues Subject: RE: Self send spam Black berry. You have to accept email from everyone if its your corporate mail server. That's how Email works.. Now to filter those connections.. You need to turn on RBL Block lists and use Zen.spamhaus.org Bl.spamcop.net (optional) Here is a good place to start with the built in mail filtering tools for Exchange 2007 http://www.msexchange.org/articles_tutorials/exchange-server-2007/security-message-hygiene/exchange-server-2007-spam-filtering-features-without-using-exchange-server-2007-edge-server.html Otherwise you need to look at spam filtering on the server or hosted. The list server host has a good program, but it takes resources and loads directly onto your server. Search the archives there are lots of posts on the subject. Greg Sweers CEO ACTS360.comhttp://www.acts360.com/ P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax From: Liby Philip Mathew [mailto:lmat...@path-solutions.com] Sent: Monday, January 03, 2011 3:35 AM To: MS-Exchange Admin Issues Subject: Self send spam Black berry. Hi, I have Exchange 2007 SP2 RU5 with all roles on a single server except EDGE on a different server on DMZ separated by an ISA. Lately users are getting as lot of self send spam. So after googling, I removed Ms-Exch-SMTP-Accept-Any-Recipient from the EDGE server using the below command. The spam stopped. But users using Black Berry started complaining. How can I strike a balance between both stopping self send spam and allowing users to use Black Berry to send their mails. We don't have a BIS. Any help appreciated. Get-ReceiveConnector Receive Connector Name | Remove-ADPermission -User NT AUTHORITY\ANONYMOUS LOGON -ExtendedRights Ms-Exch-SMTP-Accept-Any-Recipient Regards Liby Philip Mathew | ICT Consultant Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the company. Warning: Although precautions have been taken to make sure no viruses are present in this email, the company cannot accept responsibility for any loss or damage that arise from the use of this email or attachments. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Self send spam Black berry.
Hahaha.. Made that mistake myself early on.. That's with Vipre Exchange and any other spam software that accepts connections automatically with any contacts you have in Outlook. :) Greg Sweers CEO ACTS360.comhttp://www.acts360.com/ P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax From: John Cook [mailto:john.c...@pfsf.org] Sent: Monday, January 03, 2011 9:30 AM To: MS-Exchange Admin Issues Subject: RE: Self send spam Black berry. And never ever put yourself in your own contacts! John W. Cook System Administrator Partnership For Strong Families 5950 NW 1st Place Gainesville, Fl 32607 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4 From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Monday, January 03, 2011 9:28 AM To: MS-Exchange Admin Issues Subject: RE: Self send spam Black berry. You have to accept email from everyone if its your corporate mail server. That's how Email works.. Now to filter those connections.. You need to turn on RBL Block lists and use Zen.spamhaus.org Bl.spamcop.net (optional) Here is a good place to start with the built in mail filtering tools for Exchange 2007 http://www.msexchange.org/articles_tutorials/exchange-server-2007/security-message-hygiene/exchange-server-2007-spam-filtering-features-without-using-exchange-server-2007-edge-server.html Otherwise you need to look at spam filtering on the server or hosted. The list server host has a good program, but it takes resources and loads directly onto your server. Search the archives there are lots of posts on the subject. Greg Sweers CEO ACTS360.comhttp://www.acts360.com/ P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax From: Liby Philip Mathew [mailto:lmat...@path-solutions.com] Sent: Monday, January 03, 2011 3:35 AM To: MS-Exchange Admin Issues Subject: Self send spam Black berry. Hi, I have Exchange 2007 SP2 RU5 with all roles on a single server except EDGE on a different server on DMZ separated by an ISA. Lately users are getting as lot of self send spam. So after googling, I removed Ms-Exch-SMTP-Accept-Any-Recipient from the EDGE server using the below command. The spam stopped. But users using Black Berry started complaining. How can I strike a balance between both stopping self send spam and allowing users to use Black Berry to send their mails. We don't have a BIS. Any help appreciated. Get-ReceiveConnector Receive Connector Name | Remove-ADPermission -User NT AUTHORITY\ANONYMOUS LOGON -ExtendedRights Ms-Exch-SMTP-Accept-Any-Recipient Regards Liby Philip Mathew | ICT Consultant Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email
RE: Designing Implementing Exchange 2010 in the new year.
Soa detailed design of this magnitude is not something I would attempt to do via email. That being said, you've obviously done lots of investigation already, which is a good thing. I'd recommend you sit down with someone who has done a migration this large and spend a couple of days coming up with a detailed plan. I think you don't need that many servers based on 15K users. I'd probably go with four HT/CAS combinations. [1] what's your RTO? What, if anything is your backup speed/mechanism? That's the questions that defines the answer. [2] Depends on your user mix. If everyone is Outlook and you want one CAS to be able to handle the load of two CAS in case of h/w failure, I'd probably look at limiting my NORMAL active user count to around 4,000. What you want to watch out for is TCP port exhaustion. 4K users is probably going to sit around 25K ports, 8K users about 50K ports, which still gives you a little headroom for multi-mailbox users. Bumping that to 5,000 is too many. On the other hand, if everyone is using OWA, that's one port per CAS and if you size your hardware right, you can support 20K users on that CAS. Note: Outlook uses about six TCP ports per mailbox. Doesn't matter whether Outlook Anywhere or MAPI; it's still about six ports. Every additional mailbox that you have Outlook open adds ANOTHER six ports. So, if your normal configuration is to have every user open their own mailbox plus a shared mailbox, you've just cut your headcount that can be served by a single CAS in half. [3] as long as you configure all the internal and external URI's properly, Exchange doesn't care. [4] You need your OWA name, your autodiscover name, and I like to add my SMTP name. That's it. You must have (minimally) a self-signed certificate on every hub so that every hub can communicate with every other hub and MB server using SSL/TLS. All communications are encrypted. [8] proper configuration of your OutlookProviders (see Set-OutlookProvider) and autodiscover handle this. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: helpdesk UK [mailto:uk.helpd...@gmail.com] Sent: Saturday, January 01, 2011 8:55 AM To: MS-Exchange Admin Issues Subject: Designing Implementing Exchange 2010 in the new year. Hi Wish everyone a Happy New Year!!! Currently we have Lotus Domino and Windows 200 AD and it has not been maintained well. Also due to various business reasons the migrations have been long over due; hence we will be getting rid of it all soon and moving to Windows 2008 and Exchange 2010. We are not migrating stuff it will all be a new install and users will be imported from scratch. Our internal AD FQDN and external FQDN are changing too due to business mergers. I have been tasked to sort out the Exchange 2010 design. New FQDN = externalfqdn.comhttp://externalfqdn.com = External Name Space internalfqdn.internal = Internal Name Space (AD 2008 R2) No. of Users == Total number of users will be approx. 10,000 to start off with and potential for another 3000 in 6 months' time. But after a year the business plans are to grow even more so the solution is being designed with that in mind so we can expand easily. CAS servers === CAS1.internalfqdn.internal CAS2.internalfqdn.internal CAS3.internalfqdn.internal CAS4.internalfqdn.internal Mail Servers MBX1.internalfqdn.internal MBX2.internalfqdn.internal MBX3.internalfqdn.internal MBX4.internalfqdn.internal HT Servers == HT1.internalfqdn.internal HT2.internalfqdn.internal HLB (Hardware Load Balancers) == 2 * HLB ( this is still being discussed no product has been finalised yet ) Virtualisation === VMware ESX is the product of choice and all servers will be running virtually and storage will be on a fibre SAN. Queries == 1. How many users should we have in one database? 2. How many users should we have overall on one single server? 3. We intend to use the same FQDN name internally and externally on the CAS server URL setting; in spite of our FQDN internally and externally are not the same. Is this recommended or any known gotchas? a. External URL ( mail.externalfqdn.comhttp://mail.externalfqdn.com ) b. Internal URL ( mail.externalfqdn.comhttp://mail.externalfqdn.com ) c. We will apply the external URL using the new Configure External Client Access Domain wizard and the internal URL's manually using power shell. d. We will also create a new AD zone for our external FQDN and ensure required records point to internal ip address of the HLB ( www / mail / autodiscover / etc ) 4. Clarification on the SAN certificate. a. We intend to do SSL Offloading on HLB any gotchas/recommendations? b. If we have a HLB than we only need a single SAN cert correct on the HLB? c. Will the CAS servers need any certificates at all I guess not due to
Too many Proxy Addresses on a Public Folder Tree.....
I have 3x win2k3 SP 2 DC's and 2x 2008 SP2 DCs. 2 Sites. Site A has 2 Exchange 2007 servers running on Server 2008. Site B has an Exchange 2003 server running on Server 2003. All servers are fully patched and updated. I am trying to promote a 2008R2 DC. It will not promote, I get the following error. 12/30/2010 12:15:56 [INFO] EVENTLOG (Error): NTDS Replication / Replication : 1084Internal event: Active Directory Domain Services could not update the following object with changes received from the following source directory service. This is because an error occurred during the application of the changes to Active Directory Domain Services on the directory service. Object: CN=PF,CN=PF,CN=InformationStore,CN=KPMPEXCH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Kleiner Perkins Caufield and Byers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=kpcb,DC=com Object GUID:c842ac58-0b72-41e3-a63a-0c740c04a394 Source directory service: KPMPDC01.kpcb.com When I look on an existing DC, I get the following error: Internal error: The security descriptor propagation task encountered an error while processing the following object. The propagation of security descriptors may not be possible until the problem is corrected. Additional Data CN=PF,CN=PF,CN=InformationStore,CN=KPMPEXCH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Kleiner Perkins Caufield and Byers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=kpcb,DC=com Error value: -1026 JET_errRecordTooBig, Record larger than maximum size Internal ID:20903d5 This leads me to the KB: http://support.microsoft.com/kb/914036 I created an LDIF dump file to find the attribute values: I have 1225 Proxy addresses on the public folder. Uploaded on the SkyDrive Link below for your viewing pleasure. http://cid-ca7e8015c6eb699c.skydrive.live.com/redir.aspx?resid=CA7E8015C6EB699C!125 So I need to remove all the proxy addresses, and verify that the RUS is applied properly. My question at this time is 1) What is the best way to do this in a co-existence scenario? 2) My Recipient policy is currently very simple, but some users do have a different primary proxy address, what can I do to verify these changes are not lost. 3) How do I ensure that the 1225 improper proxy addresses are removed from the PF tree? Thanks for your help --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Too many Proxy Addresses on a Public Folder Tree.....
IMO, the first question is whether or not you are still using RFAX and whether or not it depends on those proxy addresses being present. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jeremy Anderson [mailto:jan...@mapiadmin.net] Sent: Monday, January 03, 2011 2:51 PM To: MS-Exchange Admin Issues Subject: Too many Proxy Addresses on a Public Folder Tree. I have 3x win2k3 SP 2 DC's and 2x 2008 SP2 DCs. 2 Sites. Site A has 2 Exchange 2007 servers running on Server 2008. Site B has an Exchange 2003 server running on Server 2003. All servers are fully patched and updated. I am trying to promote a 2008R2 DC. It will not promote, I get the following error. 12/30/2010 12:15:56 [INFO] EVENTLOG (Error): NTDS Replication / Replication : 1084Internal event: Active Directory Domain Services could not update the following object with changes received from the following source directory service. This is because an error occurred during the application of the changes to Active Directory Domain Services on the directory service. Object: CN=PF,CN=PF,CN=InformationStore,CN=KPMPEXCH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Kleiner Perkins Caufield and Byers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=kpcb,DC=com Object GUID:c842ac58-0b72-41e3-a63a-0c740c04a394 Source directory service: KPMPDC01.kpcb.com When I look on an existing DC, I get the following error: Internal error: The security descriptor propagation task encountered an error while processing the following object. The propagation of security descriptors may not be possible until the problem is corrected. Additional Data CN=PF,CN=PF,CN=InformationStore,CN=KPMPEXCH01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Kleiner Perkins Caufield and Byers,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=kpcb,DC=com Error value: -1026 JET_errRecordTooBig, Record larger than maximum size Internal ID:20903d5 This leads me to the KB: http://support.microsoft.com/kb/914036 I created an LDIF dump file to find the attribute values: I have 1225 Proxy addresses on the public folder. Uploaded on the SkyDrive Link below for your viewing pleasure. http://cid-ca7e8015c6eb699c.skydrive.live.com/redir.aspx?resid=CA7E8015C6EB699C!125 So I need to remove all the proxy addresses, and verify that the RUS is applied properly. My question at this time is 1) What is the best way to do this in a co-existence scenario? 2) My Recipient policy is currently very simple, but some users do have a different primary proxy address, what can I do to verify these changes are not lost. 3) How do I ensure that the 1225 improper proxy addresses are removed from the PF tree? Thanks for your help --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Too many Proxy Addresses on a Public Folder Tree.....
No more right fax, and i an in the process of manually removing every single one in ADSI My clicking arm is getting sore --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Too many Proxy Addresses on a Public Folder Tree.....
You can't remove them with a script? -Original Message- From: Jeremy Anderson [mailto:jan...@mapiadmin.net] Sent: Monday, January 03, 2011 12:16 PM To: MS-Exchange Admin Issues Subject: RE: Too many Proxy Addresses on a Public Folder Tree. No more right fax, and i an in the process of manually removing every single one in ADSI My clicking arm is getting sore --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Too many Proxy Addresses on a Public Folder Tree.....
LDIFDE is your friend... --Original Message-- From: Jeremy Anderson To: MS-Exchange Admin Issues ReplyTo: MS-Exchange Admin Issues Subject: RE: Too many Proxy Addresses on a Public Folder Tree. Sent: Jan 3, 2011 12:16 No more right fax, and i an in the process of manually removing every single one in ADSI My clicking arm is getting sore --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist Sent from my Verizon Wireless BlackBerry --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Too many Proxy Addresses on a Public Folder Tree.....
And or ADMODIFY .. -Original Message- From: My New Display Name for Bob. :) [mailto:don@gmail.com] Sent: Monday, January 03, 2011 12:56 PM To: MS-Exchange Admin Issues Subject: Re: Too many Proxy Addresses on a Public Folder Tree. LDIFDE is your friend... --Original Message-- From: Jeremy Anderson To: MS-Exchange Admin Issues ReplyTo: MS-Exchange Admin Issues Subject: RE: Too many Proxy Addresses on a Public Folder Tree. Sent: Jan 3, 2011 12:16 No more right fax, and i an in the process of manually removing every single one in ADSI My clicking arm is getting sore --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist Sent from my Verizon Wireless BlackBerry --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: Too many Proxy Addresses on a Public Folder Tree.....
or adfind... On Mon, Jan 3, 2011 at 12:55, My New Display Name for Bob. :) don@gmail.com wrote: LDIFDE is your friend... --Original Message-- From: Jeremy Anderson To: MS-Exchange Admin Issues ReplyTo: MS-Exchange Admin Issues Subject: RE: Too many Proxy Addresses on a Public Folder Tree. Sent: Jan 3, 2011 12:16 No more right fax, and i an in the process of manually removing every single one in ADSI My clicking arm is getting sore --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist Sent from my Verizon Wireless BlackBerry --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Too many Proxy Addresses on a Public Folder Tree.....
Short script. Or just completely remove the attribute and only put the two back that need to be there. That's easier than writing a script. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -Original Message- From: Jeremy Anderson [mailto:jan...@mapiadmin.net] Sent: Monday, January 03, 2011 3:16 PM To: MS-Exchange Admin Issues Subject: RE: Too many Proxy Addresses on a Public Folder Tree. No more right fax, and i an in the process of manually removing every single one in ADSI My clicking arm is getting sore --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Self send spam Black berry.
Hi Greg, Did the configuration. It seems to be working. But when I check Spamhaus site they say a restriction of 10 connection and 30 query per day for free use. How is the connection measured? How can check if the connection exceeds the limit and I guess the query is number of time the mail server queries spamhaus and it will be same as the number of mail received. Regards Liby Philip Mathew | ICT Consultant ICT Professional Services Path Solutions Tel: +965 24824600 Ext. 703 Fax: +965 24824500 www.path-solutions.comhttp://www.path-solutions.com/ From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Monday, January 03, 2011 5:28 PM To: MS-Exchange Admin Issues Subject: RE: Self send spam Black berry. You have to accept email from everyone if its your corporate mail server. That's how Email works.. Now to filter those connections.. You need to turn on RBL Block lists and use Zen.spamhaus.org Bl.spamcop.net (optional) Here is a good place to start with the built in mail filtering tools for Exchange 2007 http://www.msexchange.org/articles_tutorials/exchange-server-2007/security-message-hygiene/exchange-server-2007-spam-filtering-features-without-using-exchange-server-2007-edge-server.html Otherwise you need to look at spam filtering on the server or hosted. The list server host has a good program, but it takes resources and loads directly onto your server. Search the archives there are lots of posts on the subject. Greg Sweers CEO ACTS360.comhttp://www.acts360.com/ P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax From: Liby Philip Mathew [mailto:lmat...@path-solutions.com] Sent: Monday, January 03, 2011 3:35 AM To: MS-Exchange Admin Issues Subject: Self send spam Black berry. Hi, I have Exchange 2007 SP2 RU5 with all roles on a single server except EDGE on a different server on DMZ separated by an ISA. Lately users are getting as lot of self send spam. So after googling, I removed Ms-Exch-SMTP-Accept-Any-Recipient from the EDGE server using the below command. The spam stopped. But users using Black Berry started complaining. How can I strike a balance between both stopping self send spam and allowing users to use Black Berry to send their mails. We don't have a BIS. Any help appreciated. Get-ReceiveConnector Receive Connector Name | Remove-ADPermission -User NT AUTHORITY\ANONYMOUS LOGON -ExtendedRights Ms-Exch-SMTP-Accept-Any-Recipient Regards Liby Philip Mathew | ICT Consultant Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Self send spam Black berry.
Hi John, Can you please explain this. I don't want to mess up the mail flow:). Regards Liby Philip Mathew | ICT Consultant ICT Professional Services Path Solutions Tel: +965 24824600 Ext. 703 Fax: +965 24824500 www.path-solutions.comhttp://www.path-solutions.com/ From: John Cook [mailto:john.c...@pfsf.org] Sent: Monday, January 03, 2011 5:30 PM To: MS-Exchange Admin Issues Subject: RE: Self send spam Black berry. And never ever put yourself in your own contacts! John W. Cook System Administrator Partnership For Strong Families 5950 NW 1st Place Gainesville, Fl 32607 Cell (352) 215-6944 MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4 From: greg.swe...@actsconsulting.net [mailto:greg.swe...@actsconsulting.net] Sent: Monday, January 03, 2011 9:28 AM To: MS-Exchange Admin Issues Subject: RE: Self send spam Black berry. You have to accept email from everyone if its your corporate mail server. That's how Email works.. Now to filter those connections.. You need to turn on RBL Block lists and use Zen.spamhaus.org Bl.spamcop.net (optional) Here is a good place to start with the built in mail filtering tools for Exchange 2007 http://www.msexchange.org/articles_tutorials/exchange-server-2007/security-message-hygiene/exchange-server-2007-spam-filtering-features-without-using-exchange-server-2007-edge-server.html Otherwise you need to look at spam filtering on the server or hosted. The list server host has a good program, but it takes resources and loads directly onto your server. Search the archives there are lots of posts on the subject. Greg Sweers CEO ACTS360.comhttp://www.acts360.com/ P.O. Box 1193 Brandon, FL 33509 813-657-0849 Office 813-758-6850 Cell 813-341-1270 Fax From: Liby Philip Mathew [mailto:lmat...@path-solutions.com] Sent: Monday, January 03, 2011 3:35 AM To: MS-Exchange Admin Issues Subject: Self send spam Black berry. Hi, I have Exchange 2007 SP2 RU5 with all roles on a single server except EDGE on a different server on DMZ separated by an ISA. Lately users are getting as lot of self send spam. So after googling, I removed Ms-Exch-SMTP-Accept-Any-Recipient from the EDGE server using the below command. The spam stopped. But users using Black Berry started complaining. How can I strike a balance between both stopping self send spam and allowing users to use Black Berry to send their mails. We don't have a BIS. Any help appreciated. Get-ReceiveConnector Receive Connector Name | Remove-ADPermission -User NT AUTHORITY\ANONYMOUS LOGON -ExtendedRights Ms-Exch-SMTP-Accept-Any-Recipient Regards Liby Philip Mathew | ICT Consultant Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist CONFIDENTIALITY STATEMENT: The information transmitted, or contained or attached to or with this Notice is intended only for the person or entity to which it is addressed and may contain Protected Health Information (PHI), confidential and/or privileged material. Any review, transmission, dissemination, or other use of, and taking any action in reliance upon this information by persons or entities other than the intended recipient without the express written consent of the sender are prohibited. This information may be protected by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and other Federal and Florida laws. Improper or unauthorized use or disclosure of this information could result in civil and/or criminal penalties. Consider the environment. Please don't print this e-mail unless you really need to. This email and any attached files are confidential and intended solely for the intended recipient(s). If you are not the named recipient you should not read, distribute, copy or alter this email. Any views or opinions expressed in this email are those of the author and do not represent those of the
