User Rating: 0 / 5

Twitter

Share on Tumblr

Save this

There are a few common reasons why Gmail users may have trouble sending mail with Gmail's IMAP or POP feature. If you can't send mail, here's a troubleshooting checklist:
Are you able to log in to the Gmail web interface?
Visit http://mail.google.com to log in to Gmail. If you see a CAPTCHA (a security image with distorted letters), you'll need to log in before you can enable IMAP access. If you're locked out of Gmail, please wait one hour and log in to Gmail again.

Have you enabled POP or IMAP in Gmail?
Sign in to the Gmail web interface.Open the 'Forwarding and POP/IMAP' tab on your 'Settings' page, and configure IMAP or POP. After enabling this in Gmail, make sure you click 'Save Changes' so Gmail can communicate with your mail client.

Did you enable SSL for the SMTP server?
Make sure SSL is active for SMTP in your mail client. For more information, please review the configuration instructions for your specific client.

Did you set 'allow authentication' for the SMTP server?
Check that 'allow authentication' is active for the SMTP server in your mail client.

Did you enter the correct username and password?
Verify that your username is spelled correctly, and that you've entered '@gmail.com.' Google Apps customers should enter their entire email address including the domain name. Also, you should re-enter your password just to be sure it's correct.

Are you trying to send attachments?
As a security measure to prevent potential viruses, Gmail does not allow you to send or receive executable files that could contain damaging executable code. Also note that with Gmail, you can send and receive messages up to 25 megabytes (MB) in size.

Still can't send mail?
If you tried configuring your SMTP server on port 465 (with SSL) and port 587 (with TLS), but are still having trouble sending mail, try configuring your SMTP to use port 25 (with SSL).

Apple Mail users: At times, Mail may misinterpret your SMTP server settings. If you currently have 'smtp.gmail.com:username@gmail.com'; in the 'Outgoing Mail Server:' field of your settings, please try changing the field to 'smtp.gmail.com' and saving your settings.

Seeing duplicate Sent messages?
To understand settings that affect deleting and storing messages and drafts, please visit our recommended client settings.

Can you connect to the SMTP server?
To better diagnose the problem, you'll need to run a telnet test, which will check that your computer can contact our SMTP servers.

If you're running Windows Vista, you'll first need to enable the Telnet feature:

Click the Start button, then Control Panel, and Programs.
Click Turn Windows Features On or Off.
If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
In the Windows Features box, check the box labeled Telnet Client, and click OK. (It may take a few minutes for the installation to complete.)
To run the telnet test on a Windows computer:

Open the Start menu, and select Run.
Enter command in the Open: field, and click OK.
Enter 'telnet smtp.gmail.com 465,' and hit Enter, or if you're using Outlook 2007, enter 'telnet smtp.gmail.com 587' instead. (Does the information in the prompt window clear? If not, please note the message that appears.)
Close the prompt window.
To run the Telnet test on a Mac:

Click the Macintosh Hard Drive icon, and open the Applications folder.
Open Utilities, and select Terminal.
Depending on what port you're using to send, type 'telnet smtp.gmail.com 25' or 'telnet smtp.gmail.com 587' in the prompt window and press Enter.
If you receive an error message after performing step 3, your network administrator or security software has blocked access to our servers. We recommend contacting your local network administrator or Internet Service Provider (ISP) for more information.

User Rating: 0 / 5

Twitter

Share on Tumblr

Save this

The article appearing in the Standard Newspaper dated Tuesday 29th December titled ‘New Law tightens noose on Online hackers‘ starts as follows

You will now need your national identity card, birth certificate or passport before using the internet, the Communications Authority of Kenya (CA) has said.

You wonder whether this is sensational journalism trying to rope you in to read another of their articles. Then it gets worse, really, here is what one paragraph reads

In addition, CA wants service providers to retain data that will allow them to trace and identify the source of communication, the type of gadget used (phone, tablet or computer), the destination, the date, time and duration of the communication and even the geographical location of the sender and recipient of the message.

That’s right in the ball park of the Orwellian world in the book 1984.

1984

Before we even begin, how does CA even plan on getting the “geographical location of the recipient of the message”. also, birth certificates?

Where do I even start?

Let me start with the impracticability of implementing and enforcing these regulations.

How will CA monitor and ensure every establishment sticks to the rules? Full time CA officers stationed at their premises? Periodic review of all the logs and CCTV footage by an army of CA analysts stationed in a windowless room surrounded by banks of monitors?

Where will all the competent network administrators come from? Most of the ones around are ill-equipped to manage basic security requirements of a WiFi network. Trust me, breaking into most WiFi networks is embarrassingly trivial.

How do these establishments keep track of every client and internet activity that happens over their network, when they arrived and left, the devices they had, and who is who on the CCTV footage? Some form of Artificial Intelligence solution CA will provide? The logistics of this are a nightmare and the hardware expensive. Most corporate networks struggle with this exact scenario and they have teams of highly skilled personnel on their payroll.

Is there a data security standard that the establishments will have to comply with? What with them holding extremely sensitive data, our full names, ID numbers, browsing habits and so on. I read that they should hold system logs for a period not less than one year. Even forgetting the logistics , that scares the hell out of me. Your neighbourhood cyber or coffee place doesn’t exactly inspire confidence where information security is concerned. Come to think of it, the only logical explanation would be that this is a nefarious plot by CA to scare us off public internet access. That’s if we suspend all belief and decide to credit them with a level of aptitude betraying authors of such ill-thought out legislation.

I could go on and on, on the impracticability of implementing these regulations but I think you get the drift.

Let’s humour them a bit and assume that these regulations are practically implemented and enforced.

As a normal internet user, I visit a restaurant with free WiFi and present my National ID and let them inspect all the WiFi enabled devices I am carrying. The CCTV camera overhead zooms in to record my entry into the premises (we are assuming this will be correlated with my details and WiFi activity). A trained network administrator provides me with a username and password that I’ll use to login in to their WiFi network. Everything is going on smoothly as warranted by CA. I then order coffee and decide to check my mail. I’ve heard that I should use a (Virtual Private Network) VPN when using public WiFi to protect myself, so I connect to one. I then proceed to use the internet at my leisure.

That’s what a normal security conscious public internet user would do. With that single act of using a VPN, all that other foreplay of tracking me goes to naught. It will be as if I never browsed the internet from their network. Good luck to the network administrator and the army of CA suits even finding out what website I visited.

Let’s shake up things a bit. Let’s see how the person that CA is supposedly targeting would act, you are an up-to-no- good hacker. These are all scenarios that beat the system.

Just do everything by the book and then use a VPN or some anonymous browser or software like TOR. Easy!

…or

Mess with the registration process. You know those guards that require you to register before entering a building? I can assure you a lot of people leave fake details, maybe a fake second name and ID number. A hacker worth his salt would find a way to leave fake details with the resident coffee place registrar of public internet users.

…or

Go through the process until the hacker is allowed into the network. After that, the hacker gets into their system and does as he/she wishes. Next could be, alter CCTV footage and network logs, hijack another client’s credentials, or even exempt themselves from the monitoring solution in place. The possibilities are endless. We are talking of a hacker who knows their business, aren’t we?

…or

Go to a building, hijack the internet connection of a client in a neighbouring restaurant and now even the CCTV factor becomes moot. WiFi by design isn’t limited by walls, so they don’t have to be there physically.

The point is, these regulations will not deter a hacker, quite to the contrary, what it’s bound to do is to make them that bit more careful and harder to track.

The legal issues that will surround these regulations are likely to be crippling. From people’s right to privacy and protection of their data to establishments challenging the implementation. That’s a whole unopened Pandora’s box waiting to be happen.

It is quite honestly sad that several people in charge of providing direction in an esteemed institution such as the CA sat down, came up with this, presented it to the Director General and patted themselves on the back for a job well done.

It is sad that they either missed how illogical it all was or were deluded enough to believe that this was a legitimate solution.

It is sad that the average person out there could look at the regulations and immediately poke holes that challenge their core fabric.

Anyway, let’s assume that the people who came up with these regulations actually had a clue as to how to tackle the challenge of online hacking. Here’s some five ways they would go about it.

1. Enforce regulation requiring any network/system that handles public data to meet minimum security baselines. This would involve having the right people, security controls, awareness and periodic security assessments. This alone would keep out a majority of the hackers out there looking for easy targets.

2. Build a workforce of skilled information security personnel. A lot of capacity is needed in both government and private organisations in terms of skilled manpower. CA could lay the groundwork by introduction of relevant courses and guide the creation of syllabus and content with assistance from industry experts.

3. Educate the public and promote security awareness of the population at large.

4. Push for the implementation of the National Cyber Security Masterplan. This was meant to comprehensively address cyber security in the country in a wholesome approach but it gathers dust somewhere unimplemented.

5. Equip the Computer Incident Response Team (CIRT) with the necessary resources and build up the team to a high level of competence.

To sum it all up, hackers will attack from anywhere, from some remote Eastern Europe country, from their home, from a coffee place, and that is one area CA cannot control. They however can limit the attack surface. Make it hard for your network/system from being breached and your run of the mill hacker will move on to the next network, or in this case country.

An analogy for this is a bucket leaking water from multiple holes on each side with a multitude of crooks illegally collecting the water all around. Instead of fixing the holes, CA is trying to chase away one crook at a time, and it isn’t even doing it right

My advice to CA is to fix the holes and maybe then, we can start talking about taking the fight right to the hackers’ doorsteps. Leading us into a dystopian society is the wrong way to go about it.

source: http://www.afromum.com/public-internet-control-ca-wont-work-5-ways-actually-combat-cybercrime

User Rating: 0 / 5

Twitter

Share on Tumblr

Save this

My friend talked of writing stuff people look for to make it interesting. Not just people. He said. 

i write stuff I would like to read. 

I really looked for this. I searched alot. Am sharing because it helped me alot. 

The Mercury Mail package in xampp for windows is a great way to start sending emails from openemr or any open source CMS program placed in xampp. The configuration is easy, just need to follow the steps:

Benefits of Mercury Mail in openEMR

Easy to setup and integrated with XAMPP package
Appointment reminders will be sent automatically using Batchcom/Automatic_notification via cronjob
The patient reminder mails(alert reminders) will be sent automatically
Secure
Obtaining Mercury Mail

If not using XAMPP, but still want to use mercury mail, you can get it from here http://www.pmail.com/downloads_s3_t.htm

Steps of Configuration

1. After downloading Mercury Mail and installing it or if using Xampp, you can find it in C:/xampp/MercuryMail, run the program

2. First of all we disable the HTTP server of Mercury so that it doesn't conflict with the apache.

3. In the open Mercury panel, Go to "Configuration" -> "Protocol modules"

4. Disable the check "MercuryB HTTP web server" and also disable "Mercury IMAP4rev1 server" because It won't be required.

5. To be able to send external mail we have to disable "MercuryE SMTP end-to-end delivery client" in the same dialog and enable "MercuryC SMTP relaying client". Click "OK" and restart Mercury.

6. Now click on "Windows" in the top toolbar and click "Tile windows" and click save position. This will make the viewing easy and the Mercury Panel clean to work with.

7. Next Go to "Configuration" -> "Mercury core module", tab "General"

8. We want to send from localhost, therefore we check if "localhost" is the value of "internet name for this system" and adjust that if not.

9. All other settings stay the same as they are already configured, but we'll have a look to the checkboxes beneath:

Disable all but "Send copies of all errors to postmaster"
Check under the tab "Local domains" if the entry "localhost (local host or server) localhost (internet name)" is there, if not, add it.
Click "OK" and leave the dialog.
10. Next we focus on the MercuryS SMTP Server for outgoing emails.

11. Go to "Configuration" -> "MercuryS SMTP Server"

12. Choose the tab "General" and add a wonderful name for your SMTP server under "Announce myself as", simply fill in any name.

13. Under "Listen on TCP/IP port" fill in "25", that's the SMTP port

14. Add "127.0.0.1" to "IP interface to use", that's the local IP of your pc. With the IP of the pc within the network (192.168.0.X) it doesn't work.

15. Now we limit the access to the server so that only our local machine can access it:

Under "Connection Control" click on "Add restriction" and add the IP range from "127.0.0.1" till "127.0.0.1"
Now select "Allow connections".
Leave all checkboxes deselected
16.with a click on "OK" we quit the dialog and we're looking forward to the next one :)

17. Now let's configure the MercuryP POP3 Server.

18. Go to "Configuration"-> "MercuryP POP3 Server", select the tab "General"

19. "Listen on TCP port" -> "110" and "IP interface to use" -> "127.0.0.1"

20. Choose the tab "Connection control" and proceed as already written under 15 (see above)

21. That's it already, leave the dialog by clicking "OK"

22. Now we have the important one "MercuryC SMTP Client"

23. Go to "Configuration" -> "MercuryC SMTP Client"

24. To send mail to external addresses we need to have an external SMTP server. If you're renting webspace somewhere and have mail included then you normally have access to a SMTP server.

25. Enter the address of your SMTP under "Smart host name", for example "smtp.gmail.com"

26. Depending on the way you access the server fill the values under "Connection port/type":

for a "normal" SMTP that would probably be port 25 and "Normal (no SSL encryption)"
Most access SMTP via SSL (if using gmail), that would be port 465 and "SSL encryption using direct connection"
If you have other parameters simply try around a little :-)
27. We finally fill in the "Login username" and the "Password" that normally is supplied by your webhost or enter your gmail ID and password and we've nearly finished...

28. let's check the Mercury users that are normally pre-configured.

29. Go to "Configuration"-> "Manage local users"

30. There should be at least the users "Admin" and "postmaster", both with administrative rights. If not you have to add them.

31. Now we finished with Mercury, but we still need to configure PHP for sending mail with our scripts.

Configuring PHP

We search and open the appropriate php.ini, using XAMPP you find it under "xampp/php/php.ini" in newer version and under "xampp/apache/bin/php.ini" in older versions
we search for "[mail function]"...
we add/adjust the following:
1."SMTP = localhost"
2."smtp_port = 25"
3."sendmail_from = postmaster@localhost";
Save the php.ini and restart the Apache.
32. Now everything should work! But we'll test it first:

33. Within Mercury choose "File" -> "Send mail message" and send an email for testing purposes, I've chosen to send it to my googlemail account

33. Within the window "Mercury Core Prozess" we'll see our test mail at first:

"13:38:41 JOB XXXXXX: from postmaster@localhost (local) To: XXX@googlemail.com (non-local) (JOB XXXXXX) -OK"
The mail was received in Mercury and processed, after some seconds the window "Mercury SMTP client (relay version)" should show some actions:
1. "05 Jan 2008 13:39, Servicing job XXXXXX ...OK"
2. if you see this message, everything went fine and the mail was sent!
3. if you don't get the message you have to find out why, possible reasons could be:
1. wrong connection values for the SMTP server
2. SMTP server doesn't allow relaying (from your host)
34. Now we'll test the whole thing from a PHP script and we'll write a wonderful one-liner into a PHP file:

1. "mail('xxx@googlemail.com';, 'Mercury test mail', 'If you can read this, everything was fine!');"
2. call the PHP file within your browser, a command window should pop up shortly (or maybe not), it's from the fake sendmail of XAMPP, and focus back on Mercury:
1. the produre is the same as above only that the SMTP server receives the mail from php before everything else happens
2. you can watch this in the window "Mercury SMTP Server" and should see something like this: Mercury SMTP
35. If you get the error message "SMTP server response: 553 We do not relay non-local mail, sorry." while sending from PHP go to Mercury under MercuryS -> Connection Control -> "Uncheck Do not Permit SMTP relaying to non-local mail" an check this option. Should fix the problem

source: http://www.open-emr.org/wiki/index.php/Mercury_Mail_Configuration_in_Windows

User Rating: 0 / 5

Twitter

Share on Tumblr

Save this

January 2016 aint bad. All is good. Believe all is good and it'll be. btw, why the hell are you using the word bad and January in the same sentence? Ngoja tufike July then useme ivo.

Let's trust that our finances will be saved by some of these links down here.

They're all about school. Pesa ya shule ni muhimu. punguza mzigo. Kuna tu chances hapa ivi. Apply uone niaje.

Follow this link to post Scholarships Add a comment