22nd September 2008 11:12 AM
When attemping to send email, using smtp.aquiss.net, you are unable to send email, but instead presented with a Error 550 : Relay not permitted message similar to the examples (fig 1) and (fig 2) given below.
This is normally the result that you are not currently connected to Aquiss when attempting to send email.
Example (fig 1)
The rejected e-mail address was 'test @ testdomain.com'. Subject 'Example', Account: 'Aquiss Account', Server: 'smtp.aquiss.net', Protocol: SMTP, Server Response: '550 relay not permitted', Port: 25, Secure(SSL): No, Server Error: 550, Error Number: 0x800CCC79
Example (fig 2)
Your message did not reach some or all of the intended recipients.
Sent: 22/09/2008 11:53
The following recipient(s) could not be reached:
'test @ testdomain.com' on 22/09/2008 11:53
550 relay not permitted
How do I correct this problem?
There really is only one solution that will fix this problem. In order to send email via smtp.aquiss.net you must be connected directly to Aquiss via one of our broadband or dial-up connections, we confirm this by checking your IP Address in real-time. Upon sending via our mail servers, your connection is checked to ensure you are indeed an active customer with ourselves.
Therefore if your attempting to send email via our servers; and your not currently connected to Aquiss or no longer a customer, you will get relaying denied messages.
Is there anyway around this problem?
Generally we see this problem occuring more often when customer are using a mobile phone or PDA device. You will need to ask your operator for their SMTP server address which should resolve the ability for you to send email whilst on the move.
If your not currently an active Aquiss customer, be it you have recently departed or more likely joining us from another company, you will need to use the SMTP server as supplied by that company.
Why do you restrict SMTP (sending of email) in this manner?
The short answer really is to stop spam email being sent via our servers from unknown sources or customers. If spam is being sent, we will know instantly which customer this originates from.
However, all ISPs these days will restrict in some manner, with the very same aim to reduce spam. We feel that our approach is easier on our customers, without the need for extra settings being applied during account setups, such as username and passwords via the SMTP Authenicated approach to SMTP relaying.
Do you offer an SMTP Authenication option?
Not at the present time with our Broadband or Dial-up inclusive services. However, our dedicated Plesk based hosting solutions do offer SMTP Authenication as part of the standard service.