Monday, November 25, 2013

Difference between Share point server 2010 and Share point server 2013

Difference between Share point server 2010 and Share point server 2013



Hi friends,
In this my first article in which, I am going to introduce you about the Microsoft brand new Share Point 2013, in this article I will cover the major differences between the Share Point 2010 and 2013.

Share point server 2013 brings strong enhancement to its 2010 predecessor with
All new consoles having new feel of windows 8 operating System. Customer feedback and a growing social world have influenced changes to development, social computing, search, multilevel team site making upgradable to share point 2013 a new attractive possibility. Now
Microsoft has released share point 2013 and its online counterpart Office 365, IT decision makers must choose whether to deploy it in-house or use the latest cloud-based iterations of the collaboration platform.


Features
SharePoint 2010
SharePoint2013
Sandbox solution
Available
Available
App catalog and marketplace
NA
Available
Team sites
Available
Available
Work Management
NA
Available
News feed
NA
Available
Sky drive pro
NA
Available
Community sites
NA
Available
Task list aggregation
NA
Available
Follow content & people
NA
Available
Basic search
Available
Available
Out of box fast search
NA
Available
Continuous crawl
NA
Available
Content Authoring
Available
Available
Records Management
Available
Available
Managed Navigation
Available
Available
Managed Metadata
Available
Available
Cross site publishing
Available
Available
e-discovery
Available
Available
Excel  service ,power pivot
Available
Available
Scorecard & Dashboard
Available
Available
access
NA
Available
Visual studio
Available
Available
InfoPath
Available
Available
Excel
Available
Available
SharePoint 2013 workflow
NA
Available
Business Connectivity Services
Available
Available
Design Manager
NA
Available
Channels (master pages)
NA
Available
Update SharePoint designer
NA
Available
Native support for iOS/ android
NA
Available
Mobile views
Available
Available
Office web apps
Available
Available

                        ************************************************
                                                             Regards,
                                                          Sunil Kumar
                                           MCP, MCTS, MCITP, VCA SharePoint


Sunday, November 24, 2013

SPF Record Failure Issue

                                                 SPF Record Issue

Hi Friends,
In this article I am going to introduce you with a common issue of Email organization which called "SPF record not found"

If you're not able to send the emails due to SPF record are not found or not valid.

What is SPF??????

Sender Policy Framework (SPF) is an email validation system designed to prevent email spam by detecting email spoofing, a common vulnerability, by verifying sender IP addresses. SPF allows administrators to specify which hosts are allowed to send mail from a given domain by creating a specific SPF record (or TXT record) in the Domain Name System (DNS). Mail exchangers use the DNS to check that mail from a given domain is being sent by a host sanctioned by that domain's administrators

 Firstly we have to check the emails logs and on the behalf of that logs, we analyze that email is rejecting due to SPF record failure.
Here I am attaching a screenshot of SFP record failure issue.


                                                Image-1.1

For more details click on log and you will see the following results.

6:59:23.000 PM   
Oct 24 18:59:23 mx-01.test.com sm-mta[1165]: r9OFxLhb001165: from=<Reggie.Waterman@rci.rogers.com>, size=7728, class=0, nrcpts=1, msgid=<da19bbed761a4c248265eb39728e10b1@CO1PR04MB426.namprd04.prod.outlook.com>, proto=ESMTP, daemon=MTA, tls_verify=FAIL, auth=NONE, relay=mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208]
Oct 24 18:59:23 mx-01.test.comdkim-filter[5874]: r9OFxLhb001165: no signature data
Oct 24 18:59:23 mx-01.test.comsm-mta[1165]: r9OFxLhb001165: Milter insert (1): header: X-DKIM:  OpenDKIM Filter v2.1.3 mx-01.test.comr9OFxLhb001165
Oct 24 18:59:23 mx-01.test.comMM: [Jilter Processor 17 - Async Jilter Worker 13 - 127.0.0.1:42288-r9OFxLhb001165] INFO  user.log  - mtaqid=r9OFxLhb001165, engine=cloudmark, from=<Reggie.Waterman@rci.rogers.com>, recipients=<chad.saliba@test.com>, relay=mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208], spam_score=0.00, size=7947, spam_class=ham
Oct 24 18:59:24 mx-01.test.comMM: [Jilter Processor 17 - Async Jilter Worker 13 - 127.0.0.1:42288-r9OFxLhb001165] INFO  user.log  - SPF.Check: classification=SPF-Failure
Oct 24 18:59:24 mx-01.test.comMM: [Jilter Processor 17 - Async Jilter Worker 13 - 127.0.0.1:42288-r9OFxLhb001165] INFO  user.log  - mtaqid=r9OFxLhb001165, pra=Reggie.Waterman@rci.rogers.com, relay=mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208], sid-status=FAIL
Oct 24 18:59:24 mx-01.test.comMM: [Jilter Processor 17 - Async Jilter Worker 13 - 127.0.0.1:42288-r9OFxLhb001165] INFO  user.log  - mtaqid=r9OFxLhb001165, msgid=<da19bbed761a4c248265eb39728e10b1@CO1PR04MB426.namprd04.prod.outlook.com>, from=<Reggie.Waterman@rci.rogers.com>, size=7947, to=<chad.saliba@test.com>, relay=mail-bl2lp0208.outbound.protection.outlook.com [207.46.163.208], categorization=clean, disposition=permanently-rejected
Oct 24 18:59:24 mx-01.test.comsm-mta[1165]: r9OFxLhb001165: Milter: data, reject=551 SPF failed
Oct 24 18:59:24 mx-01.test.comsm-mta[1165]: r9OFxLhb001165: to=<chad.saliba@test.com>, delay=00:00:01, pri=37728, stat=SPF failed


Note: Under the red bold color, you can see the SPF failure issue.

Visit on the following sites to check the status of SPF Failure or understand more about the  SPF record.

                Or

To resolve this issue, you should inform to IT-Team to register or verify the IP address of their Sending (Outgoing) server in public DNS SPF record.

                  **************************************************************

                                                                               
                                        Regards,
                                     Arun Chaudhary
                              MCP, MCTS, MCITP, VCA, ITIL


                                

TLS Encryption Issue

                                TLS Encryption Issue


Hi Friends,
In this article I am going to introduce you a common issue of Email organization which called TLS encryptions is less than 168 bit. If your organization users are sending email to external domain but mail are getting bounce due to “TLS encryption setting is less than 168 bit on receiver end”.

How to analyze this issue in log files of your server.

Here is an example of Sendmail Sentrion Mail server.

·         Check the Emails NDR.
·         Check logs in Sentrion master console and expand the logs for more details.
·         If issue is regarding TLS encryption is less than 168 bit, it will be appear in the log files.

Here I am attaching a screenshots of TLS encryption issue log files.


                                                Image-1.1

Note:Under the red box you can see the issue of TLS encryption.

How to resolve this issue:

To resolve this issue, check your MX_gateway “TLS encryption setting on 168 bit” so emails can deliver successfully.

Once you done this task at your end, send an test email to receiver and make sure that issue is resolved.

                                *****************************************************

                                                Regards,
                                         Arun Chaudhary

                                    MCP, MCTS, MCITP, VCA, ITIL

Domain Greylisting Issue

                                    Domain Greylisting



In This article, I am going to introduce you with a common issue of mail servers called Domain greylisting (emails are not getting deliver due to domain is greylisted in commtouch).

Issue: Emails were getting rejected due to domain was considering temporary as a Spam sender

Note: Greylisting is a measure against spam where the receiving server would reject a message temporarily with a message after which time to retry, usually within minutes and not later than some timeout (usually ~ 4 hours).  If the sender waits accordingly and resends the message within the timeout, it will be whitelisted, otherwise not.

How to check the domain greylisting

{Note: There is no exact tool to check the Greylisting of a domain, we can check the log files and NDR’s for more details.}

How to check domain whitelisting and blacklisting of domains.

Go to the following links and check.

Open this link and type the domain name under the Server Name or Domain and click on Blacklist check.


http://mxtoolbox.com/blacklists.aspx
                             Image- 1.1

Note: For testing purpose here I am going to test the blacklisting of http://www.songs.pk 

When you will type the songs.pk under the domain name and click on blacklist check, you will get the following result.


                                    Image- 1.2

Note: Here you can see that this domain is showing blacklisted, it’s mean we are not able to send and receive emails from this domain, because it seems Spam sender.

How to verify that domain is whitelisting

Our email server doesn't seem to understand greylisting. When sending emails to external addresses whose servers implement greylisting, our MTA seems to retry several times immediately (which will be rejected for obvious reasons) and then give up and retry only after hours.




Analyzing Email Header

    Analyzing Email Header

In this article, I am going to introduce my followers that how to analyze the Email headers fields and understand the different- different portion information of Email header.
Before we start analyzing the email header field, we should know how to access or extract the email header in different - different emails clients.
1. How to access Email header in Gmail:
Login to your Gmail account & click on any email (which header you want to analyze).
Click on triangular button under the red circle and click on Show original.


                     Image-1.1
When you will click on show original, Email header will be open in a new window, copy that email header in any text or word file to analyze it.

2. How to access Email header in Yahoo.com
Login to Yahoomail
Click on More under the red box and then click on View full header to open the email header.



                                                Image-1.2

3. How to access the Email header in Hotmail
Login to your hotmail account
Click on any email, which header you want to access
Click on the red circle place and click on View message source


                                                Image- 1.3

4. Access the Email Header in Microsoft Outlook
Login in MS Outlook and double click on any email, which header you want to access
Click on triangular under the red circle box
See the Email header under the Internet header.


                                                Image-1.4

5. Access the Email header in Microsoft Outlook Express
Login in MS Outlook Express and click on email, which header you want to access
Right-click on it and select Properties and go to Details to see the header.

Analyzing the Email Header:
Here I am going to show you the original Email header and will explain the each part of message header.

                                                                                                                                                                                                                                                               
MIME-Version: 1.0
Received: by 10.221.37.133 with HTTP; Sat, 23 Nov 2013 01:16:32 -0800 (PST)
Date: Sat, 23 Nov 2013 14:46:32 +0530
Delivered-To: arunkalagarh@gmail.com
Message-ID: <CAE-W5LJM8w88r9U9JZsw3Zb4cPWQZLEU0CeSwmMTmMgcwCF_5g@mail.gmail.com>
Subject: docs
From: Arun Chaudhary <arunkalagarh@gmail.com>
To: Arun Chaudhary <arunkalagarh@gmail.com>
X-Mailer: Mail Client
Content-Type: multipart/mixed; boundary=001a1133840e386fef04ebd49605

--001a1133840e386fef04ebd49605
Content-Type: multipart/alternative; boundary=001a1133840e386fea04ebd49603

--001a1133840e386fea04ebd49603
Content-Type: text/plain; charset=UTF-8


Understand the different - different part of an Email Header:
·         MIME ver :                   Version of MIME  
·         Received :                    Sender IP address and protocol
·         Date:                              The date the message was sent
·         Delivered To:              Receiver email ID
·         Message-ID:                                The ID of the message
·         Subject:                         The message subject
·         From:                             The message sender email ID
·         To:                                   The message recipient email ID
·         X-Mailer:                      The mail client (mail program) used to send the message
·         Content Type:            The content of Email, like: HTMP, plain text

The From:  line, which contains the sender of the message could be faked easily, so you should not rely on this information.
The lines in green contain the routing information, from the senders computer to the recipients mailserver.
                Let's have a closer look at these lines:
Received: from senderhostname [xxxx.xxxx.xxxx.xxxx] (helo=[ senderhostname])
by mailserver.senderdomain.tld with esmtpa (Exim x.xx)
(envelope-from <sender@senderdomain.tld) id yyyy.yyyy.yyyy.yyyy
for recipient@recipientdomain.tld; Tue, 01 Apr 2013 10:36:08 -0100
 The message was sent from the senders computer with the IP address xxxx.xxxx.xxxx.xxxx to the mailserver of the sender. In many cases the sender IP xxxx.xxxx.xxxx.xxxx is a dynamic IP address, e.g. DSL. The IP address gives many information's about the sender, the location of the sender and the provider.
Received: from mailserver.senderdomain.tld ([bbb.bbb.bbb.bbb] helo=mailserver.senderdomain.tld)
by mailexchanger.recipientdomain.tld with esmtp
id xxxxxx-xxxxxx-xx 
  The message was transferred from the senders mailserver with the IP address bbb.bbb.bbb.bbb to the recipients mailexchanger. The mailexchanger is the mailserver, which accepts incoming messages for a domain.

Received: from mailexchanger.recipientdomain.tld([ccc.ccc.ccc.ccc])
by mailserver.recipientdomain.tld running ExIM with esmtp
id xxxxxx-xxxxxx-xxx; Wed, 2 Apr 2013 11:39:23 +0200 
 The message was finally received by the recipients mailserver from the the recipients mailexchanger ccc.ccc.ccc.ccc.
 This is only a sample, which should show the principles. The message routing can contain much more steps, depending on the used mailprovider. It should always be possible to see the sender computer IP address aaa.aaa.aaa.aaa and the sender mailserver bbb.bbb.bbb.bbb if the message was sent from a mail client and a client computer. If the message was sent from a webmail client, then the real IP address of the sender is not included - in this case aaa.aaa.aaa.aaa (if any) will be the IP address of the webmail.
Some might try to fake the routing information, but your mailserver should give you a warning that something is not correct during the transfer from the sender mailserver bbb.bbb.bbb.bbb to the recipient mailexchanger ccc.ccc.ccc.ccc.

Note: Please leave your comments , if you like this articles and send your any query to me, I will get back you with possible solution.

                                                        Regards,

                                      Arun Chaudhary