@@ -102,7 +102,7 @@ By deafult, all configuration happens in ``config/``
102102^^^^^^^^^^^
103103
104104This file is used by Salmon during start-up to configure the daemon with
105- various things, such as starting the ``LMTPReceiver ``. It's a bit like the
105+ various things, such as starting the ``AsyncLMTPReceiver ``. It's a bit like the
106106``wsgi.py `` file that Python web apps have. If you want to use a different boot
107107module, you can specify it with the ``--boot `` argument. E.g. to use
108108``myapp/othermodule.py ``, do:
@@ -144,18 +144,18 @@ much in the same way as you host a WSGI application behind Apache or Nginx.
144144
145145As seen above, a new Salmon project will start a LMTP server that listens on
146146``localhost:8823 ``. You can go into ``config/settings.py `` and change the host
147- and port Salmon uses. You can also switch out ``LMTPReceiver `` for
148- ``SMTPReceiver `` if you require Salmon to use SMTP instead.
147+ and port Salmon uses. You can also switch out ``AsyncLMTPReceiver `` for
148+ ``AsyncSMTPReceiver `` if you require Salmon to use SMTP instead.
149149
150150.. warning ::
151151
152152 Due to the way Salmon has been implemented it is better suited as a LMTP
153- server than a SMTP server. ``SMTPReceiver `` is unable to handle multiple
153+ server than a SMTP server. ``AsyncSMTPReceiver `` is unable to handle multiple
154154 recipients in one transaction as it doesn't implement the nessessary
155155 features to properly implement this part of the SMTP protocol. This is a
156- compromise ``SMTPReceiver `` makes in order to allow users more freedom in
156+ compromise ``AsyncSMTPReceiver `` makes in order to allow users more freedom in
157157 what they do in their handlers.
158158
159159
160- ``LMTPReceiver `` is unaffected by this issue and implements the LMTP
160+ ``AsyncLMTPReceiver `` is unaffected by this issue and implements the LMTP
161161 protocol fully.
0 commit comments