-
Notifications
You must be signed in to change notification settings - Fork 28
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
Remove code for QMTP. #142
Comments
You are mixing up 2 things: QMTP is in qmail-qmtpd*. The qmail-qmqp* files are the queue-to-queue-copy-protocol, which you can use with local machines to have one do the outgoing mail for the neighbors. This may or may not be still useful. |
I guess it's clear I've never used either one :-) Reduced the scope of this issue to QMTP only. |
On Sat, 23 May 2020 at 19:19, Amitai Schleier ***@***.***> wrote:
According to DJB in 1997, QMTP is a replacement for SMTP. This doesn't seem to have happened.
Our next release announcement (1.09, as of this writing) can include our intent to remove this code. After that release goes out, barring persuasive objections, we can remove these files and references thereto:
qmail-qmqpc.8
qmail-qmqpc.c
qmail-qmqpd.8
qmail-qmqpd.c
qmail-qmqpc, qmail-qmqpd shouldn't be removed. It is very useful for
diskless clients. Also I know users who are running qmail on a podman
container, but on the server which runs the container, they use
mini-qmail installation to push all email from cron, etc to go to the
podman server, without requiring a queue or qmail installation on the
server.
…--
Regards Manvendra - http://www.indimail.org
GPG Pub Key
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C
|
We use serialmail’s qmtp client to push messages from our MX to the device that ends up reading them. http://untroubled.org/mailfront/ provides maintained QMTP and QMQP frontends, which provides a migration path for QMTP users. (Also, out of scope for this issue, but QMQP is an essential part of miniqmail) |
So it may be useful for us to check that mailfront can still use notqmail as a backend as development goes. |
Leave qmtp alone. Do not remove it. Instead, fully merge with mailfront. |
Definitely not something to remove, please. I'd hazard a guess that many heavy/high volume users of qmail deploy QMTP/QMQP behind the scenes, as my business does. |
According to DJB in 1997, QMTP is a replacement for SMTP. This doesn't seem to have happened.
Our next release announcement (1.09, as of this writing) can include our intent to remove this code. After that release goes out, barring persuasive objections, we can remove these files and references thereto:
qmail-qmtpd.8
qmail-qmtpd.c
The text was updated successfully, but these errors were encountered: