If you decided to use Google as your mail server and already set up it in a way like:
- Set the SMTP server name to smtp.gmail.com
- Set the username to your google email address
- Enter your password
- Set SMTP Port to 465
- Set SMTP Encryption to TLS
yet when I tried to send email I was receiving “internal server error ” msgs.
In the error log I see “Premature header…”
After spending hours on research I found that on your server you should have outgoing port 465 not blocked by the firewall.
We all remember the bad times with Microsoft killing its competition and not caring about it customers. So Google came and we fell in love with their "free" applications opens source etc…
As you can notice recently to breath you have to have a google email account. For example if you buy a phone from T-mobile you need to have internet and open a gmail account.
A month ago Google suspended my adsense account for Invalid Clicks they provided no explanation just suspended the account by accident just about when the payout was due…
Unfortunetly I hate google as they are getting more arrogant as they grow.
If anyone has another suggestion of other advertising companies Please share with us.
Yak HATE GOOGLE SO MUCH NOW>>>> 🙂
General Information [ ^ ]
.htaccess Definition1 [ ^ ]
Apache server software provides distributed (i.e., directory-level) configuration via Hypertext Access files. These
htaccess files enable the localized fine-tuning of Apache’s universal system-configuration directives, which are defined in Apache’s main configuration file. The localized
htaccess directives must operate from within a file named
htaccess. The user must have appropriate file permissions to access and/or edit the
htaccess file. Further,
htaccess file permissions should never allow world write access — a secure permissions setting is “644”, which allows universal read access and user-only write access. Finally,
htaccess rules apply to the parent directory and all subdirectories. Thus to apply configuration rules to an entire website, place the
htaccess file in the root directory of the site.
Commenting .htaccess Code [ ^ ]
Comments are essential to maintaining control over any involved portion of code. Comments in
htaccess code are fashioned on a per-line basis, with each line of comments beginning with a pound sign
#. Thus, comments spanning multiple lines in the
htaccess file require multiple pound signs. Further, due to the extremely volatile nature of htaccess voodoo, it is wise to include only alphanumeric characters (and perhaps a few dashes and underscores) in any
Continue reading “.htaccess Guide” »