Author Archive
server VPS baru telah tersedia
by admin on Mar.09, 2010, under News
Dear All,
Saat ini kami telah menambah 4 buah server baru yang akan difungsikan untuk melayani pelanggan vps. Server ini dilengkapi dengan quad core cpu, 16 GB ram ECC dan raid 5 harddisk. Jenis virtualisasi yang kami gunakan pada server ini adalah xen hypervisor.
Bantuan Pelayanan dan Informasi
by admin on Jan.26, 2010, under News
Pelanggan YTH,
Untuk mempermudah komunikasi, trouble shoot dan lainnya silahkan untuk mengubah kontak kami menjadi :
Yahoo, MSN, AIM, Google Talk dan Skype dengan ID : cybernoc2k3
Untuk memantau kondisi terakhir dari status server dan jaringan dapat dilihat di http://www.twitter.com/indovps
Regards
452 – Requested action not taken – Insufficient storage. (also called SMTP Error 4.5.2)
by admin on Jan.26, 2010, under Mail
SMTP Error 452 : The ISP server’s disk system has run out of storage space, so the action had to be cancelled. Unless you are with an ISP which is so slack that they have not implemented Disk Full Alerts, this error usually indicates that your ISP’s mail server is overloaded from too many messages. This can happen even to the best ISPs when, for example, there have been problems and none of the ISP’s customers could send mail; as soon as the problems are fixed there is almost always a situation where thousands of users and organizations are trying to send mail all at the same time, and those numbers can occasionally result in the ISP’s mail servers’ hard disks temporarily filling up, with SMTP Error 452 being the result.
The next attempt to send by your server may prove successful.
SMTP Error 452 : Most ISPs mail servers impose a maximum number of concurrent connections that client’s mail servers can attempt to make, and they usually also have a limit on the number of messages that are sent per connection. With business customers these maximums are rarely reached, if ever. Nevertheless, If you have a lot of messages queued up, for example as a result of the connection to your ISP going down for a significant amount of time (and you have hundreds of users in your organization, or it happened just as you were about to send that large mailshot!), there could be a situation where the output of messages from your server goes over the maximum number of messages per connection allowed by your ISP. This is another case where the ISP’s server may issue a 452 SMTP error. As above, the next attempt to send by your server may prove successful.
SMTP Error 452 : This error can also be indicative of a problem on your own mail server.
Here is an example of an SMTP 452 error : “”452 Out of memory”
451 – Requested action aborted – Local error in processing. (also called SMTP Error 4.5.1)
by admin on Jan.26, 2010, under Mail
SMTP Error 451 : The action has been aborted by the ISP’s server. “Local” refers to the ISP’s server. This error is usually due to overloading at the ISP from too many messages or transient failures. Typically some [hopefully] temporary event prevents the successful sending of the message. The next attempt to send by your server may prove successful.
If this error keeps occurring to the point that it has effectively lost its transient nature and has become ….. frequent (!!), then the problem is at your end and you should check your own mail server (if you email out of a corporate network), communications on your side (router, server network card), or inform your ISP if your mail server relays through your ISP or if you are a home user emailing out through Outlook, Outlook Express, Windows Mail, or similar email program.
Example of typical SMTP Error 451 return messages :
“SMTP error 451 Unable to complete command, DNS not available or timed out” or “451 Domain of sender address does not resolve” or “451 Error getting LDAP results in map”.
450 – Requested action not taken – The mailbox was unavailable at the remote end. A secondary SMTP error code may follow “450” to refine the reason for the failure to transmit the message, e.g. “SMTP Error 450 (also called SMTP Error 4.5.0)
by admin on Jan.26, 2010, under Mail
SMTP Error 450 : The server could not access the mailbox to deliver the message. This could be caused by a process on the remote server tidying up the mailbox, or the remote mailbox could be corrupt, or the remote mailbox may be stored on another server which is currently offline, or the network connection went down while sending, or the remote mail server does not want to accept mail from your server for some reason (IP address, blacklisting, etc..). In general SMTP Error 450 is a transient error at the remote end (the destination), or at one of the servers en route to the remote end, and should induce your mail server to retry after it’s preset retry interval.
Example of an SMTP Error 450 reply message : “450 Please try again later”.
SMTP Error 450 is often followed by a second SMTP error code to refine the reason for the email not reaching its destination. For example : “SMTP Error 450 5.2.3 Msg Size greater than allowed by Remote Host”. When that is the case and If the error message is not as clearly worded as in this example, then simply search this document for the secondary error code. In this case searching this document for SMTP Error 523 or SMTP Error 5.2.3 would yield an explanation identical to the wording above.
