Hi!

But LMTP is the "Local" Mail Transfer Protocol. I only have access to IMAP, POP3 and SMTP. Outgoing seems to be simple, but what about incoming?

Regards, Florian Schulze

On 11 Sep 2021, at 21:21, Jörg Michael Schulz via Mailman-users wrote:

Hi,

yes, this should be possible.

See the parameters in your mailman.cfg:

[mta] # The class defining the interface to the incoming mail transport agent. incoming: mailman.mta.exim4.LMTP #incoming: mailman.mta.postfix.LMTP

# The callable implementing delivery to the outgoing mail transport agent. # This must accept three arguments, the mailing list, the message, and the # message metadata dictionary. outgoing: mailman.mta.deliver.deliver

smtp_host: mail.yourfavoritedomain.de smtp_port: 25 smtp_user: smtp_pass:

Am 11.09.21 um 19:53 schrieb Florian Schulze:

...

Hi!

Is it possible to use an external Mail-Server? Does mailman3 support that directly, or would I have to setup a local MTA which somehow fetches incoming mails from the external inbox and uses the external Mail-Server for delivery?

Does anyone do that and have example configurations?

Regards, Florian Schulze

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

---

Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

De: Abhilash Raj <maxking@asynchronous.in>

On 9/12/21 12:21 AM, Florian Schulze wrote:

...

Hi! But LMTP is the "Local" Mail Transfer Protocol. I only have access to IMAP, POP3 and SMTP. Outgoing seems to be simple, but what about incoming?

For incoming, you'd have to have a local MTA that can receive emails over SMTP and deliver it to Mailman over LMTP.

I've always setup Mailman with a local MTA but my experience tells me that anything that can listen on a TCP socket on localhost (127.0.0.1 or ::1) can be "convinced" to listen on any other address.

So, Mailman should be able to listen for properly finerwalled LMTP connections external to the server it runs on from an "external" MTA that knows how to deliver via LMTP like, for example, Postfix (I quit speaking Klingon in the late '90s ;-))

Victoriano Giralt Sent from a hand held device

On 12/09/2021 09:08, Jörg Michael Schulz via Mailman-users wrote:

Hi,

in my humble opinion:

re: incoming: you only need to configure the process that serves your incoming mail to route/forward it to the LMTP port of mailman as described in the docs, for example here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.ht...

in

# /etc/exim4/conf.d/transport/55_mm3_transport mailman3_transport: driver = smtp protocol = lmtp allow_localhost hosts = localhost port = MM3_LMTP_PORT rcpt_include_affixes = true

If you are in a position to set up Exim as the local MTA, you could use my ansible config:

https://github.com/rivimey/ansible-exim4

to install it very simply. Ansible is a generic tool to configure software on hosts, and this config tries to abstract a lot of the knowledge I have gained into a very simple config. For example, this is the config I use to set up as a 'smarthost', accepting and forwarding all mail:

######################### EXIM SMARTHOST

exim_server_name: "{{ hostname_fqdn }}"
exim_disable_ipv6: no

# TCP/IP ports on which exim should listen for mail. Keep things simple.
exim_listen_ports: [ 25 ]
exim_tls_ports: []
exim_local_domains: []

# These define the basic operation: here, a non-local smarthost.
exim_deliver_direct: no
exim_deliver_smarthost: yes
exim_deliver_localuser: no

# Where is the smarthost?
exim_smarthost_authenticated: no
exim_smarthost_address: post.ivimey.org

# Pi doesn't include spamd support.
exim_use_spamassassin: no
exim_use_dkim: no

While this is a fragment of my main mailserver config, which deals with mailman, multiple email domains, TLS, DKIM, user auth, spam detection, and delivery to dovecot:

######################### EXIM
# TCP/IP ports on which exim should listen for mail
exim_listen_ports:
   - 25
   - 465
   - 587

# Ports (in exim_listen_ports) that are TLS by default.
exim_tls_ports:
   - 587

# User/password lookup on local mysql server:
exim_mysql_hostname: localhost
exim_mysql_database: mail
exim_mysql_user: post
exim_disable_ipv6: true

exim_server_name: ivimey.org
exim_intercommand_delay: 1s

exim_auth_store_mysql: yes
exim_deliver_direct: yes
exim_deliver_smarthost: no
exim_imap_transport: yes
exim_local_parts_suffix: yes
exim_use_antivirus: no
exim_use_dkim: yes
exim_use_spamassassin: yes

# see also dovecot_dir_storage
exim_virtual_homes: /opt/mail/home

# Optional parts:
exim_mailman_transport: v3
exim_mailman_transport_host: mailman.ivimey.org
exim_mailman_transport_port: 8024
exim_mailman_root: "{{ mailman3_var_dir }}/lists"

exim_procmail_transport: no

For the interested, I also have an ansible config for mailman itself, though it is not necessary to use both together:

https://github.com/rivimey/ansible-mailman3

Whether or not you use my configs, I would definitely recommend trying Ansible out as a good way to configure software in (a) a repeatable and sane way, and (b) to take advantage of the experience of those who have created the configs, so you don't make too many mistakes!

Best regards,

Ruth

-- Ruth Ivimey-Cook Magazine Editor, Software Consultant Blog: http://www.ivimey.org/blog