Sending Email: Difference between revisions

(6 intermediate revisions by 2 users not shown)

Line 1:

<indicator name="Faults">[[File:Menu-email.svg|link=:Category:Email|30px|Back up to the Email Category]]</indicator>

__NOTOC__

==Overview==

We provide outgoing email services to:

*Customers using us as their internet connection. (No authentication required, no domain required.)

*Customers using us for their internet connection (eg DSL, L2TP, FTTP etc). (No authentication required, no domain required.)

*Customers with a domain and email services (authentication required if not using us for your internet connection)

Line 18:

Line 17:

!Port

|587

|port 25 may be removed in the near future

|You can use 25 if needed.

|-

!Security

Line 25:

Line 24:

|-

!Authentication

|Recommended

|Optional

|If you are sending from outside an AAISP connection, then you will need to use your mailbox username and password to authenticate. You will also need to enable STARTTLS

|}

Line 36:

Line 35:

==Encrypted Communication==

You should use STARTTLS (encrypted link) to connect to our mail servers for sending email or the submission port. These are usually options on most applications in the same place as you configure the mail server. If you are concerned about security you may like to look in to [[http://aa.net.uk/kb-pgp.html PGP]] encrypted email which would allow you to send emails only the recipient can ever read.

You should use STARTTLS (encrypted link) to connect to our mail servers for sending email or the submission port. These are usually options on most applications in the same place as you configure the mail server. If you are concerned about security you may like to look in to [http://aa.net.uk/kb-pgp.html PGP] encrypted email which would allow you to send emails only the recipient can ever read.

==Webmail Accesss==

Line 50:

Line 49:

See [[Outgoing Spam Restrictions]]

==Retry==

If a message cannot be delivered at the first attempt - eg if the remote mail server is busy or gives a 'soft' fail etc we will retry as follows:

* For the first 6 hours, we'll try every 5 minutes

* For the next 16 hours we will retry around every hour

* Thereafter we will retry every 6 hours for the next 4 days

* after 4 days we will give up and bouncing it back

During this time, we will send automated emails saying that the email is delayed.

If the remote server outright rejects message or if there is some other permanent error, we will bounce the message back right away and not retry.