Sometimes there are local less world known share websites that are not supported out of the box by the RadSocialShare.

An empty template similar to the one for a Styled button can be added where you can place your own button's markup so that a more uniform look can be achieved while keeping the desired functionality.

In the meantime, the approach from the following code library project can be used so you can add custom buttons: http://www.telerik.com/support/code-library/add-pinterest---pin-it-button-to-radsocialshare

Another approach you can take is to use the control's API (http://docs.telerik.com/devtools/aspnet-ajax/controls/socialshare/client-side-programming/radsocialshare-object) and events (http://docs.telerik.com/devtools/aspnet-ajax/controls/socialshare/client-side-programming/events/onsocialbuttonclicking) and a social network you will not be using as a custom button. For example, Digg:

			<telerik:RadSocialShare runat="server" ID="RadSocialShare1" OnSocialButtonClicking="OnSocialButtonClicking" UrlToShare="somePage.aspx" TitleToShare="some title">
				<MainButtons>
					<telerik:RadSocialButton SocialNetType="Digg" />
				</MainButtons>
			</telerik:RadSocialShare>
			<script>
				function OnSocialButtonClicking(sender, args) {
					if (args.get_socialNetType() == "Digg") {
						args.set_cancel(true);
						window.open(
							"someSocialNetworkSharingUrl.html?url=" + sender.get_urlToShare() +
							"&title=" + sender.get_titleToShare());
							//use the URL according to your social network and escape strings as needed
					}
				}
			</script>
			<style>
				div.RadSocialShare .sshDigg,
				div.RadSocialShare .sshDigg:hover
				{
					background-image: url('images/icon_16x16.png');
					background-position: 0 0;
				}
			</style>

This should be an additional property in the EmailSettings that will point to the port, so it can be used in the SmtpClient constructor: http://msdn.microsoft.com/en-us/library/system.net.mail.smtpclient.aspx

This can be done by exposing the email message that will be generated in an event (e.g. several fields in the event arguments - from, to, subject, body). There can be both client-side and server-side events to allow using different APIs. A client-side event should be cancellable to prevent the callback we generate by default. The issue with a client-side event is that the Captcha cannot be validated on the client, only on the server, so a client-side event can create an opportunity for spam and abuse.