Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Advertise available addresses to MTA #32

Open
1 of 4 tasks
EtienneBruines opened this issue Jul 5, 2015 · 0 comments
Open
1 of 4 tasks

Advertise available addresses to MTA #32

EtienneBruines opened this issue Jul 5, 2015 · 0 comments

Comments

@EtienneBruines
Copy link
Collaborator

Let's say we have one e-mail account [email protected]. If we want to store e-mail from this e-mail address, we should configure the MTA (Postfix in this example) to receive this e-mail, and forward it to our IMAP server.

If it forwards it to the IMAP server, the IMAP server can say "OK, received", or something like "NO, I don't know that user". In the latter case, the MTA often tries to send an Undelivered Mail Returned to Sender e-mail to the sender-address (which does not have to be the actual sender). This causes backscatter.

So, we should tell the MTA which e-mails should be forwarded, and which e-mails should not.

Possibilities

  • Using Unix sockets (socketmap_table) - I want to support at least this
  • Using TCP sockets (tcp_table)
  • Using DBMS systems (nothing to support; when we can read from MySQL, then so can Postfix)
  • Support anything else than Postfix (exim4, ...?) -- help wanted

... more?

This issue is there for discussion / new possibilities to implement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant