A Python Mail Server

Not sure if this is a proper place to ask for questions/help (see #45).

I'm now wondering how I can just ignore emails which are sent to some other host than what I've specified.

My undeliverable queue fills up with some spam that my server receives. That spam is designated to some weird email addresses with weird hosts. I'd like just ignore the mail if the "To" host isn't one of my accepted host names (I have a few of them). Is there a place to list these valid hostnames or are they automatically parsed from the used handlers? And how then ignore mail that doesn't match these host names?

Anyway, thanks a ton for working on this Lamson fork, this is great.

Sorry but you can't just fork a project at some random point and declare it licensed contrary to what I want. I own copyright and that means if I want my BSD license then that's what you use.

Basically you ripped out my license modifications which then means you took away the rights I have to give you rights.

I'd appreciate it if you'd put the license back the way it is supposed to be. It's that way for a reason.

This commit fixes a regression in 4855991 which is raising an AttributeError on both 2.7.5 and 3.6.5.

$ pyenv shell 3.6.5; python -c "import email; assert email.header.Header"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
AttributeError: module 'email' has no attribute 'header'

I try to use salmon in my django project (1.7>=), and when I try to access django ORM in salmon router code, it raises AppRegistryNotReady: Models aren't loaded yet.. Any suggestion how to use django & salmon? Popular answers from google is os.environ.setdefault("DJANGO_SETTINGS_MODULE", "http_handler.settings") and django.setup() but it does not work for salmon projects.

I'm trying to set up a very simple mail server: listen to emails for a particular domain, determine whom it should be sent to based on the address and send the email using ISP mail server as a relay. A very simple mailing list server.

This was very easy with Lamson. With Salmon, there was a bug(?) in SMTPReceiver that only one recipient was handled. With LMTPReceiver (which is now the default), this is fixed but now there is suddenly the nightmare of setting up a mail server gateway in front of Salmon. The main reason to use Lamson/Salmon - at least for me - was to avoid setting up and maintaining these huge massive complex mail servers and just have a very simple process running and doing the simple thing. Or perhaps I'm missing something and it should be as easy with Salmon too somehow? I'm a bit confused on how Salmon is supposed to be used.. The only instructions I found were: "Salmon is best deployed behind another mailserver such as Postfix or Sendmail - much in the same way as you host a WSGI application behind Apache or Nginx."

For these reasons, I would really appreciate some help on how to set up Salmon so that it works as a mail server. If that really requires some mail server gateway in front, then it'd be great to have some instructions or at least pointers on how to achieve this in a very lightweight way. I don't need mailboxes, I don't need mail sending server (I use my ISP mail server as a relay). If you have any ideas how to proceed, I'd be really happy to hear. If I get it working, I could perhaps write some instructions in case that's useful for other users. Anyway, thanks for this great package and your efforts!

QueueReceiver is quite bad at handling a large influx of messages in a reasonable amount of time.

Implementation-wise QueueReceiver is the only receiver class that doesn't use threading. Though it's quite a simple class, I think it's also what makes it slow: we're waiting for each message to be processed before fetching another.

Investigate how threading could improve performance and how badly it would complicate code.

Thanks for this great project! I noticed there hasn't been a release in a while, last one is version 2, from 20 Jun 2014. Almost three years old.. Would you like to make a new release? Or is the state after every commit equally stable and ready for production? If you'll make releases, may I suggest using semantic versioning so it's easy to notice, for instance, if the API changes in possibly backwards incompatible ways.

It seems that if the list of recipients contains several email addresses that Salmon needs to handle, it only handles one and delivers the mail there. At least I've been trying to send one email to several recipients and only one of them receives it each time.

Fixes #7

• Try to avoid easy_install
• Remove win32 "support" - it was untested and couldn't be used in production anyway.
• Mock chardet rather than the string object
• Don't use reserved words
• Do binary file reading properly
• SMTPD messages are slightly different between Python 2 and 3
• Put test states.db in a folder that gets cleaned between test runs
• Depending on what version of Python we're using, reload could in one of three places.
• Use more modern try: except: syntax
• Print is a function in Python 3

I'm in the process of converting the old Lamson docs (from the old gpl3 version that salmon was forked from ) into rst in the form of a sphinx project so it can be deployed as a rtd project or through github sites.

I still need to do some tweaking and cleanup to match changes in salmon since the fork but before I put too much more work into tweaking stuff, I wanted to see if there's an interest in such a PR

Hi ✋ !

I am planning to develop an app which needs to act on emails receiving and have some questions about production deployment with Salmon.

1. Do you have some guidelines or documentation about configuring Salmon behind Postfix or Sendmail as advised ?
2. Is it possible to have a Django app running behind Nginx on a server and a Salmon process running behing Postfix or Sendmail on the same server with Salmon and Django interacting with each other ? (I have seen a quick demo code in Salmon documentation about this)

Thank you in advance,

There are small typos in:

• README.rst
• docs/conf.py
• salmon/commands.py
• salmon/routing.py
• tests/test_integration.py
• tests/test_server.py

Fixes:

• Should read under rather than uner.
• Should read that rather than shat.
• Should read only rather than onlly.
• Should read module rather than modiule.
• Should read destroyed rather than destoryed.
• Should read configuration rather than configureation.
• Should read affected rather than afffected.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Hi,

Would you be interested in a PR that adds DKIM signatures to salmon? This is somewhat related to #72 but its use case is different (it allows mails originating from salmon to contain correct signatures for their domain).

  ======================================================================
  FAIL: test_queue_receiver_sleep (tests.test_server.ServerTestCase)
  ----------------------------------------------------------------------
  Traceback (most recent call last):
    File "/Users/runner/hostedtoolcache/Python/3.6.15/x64/lib/python3.6/unittest/mock.py", line 1183, in patched
      return func(*args, **keywargs)
    File "/Users/runner/work/salmon/salmon/tests/test_server.py", line 303, in test_queue_receiver_sleep
      self.assertEqual(sleep_mock.call_count, 2)
  AssertionError: 3 != 2

I feel like I've seen this fail before. Maybe just checking the call count is greater than 0 would be enough to ensure correctness?

Salmon should have been thread-safe and performant from the start. This PR makes that true.

• [x] Write tests for locking handler call
• [x] Write tests for locking and nolocking decorators
• [x] Make sure state storages are thread-safe (I think they are already, but it's worth checking)
• [x] Update docs

It would be great if Salmon could be told to treat errors in byte decoding with something other than "strict". For example, it might be desirable to use "replace" instead if half an email was better than no email.

guess_encoding_and_decode has an optional argument errors which is set to DEFAULT_ERROR_HANDLING by default. Because this is set in the function signature it's impossible to monkey-patch the default to some other value without monkey-patching the entire function.

I imagine this was the original intention behind errors/DEFAULT_ERROR_HANDLING as other variables can be monkey-patched at runtime in lieu of a proper settings sytems.

1. Change the default value of errors to None and then set errors to DEFAULT_ERROR_HANDLING if errors is still None when the function is called.
2. Go up the function chain, all the way up to calls from MailRequest and give each one an errors argument. Also give MailRequest some property which can be set after object initialisation that controls the value of errors.

1 is required to be done to close this issue, 2 would be nice if there aren't too many functions between MailRequest and guess_encoding_and_decode