Hi,

Here the placement for System Administrator – Abu Dhabi, UAE.

Position : System Administrator

No.Of Openings : 3

Experience : 3 years.

Qualification :

Location : Abu Dhabi, UAE.

Required Skill set :

• General understanding of Microsoft Windows Server OS and supporting systems including SMTP, Sites and directory object management.
• Knowledge of basic networking protocols such as TCP/IP, Kerberos and SNMP.
• Understanding of Server hardware and peripherals.
• Knowledge of Microsoft Windows based Operating Systems, networking best practices and troubleshooting techniques/
• Experience with Dell hardware and Dell Blade Servers.
• HP and/or Dell certification a plus.
• Hands on experience with a helpdesk ticket system. Remedy is preferred.
• Team oriented with a desire to succeed in a fast paced environment.
• Excellent customer service.

Would you be interested ?

Please send us your latest updated profile with contact nos.
current & expected salary details and joining time required toradha@kbsconsultants.com

You may also suggest this opening to your friends who may be interested.

Further Information:

KBS Consultants

Flat H,Kulothungan Apts,
No, 5 Natesan Road
Ashoknagar,
Chennai 600 083.
India
Phone: +91-44 2489 5341 / 2371 9622

Visit Our Sites:

International jobs: http://www.jobsearchworld.com/
SAP ERP Jobs : http://www.jobsvista.com/
Core Engineering Jobs : http://www.gotachance.com/
Technology Jobs : http://www.kbsconsultants.com/
India Jobs :http://www.kbsconsultants.org.in

Birkaç gündür müşterilerimizden outlook üzerinden mail atamadıkları şeklinde şikayetler alıyoruz. Ben de bu konuda bir yazı yazarak bu konuda bilgi vermek istedim.

Eğer sadece mail atarken sorun yaşıyorsanız, ki bizim müşterilerimiz bu konuda sorun yaşıyorlar, bunun nedeni büyük ihtimalle SMTP portunun yanlış ayarlanmasıdır. Eğer webmail üzerinden mail atabiliyorsanız, bunun nedeni kesinlikle SMTP portudur. Türk Telekom geçtiğimiz günlerde SMTP portunu 25 yerine 587 ile değiştirdi. Bunun nedeni maillere çok sık spam ve virüs gelmesi. Bunu düzeltmek için outlook’ta araçlar(tools) sekmesinden e-posta hesaplarını(email accounts) seçiniz. Burada çıkacak ekranda varolan hesapları görüntüle ve değiştiri seçiniz. Gelen ekranda hesabınızı seçiniz ve değiştir deyiniz. Karşınıza hesabınızla ilgili bilgiler gelecek. Bunlar doğru ise alttaki diğer ayarlar butonuna basınız. Yeni bir ekran karşınıza çıkacaktır. Burada gelişmiş sekmesini seçiniz ve 25 olan SMTP portunu 587 ile değiştiriniz.

Eğer buradaki port 587 ise değiştirmeyiniz. Bunun yerine giden sunucu sekmesinden “Gelen sunucum (SMTP) için kimlik doğrulaması gerekiyor” kutucuğunu işaretleyin. Bundan sonra tekrar mail atmayı deneyin. Büyük ihtimalle mail atabileceksiniz. Eğer hala atamıyorsanız SMTP portunu 25 yapıp bir kez daha deneyin. Yine olmazsa mail hesabınızı barındıran şirketle irtibata geçmenizi tavsiye ederim.

*Bu anlattıklarım Outlook 2003 için geçerlidir ancak diğer Outlook versiyonlarında da yaklaşık olarak aynıdır.

I basically have only three email accounts that I can choose to set up for my Evolution Email app in my new Ubuntu machine.

Two accounts are GMAIL and they are free accounts but graciously support POP and SMPT

The THIRD account is the paid account that comes with Verizon DSL.

They now require a port change from port 25 to port 587
which seems to be documented at the following link, but seems too complex for me to bother with.

https://help.ubuntu.com/community/Postfix

I AM able to change to port 587 in Outlook under Windows and utilize my Verizon email account.

In order to set up the two Gmail accounts, I had to experiment quit a bit to guess at the proper settings.

Whenever you launch EVOLUTION email client in Ubuntu, you may click on Edit-> Preferences and see the various email accounts that you are attached to.

The two TRICKY tags are SENDING EMAIL and RECEIVING EMAIL

For a Gmail account, in the RECEIVING EMAIL, you want to specify
Server: pop.gmail.COM
Username: (whatever your email user name like superman or wonderwoman if you prefer i.e. whatever name you chose to go in your address like MYFREAKINGNAME@gmail.com but leave out the @gmail.com part for this field and just enter the NAME)

Use secure connection: SSL encryption
Authentication type: PASSWORD

and you may experiment with checking the REMEMBER ME box to see which you might prefer.

The SENDING EMAIL is configured as follows for Gmail:

Server type: SMPT
Beneath this option check the box for SERVER AUTHENTICATION REQUIRED.

Server: smpt@gmail.com

Use Secure Connection: SSL encryption

Type: Login

And you may experiment with checking and unchecking the REMEMBER PASSWORD box to see what suits your need.

Username: (here you put your user name as above – e.g. superman, wonderwoman)

Google recently announced their most ambitious project to date called Google Wave. According to Google, Wave is “what email would look like if it was invented today.”

Compania de securitate IT, Avira Soft, anunta descoperirea unui vierme in campanii promotionale false McDonald’s si Coca Cola.

O noua schema de fraudare pentru utilizatorii de Internet: Creatorii de virusi trimit prin email cupoane false de reduceri in numele companiilor Coca Cola si McDonald’s.

Cupoanele sunt atasate emailurilor falsificate, ce vor sa para ca sunt trimise de catre McDonald’s sau Coca Cola. In timp ce emailul ce vrea sa para ca este trimis de McDonald’s aduce informatii despre un meniu redus care trebuie printat de catre recipient pentru a putea fii folosit, asa-zisul email de la Coca Cola face referire la un nou joc online. In momentul dezarhivarii fisierelor ZIP atasate, in loc sa gaseasca respectivele cupoane de reduceri sau jocul Coca Cola, utilizatorii vor primi un “cadou” neasteptat – infectarea calculatoarelor cu viermele Worm/McMaggot.A.

Viermele instaleaza o alte componenta, descarcata de pe net, pe care Avira o detecteaza ca BDS/McMaggot.A si care reprezinta un backdoor. Acest backdoor este folosit pentru a prelua controlul de la distanta asupra calculatorului si pentru a inregistra ceea ce se tasteaza pe tastatura. Viermele scaneaza computerul pentru a gasi adrese de email si le foloseste pentru a se trimite singur prin intermediul propriului motor SMTP de email.

sursa: securizare.ro

Para mais informações e para contratar, visite:    http://shop.bsrsoft.com.br/product.php?id_product=54

Recently I needed to setup several mailing lists to use in my current project. And I’ve found great solution for this – MailEnable.

MailEnable is a powerful mailing server. But I only needed the functionality related to the mailing lists:

And all above is available even in MailEnable Standard Edition (Free – unlimited domains/users).

Here’s a story written by the Abuse Coordinator at a small ISP, where he talks about a spambot infection that took over some workstations in their office.

What strikes me odd about this is how he found out they were infected, by finding his corporate public IP address listed in several blacklists.  If that happens, lots of damage has already been done.  Your systems by this point have been pumping out spam by the bucketload, and getting yourself off blacklists is a big time waster.  Secondly, the malware has had more time to spread internally.

If they had any kind of firewall log management and alerts set up, they would have immediately seen a spike in outgoing SMTP traffic and could have quarantined the single infected PC.  Eventually he did look at the firewall logs to get some clues, but why this sort of proactive log monitoring wasn’t in place at an ISP of all places is beyond me.

Postal is used to benchmark SMTP servers.
I am using it so that I can send mails continously to my test server and hence check if it is working properly. Hence this saves me from the pain of composing mails everytime I do some changes in the server and check if the changes I made is what I intended.

All I have to do is execute one command given below.

postal -m 100 -f test -t 5 192.168.31.100 users_mail

users_mail has the list of all the users in my test server.

Ubuntu Server 9.10 kurmus olmamdan henuz 1 hafta bile gecmemis olmasina ragmen bu sure zarfinda sisteme 3 kez format attim, Mac’e VMware uzerinde Ubuntu kurdum, CentOS kurulumu denedim, Ubuntu’yu iki kez daha kurdum. Anlasilan FTP sorunu bir dizi problemin sadece bir baslangiciymis!

Internet en buyuk yardimcim oldu bu surecte ve sonunda mukemmele yakin calisan bir sisteme kavustum. 1 gun boyunca test server’i uzerinden yayin dahi yaptim. Iste simdilik karsilastigim sorunlar ve workaround’lari:

→ Apache Virtual Host Problemi

Ubuntu’yu toplamda 3 kez kurmamin ana nedeni aslinda buydu. Bircok web sitesini ayni server’da tek IP uzerinde barindirdigim icin Apache’nin virtual host ozelligini kullanmam gerekti. IIS’te bunun icin ek hicbir islem yapmama gerek yokken Apache icin bir konfigurasyonlar dizisini modifiye etmem gerekiyordu. Ancak internetten buldugum ve Ubuntu Server 9.10 icin olan hicbir tutorial isime yaramadi. Her defasinda Apache coktu ve her seye bastan baslamam gerekti.

En son kurulumumda Webmin modulunu yukledim ve tum islemleri, kurulan bir web arayuzu araciligi ile yaptim. Baslarda bu bile sorunlara neden oldu ki ornegin bircok virtual host tanimlamama ragmen a.com b.com c.com, adrese ne yazarsaniz yazin hep ayni siteye yonlendiriyordu Apache kendiliginden. Bunun ise basit bir Port hatasi oldugunu gordum, Virtual Host yaratirken Port belirtmediginiz taktirde Apache en son kurulan virtual host’a yonlendiriyor adres ne olursa olsun. Sanirim bir tur Bug.

Linux icin olan bircok FTP programini denedim, bunlara VSFTPD, SFTP, VFTPD ve PURE-FTPD dahil. Pure-FTPD haric hepsinde yine Virtual User yaratma sorunu ile karsilastim. Ardindan Pure-FTPD haric hepsinde kullanici yaratabildim ancak bu sefer de login bilgilerini degistiremedim.

Pure-FTPD kurulumu sorunsuz gecti, istedigim kadar user olusturup kisisel ayarlarini degistirebiliyorum. Yalniz dun aksam 2 saatligine anlam veremedigim bir sorunla karsilastim: Gerek network icerisinden gerekse disaridan baglanti kuramiyordum. 425, Sorry Wrong Address hatasi aliyordum devamli. Gizemli bir sekilde birkac kez remove & reinstall isleminden sonra bu sorun da cozuldu.

En onemli problemlerden birisi: PHP ile mail gondermek. IIS’te bir turlu ustesinden gelemedigim problemdi. Ne yaparsam yapayim, ne kendi server’imdan ne de baska bir SMTP server‘dan email gonderemiyordum. Linux’ta yine boyle bir sorunla karsilasmaktan korkuyordum. Ancak PHP PEAR ile Google Apps‘deki hesabimdan SMTP ile mail gondermeyi basardim. Local olarak kendi SMTP server’imdan gondermeye vakit ayirir miyim bilmiyorum, onceki deneyimlerimden dolayi IP adresimin whitelist‘te olmamasindan dolayi bircok mailbox’a SPAM olarak gittigini biliyorum.

Sebarkanlah pengetahuan meskipun cuma sedikit. Semoga bermanfaat.

Bagaimana Mengirim Email SMTP menggunakan PHPMailer (download disini) Via Linux Server

Karena gw pusing membaca dokumentasi instalasi Pear di Linux Shared Hosting, akhirnya gw enggan dan mencoba mencari alternatif lain. Gw googling dapet yg katanya terbaik PHPMailer. Gw googling lg tutorialnya dan selalu gagal saat mencoba tutorial-tutorial yg diberikan orang lain. Pusing bercampur heran, napa org bisa, koq gw gagal, padahal tinggal copy paste doank. Akhirnya gw temuin sedikit masalah dlm tutorial mereka.

Mengirim email menggunakan SMTP via Windows mungkin gampang, tp gag semudah yg gw bayangin klo lewat Linux. Sebelumnya gw gag ngerti klo lewat Windows beda ama Linux. Setelah gw berhasil test di localhost, eh gag taunya gagal di server. Akhirnya temen ngetawain.

Setelah bekerja keras dgn kemampuan SMA (hahaha, maklum gag perna kuliah) dan dibantu Om Google tentunya, serta sesuai saran teman Programmer, Wahyu Primadi katanya Coba Dan Coba Lagi (ampe jidat melebar), gw berhasil ! Yeah! Hehe, uda bs ngopi dgn tenang sambil ngebul .

Langsung trik’nya :

Ekstrak PHPMailer lalu upload 2 file: class.phpmailer.php dan class.smtp.php

1. Disini gw mengambil contoh dr form Suggest di web gw. Ada 2 page yg gw gunakan yaitu: recommend.html utk form’nya dan index.php utk submit datanya. Anda bs mengganti form’nya dgn form html anda sendiri.

<html>
<head>
</head>
<body>
<form name="tellafriend" action="index.php" method="post" onSubmit="return checkfields()">
<div align="center"><center>
		<table border="0" cellpadding="10" cellspacing="0">
			<tr>
				<td> *Nama :</td>
				<td>
<input size="30" name="name" maxlength="45">
				</td>
			</tr>
			<tr>
				<td>*Email :</td>
				<td>
<input size="30" name="email" maxlength="45">
				</td>
			</tr>
			<tr>
				<td colspan="2">
<p align="center">Masukkan email teman kamu :</p>
				</td>
			</tr>
			<tr>
				<td>*Email :</td>
				<td>
<input size="30" name="friendmail1" maxlength="45">
				</td>
			</tr>
			<tr>
				<td colspan="2">
<p align="center">Email yg terkirim akan berisi data Nama dan Email kamu.<br />* = harus diisi</p><br />
<input onClick="validate();" type="button" value="Kirim" style="color:#000000">
				</td>
			</tr>
</table></center></div>
</form>
</body>
</html>

2. Mengambil data yg terkirim.

<?php

// Kelemahan tutorial yg gw dapet, saat page index di'view langsung, akan langsung mengirimkan email apabila kita
// telah menambahkan email address buat notifikasi kita. maka gw menambahkan $_POST function. Perhatikan nama
// setelah $_POST dan tanda ! jika tdk ada email yg didapat lalu dialihkan ke page form
if(!$_POST["email_yg_terkirim"]) {
	header("Location: /recommend.html");

// Disini jika data email didapat maka akan membuat PHPMailer baru
} elseif($_POST["email_yg_terkirim"]) {

// kode PHPMailer yg gw tambahkan sedikit dr tutorial org. Mgk mereka bisa berhasil krn lewat Windows. Akhirnya gw
// tambahkan require("class.smtp.php");
	require("class.phpmailer.php");
	require("class.smtp.php");

// Membuat email baru. Untuk pengguna aplikasi Gmail masukkan username dgn penuh, kamu@domainkamu.com dan buat otentifikasi secure ssl, host smtp.gmail.com, port 465
	$mail = new PHPMailer();

    $mail->IsSMTP(); // send via SMTP
	$mail->SMTPSecure = "ssl";                 // sets the prefix to the servier
    $mail->Host = "smtp.gmail.com"; // SMTP servers
	$mail->Port = 465;                   // set the SMTP port
    $mail->SMTPAuth = true; // turn on SMTP authentication
    $mail->Username = "kamu@domainkamu.com"; // SMTP username
    $mail->Password = "passwordkamu"; // SMTP password

    $mail->From = "kamu@domainkamu.com";
    $mail->FromName = "namakamu";
    $mail->AddAddress("$_POST[email_yg_terkirim]");
    $mail->AddAddress("notifikasi_emailkamu");
    $mail->AddReplyTo("$_POST[email_pengirim]");

    $mail->IsHTML(true); // send as HTML

    $mail->Subject = "subject_form_kamu";
    $mail->Body = "pesan_form_kamu";
}

    if(!$mail->Send())
    {
    echo "Message did not sent";
    echo "Mailer Error: " . $mail->ErrorInfo;
    exit;
    }

// Dialihkan kembali ke page form setelah 5 detik
    header("refresh:5;url=recommend.html");
	echo "<div align=\"center\">Message has been sent<br />Thank You<p>Redirecting to previous page...</p></div>";

?>

Selamat mencoba! Tolong betulkan jika ada salah atau lubang sekuriti yah.

Bagi warga cluster nirwana yang sudah mendapatkan email, anda bisa mengakses email tersebut dengan beberapa cara yaitu:

1. melalui browser dengan mengakses url http://webmail.clusternirwana.com

2. Melalui email client seperti Microsoft Outlook dengan parameter sebagai berikut:

• Incoming Mail Server: pop.gmail.com port:995 (SSL) atau
• Incoming Mail Server: imap.gmail.com port:993 (SSL)
• Outgoing Mail Server: smtp.gmail.com port: 465 atau 587 (TLS)
• User Name: username@clusternirwana.com
• Password: password email anda.

3. Melalui ponsel anda dengan menggunakan parameter di point no.2, namun jika ponsel anda mendukung push email (seperti Sony Ericsson P1i) maka anda bisa menggunakan IMAP sebagai incoming mail server. Karena dengan menggunakan IMAP maka kemampuan ponsel anda akan setara dengan menggunakan fitur Blackberry Connect  pada ponsel anda. Ini akan menguntungkan jika anda tidak terlalu menerima banyak email setiap harinya, karena anda cukup membayar biaya koneksi GPRS/3G/3.5G untuk biaya email anda dibandingkan berlangganan Blackberry Connect yang relatif cukup mahal hanya untuk fasilitas email, karena di ponsel yang mempunyai fitur blackberry connect, langganan BIS anda hanya bisa digunakan untuk email sedangkan untuk browsing dan chatting anda akan tetap dikenakan biaya koneksi GPRS/3G/3.5G. Keuntungan yang lain battery anda akan lebih hemat, karena jika menggunakan fitur blackberry connect fitur ini cukup boros dalam penggunaan sumber daya battery anda, selain itu anda sudah tidak perlu  menggunakan program 3rd party seperti SEVEN untuk membuat ponsel anda mampu mengimplementasikan push email.

Iseng …, mungkin lebih tepatnya begitu.

Barusan register domain clusternirwana.com, dan sampai saat ini belum ada ide mau diapakan domain tersebut. Mungkin ada saran atau ide dari warga cluster ?!!
Yang pasti tadi udah di daftarkan ke Google Apps, jadi udah bisa dipakai untuk register email dengan domain clusternirwana.com

Bagi warga cluster nirwana yang butuh email gratis dipersilahkan menghubungi saya, khusus untuk 50 pendaftar pertama. Dengan quota mencapai 7 GB, saya rasa lebih dari cukup untuk pemakaian sehari-hari, ditambah ada fasilitas IMAP, POP3 dan SMTP maka email ini bisa di setting di hp sebagai alternatif email, juga sebagai identitas anda yang seorang warga cluster nirwana…

Microsoft decided to remove the SMTP server feature from the Vista operating system (all versions).

This of course is a real problem for those of us who are developers as we can no longer use the local SMTP server to send emails from our applications as we are developing and testing them.

Luckily there are a few applications out there which we can use instead. Here are just a few alternatives for use as your local SMTP server for development.

Free SMTP Server from SoftStack.com: This is a good alternative as it is extremely easy to setup and use. But on the downside it is limited to 10 emails a day unless you purchase the full version.

If you need to be able to send more than just 10 emails during a day Pegasus Mail provides a free SMTP server titled Murcury SMTP Server.

The SMTP protocol considers the whole of the message (the headers and the body) to be payload, part from adding to the headers an MTA (Message Transfer Agent) should not process the headers.
This means that, in many cases, you can send a customised SMTP message that has totally bogus values for the To and From fields (and I’m sure the SPAMmers are well aware of that!).

However, what I learned yesterday is that these fields are required to be in the correct format for email addresses.
So this is not valid SMTP:

To: "Unrelated text"

But this is:

To: "Unrelated text" <a.totally.made.up.address@a.totally.made.up.domain>

The actual list of recipients that the message is to be delivered to is sent in a completely separate part of the SMTP communication.
It is the job of the MUA (Mail User Agent – your mail client) to generate this list from the To, CC and BCC fields in your mail.

Rather an obscure things, but there you go…

Symptoms
SMTP server reports authentication error despite correct credentials configured. It happens when dynamic addressing is in use.

Cause
There was a problem with Narawen Inox POP3 Connector. It was not sending authentication details to SMTP server when dynamic addressing was in use.

Solution
Upgrade to latest release of Narawen Inox POP3 Connector.

Applies to
Narawen Inox POP3 Connector 5.2 SR1 (2008-02-05)
Narawen Inox POP3 Connector 5.2 (2007-11-14)
Narawen Inox POP3 Connector 5.1 SR1 (2006-09-25)
Narawen Inox POP3 Connector 5.1 (2006-06-14)
Narawen Inox POP3 Connector 5.0 (2005-11-10)

http://smtp25.blogspot.com/2007/12/530-571-client-was-not-authenticated_25.html

Cause:

The anonymous users do not have permission on the “Default receive connector.”

• Click on Server configuration
  
• Click on Hub Transport, select default receive connector and go to properties
  
• Click on Permission group
  
• Tick the check box where is says “Anonymous users”
  

Now try the telnet on port 25 to your mail server, everything should work.

http://support.microsoft.com/kb/323350

Test the SMTP Service

To test the SMTP service, follow these steps:

1. On a computer running Windows Server 2003, type Telnet at a command prompt, and then press ENTER.
2. At the telnet prompt, type set LocalEcho, press ENTER, and then type open <machinename> 25, and then press ENTER.

   The output resembles the following:

   220 computername.microsoft.com ESMTP Server (Microsoft Exchange Internet Mail Service 5.5.2651.58) ready

3. Type helo me, and then press ENTER.

   The output resembles the following:

   250 OK

4. Type mail from:email@domain.com, and then press ENTER.

   The output resembles the following:

   250 OK - mail from <email@domain.com>

5. Type rcpt to:youremail@yourdomain.com, and then press ENTER.

   The output resembles the following:

   250 OK - Recipient <youremail@yourdomain.com>

6. Type Data, and then press ENTER.

   The output resembles the following:

   354 Send data.  End with CRLF.CRLF

7. Type Subject:This is a test, and then press ENTER two times.
8. Type Testing, and then press ENTER.
9. Press ENTER, type a period (.), and then press ENTER.

   The output resembles the following:

   250 OK

10. Type quit, and then press ENTER.
    

    The output resembles the following:

    221 Closing Port / Mail queued for delivery

Sending email using Java is not a difficult task and it’s just about writing few lines of codes. But when you are writing such an application, you’ll end up with lot of exceptions obviously. There are lots of reasons for that, but as my opinion, wrong email configuration settings would cause the exceptions.

If you need to write a Java application to send an email, you need an outgoing mail server such as SMTP (Simple Mail Transfer Protocol) server. There are many SMPT servers out there, but in order to send an email most servers require authentication (You have to have an account in your SMTP server and you must know account credentials). There exist free SMTP servers without authentication, but I’m not sure about their reliability and Quality of Service (QoS).

At the authentication process, most developers fail due to bad configurations. There are several configuration settings should be set in your code, before you submit the message to the SMTP server.

To demonstrate this settings, I’ll create a Java application from the scratch and it will use Gmail as the outgoing SMTP server (You can use any SMTP server with valid credentials. But here I used Gmail because I’m addicted to Google!).

You can download the complete source code and required libraries here. I developed it using NetBeans IDE, but you can use any IDE to proceed.

Prerequisites

• JavaMail API (http://java.sun.com/products/javamail) libraries. (No need to download the libraries. I’ve included them in my sample application).
• Valid Gmail (http://www.google.com/gmail) account. (You must know the user name and the password)

Source Code

package com.dunithd.jmail;

package com.dunithd.jmail;

import javax.mail.*;
import javax.mail.internet.*;
import javax.mail.internet.MimeMessage.RecipientType;

import java.util.*;

/**
 * Simple Class to send an email using JavaMail API (javax.mail) and Gmail SMTP server
 * @author Dunith Dhanushka, dunithd@gmail.com
 * @version 1.0
 */
public class GmailSender {

    private static String HOST = "smtp.gmail.com";
    private static String USER = "your_username@gmail.com";
    private static String PASSWORD = "put_your_password_here";
    private static String PORT = "465";
    private static String FROM = "put_from_address_here";
    private static String TO = "put_to_address_here";

    private static String STARTTLS = "true";
    private static String AUTH = "true";
    private static String DEBUG = "true";
    private static String SOCKET_FACTORY = "javax.net.ssl.SSLSocketFactory";
    private static String SUBJECT = "Testing JavaMail API using http://dunithd.wordpress.com";
    private static String TEXT = "This is a test message from my java application. Just ignore it";
    public static synchronized void send() {
        //Use Properties object to set environment properties
        Properties props = new Properties();

        props.put("mail.smtp.host", HOST);
        props.put("mail.smtp.port", PORT);
        props.put("mail.smtp.user", USER);

        props.put("mail.smtp.auth", AUTH);
        props.put("mail.smtp.starttls.enable", STARTTLS);
        props.put("mail.smtp.debug", DEBUG);

        props.put("mail.smtp.socketFactory.port", PORT);
        props.put("mail.smtp.socketFactory.class", SOCKET_FACTORY);
        props.put("mail.smtp.socketFactory.fallback", "false");

        try {

            //Obtain the default mail session
            Session session = Session.getDefaultInstance(props, null);
            session.setDebug(true);

            //Construct the mail message
            MimeMessage message = new MimeMessage(session);
            message.setText(TEXT);
            message.setSubject(SUBJECT);
            message.setFrom(new InternetAddress(FROM));
            message.addRecipient(RecipientType.TO, new InternetAddress(TO));
            message.saveChanges();

            //Use Transport to deliver the message
            Transport transport = session.getTransport("smtp");
            transport.connect(HOST, USER, PASSWORD);
            transport.sendMessage(message, message.getAllRecipients());
            transport.close();

        } catch (Exception e) {
            e.printStackTrace();
        }

    }

    public static void main(String[] args) {
       GmailSender.send();
       System.out.println("Mail sent successfully!");
    }
}

Environment Properties

When writing the application, you have to set some Environment Properties that are used by the JavaMail APIs. The JavaMail javadocs contain additional information on properties supported by JavaMail.

You can use java.util.Properties class to set these properties.

• mail.smtp.host: Specifies the protocol-specific default Mail server. In your application, set this property to smtp.gmail.com
• mail.smtp.user: Specifies the protocol-specific default username for connecting to the Mail server. In your application, set this property to your Gmail username.
• mail.smtp.auth: Specifies whether host requires authentication or not. In our application, set this property to true.
• mail.smtp.debug: Specifies the initial debug mode. Setting this property to true will turn on debug mode, while setting it to false turns debug mode off. If you need deeper diagnosis, set this to true.
• mail.smtp.port: Specifies the port that is used by SMTP server. In your application, set this to 465.
• mail.smtp.starttls.enable: This is the most important one. If you miss this, you’ll definitely get an error. Most SMTP servers support SSL (Secure Socket Layer) connections which can be used for secure login to the server. They use STARTTLS command (see RFC 2487 and RFC 3501) to switch the connection to be secured by TLS.
  Use of the STARTTLS command is preferred in cases where the server supports both SSL and non-SSL connections. This SSL/TLS support in JavaMail works only when JavaMail is used on a version of J2SE that includes SSL support.
  The STARTTLS support is available in the standard “IMAP” and “SMTP” protocols, but must be enabled by setting the appropriate property, mail.imap.starttls.enable or mail.smtp.starttls.enable, to “true”. When set, if the server supports the STARTTLS command, it will be used after making the connection and before sending any login information.

If everything goes fine, you’ll see an output like this.

Output of the application

Notes

This application cannot be used in a network that uses a proxy server. You must have a direct connection to the internet otherwise you’ll get UnknownHostException.

UnknownHostException

In my next post, I’m gonna explain you how to send an email with an attachment.

Download source code and required libraries here.