Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Hi Yaakov, Yaakov Selkowitz wrote: > > Corinna, Christian, Daniel, Pierre, > > Because MTAs must be user-configured, and we certainly don't want to > lose the selection during package upgrades, the alternatives cannot be > handled in package postinst/prerm. I think the only way to make this > work is for each MTA config script to handle these instead by including > the following snippets in the respective MTA config scripts. > > Please review this carefully in case I missed anything. > > sendmail: > > > /usr/sbin/alternatives --install /usr/sbin/sendmail mta > /usr/sbin/sendmail-real.exe 0 \ > --slave /usr/lib/sendmail mta-sendmail /usr/sbin/sendmail-real.exe \ > --slave /usr/bin/mailq mta-mailq /usr/sbin/sendmail-real.exe \ > --slave /usr/bin/newaliases mta-newaliases > /usr/sbin/sendmail-real.exe \ > --slave /usr/bin/rmail mta-rmail /usr/sbin/sendmail-real.exe > > /usr/sbin/alternatives --set mta /usr/sbin/sendmail-real.exe Thanks. I will use these with a slight modification. My source code is currently being used on Cygwin, Ubuntu, Lubuntu, Kubuntu, Debian and Suze. So I already had to come up with a solution which would work for all of these systems. My solution is to install the Sendmail binary into /usr/libexec. This works beautifully, because now the "shared namespace" /usr/sbin/sendmail can be overwritten, without removing the actual binary. Sincerely, Daniel
RE: MTA packaging (exim, postfix, sendmail, ssmtp)
> -Original Message- > From: Yaakov Selkowitz> Sent: Wednesday, October 08, 2014 13:59 > > On 2014-10-08 12:01, Pierre A. Humblet wrote: > >> -Original Message- > > I was going to mention that and suggest to add another alternative in > > cron-config /usr/sbin/alternatives --install /usr/sbin/sendmail mta > > /usr/bin/cronlog 0 > > Except that cronlog isn't a real MTA. What I think should happen instead is > cron should use cronlog if sendmail isn't present. That means a change to the C code, much easier to do it in cron-config. What's the harm? cronlog prints an error message if it is not called from cron, so trying to use it as an mta will fail immediately, with feedback to the user. > > Also exim itself can run perfectly fine if the mta alternatives is set > > to another mta, except that mailq and sendmail won't call exim. > > So in exim-config I was going to present the current mta alternative > > to the user, explain the above, and ask if it should be changed. In some cases (don't want to start a long discussion) it makes sense for applications to send mail with ssmtp, which can be configured to send the mail to exim running on localhost. That can be done by setting the mta to ssmtp, as applications look for sendmail. > IOW /usr/bin/exim can be called directly? True, and I suspect that would be > the case for the other MTAs (certainly ssmtp). But in that case, is there a > need to run exim-config? There is a ton of other stuff to do in exim-config, from setting the hostname the outside world should see to calling cygrunsrv the right way. Pierre
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
On 2014-10-08 12:01, Pierre A. Humblet wrote: -Original Message- I was going to mention that and suggest to add another alternative in cron-config /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/bin/cronlog 0 Except that cronlog isn't a real MTA. What I think should happen instead is cron should use cronlog if sendmail isn't present. I am fine with the proposal for exim, except that I was not planning to add rmail, rsmtp, and runq Those are for compatibility with smail. I never included them in the cygwin distribution and nobody has ever complained. Okay, thanks for clarifying. Also exim itself can run perfectly fine if the mta alternatives is set to another mta, except that mailq and sendmail won't call exim. So in exim-config I was going to present the current mta alternative to the user, explain the above, and ask if it should be changed. IOW /usr/bin/exim can be called directly? True, and I suspect that would be the case for the other MTAs (certainly ssmtp). But in that case, is there a need to run exim-config? Yaakov
RE: MTA packaging (exim, postfix, sendmail, ssmtp)
> -Original Message- > From: Christian Franke > Sent: Wednesday, October 08, 2014 12:32 > > Yaakov Selkowitz wrote: > > On 2014-10-08 07:52, Corinna Vinschen wrote: > >> On Oct 6 17:19, Yaakov Selkowitz wrote: > >>> Because MTAs must be user-configured, and we certainly don't want to > >>> lose the selection during package upgrades, the alternatives cannot > >>> be handled in package postinst/prerm. I think the only way to make > >>> this work is for each MTA config script to handle these instead by > >>> including the following snippets in the respective MTA config > >>> scripts. > >>> > >>> Please review this carefully in case I missed anything. > >> > >> The ssmtp part looks ok to me. Two questions: > >> > >> - Don't we have to add something to preremove as well? > > > > No, because we don't distinguish between removing and upgrading a > > package in preremove. Whenever a user wishes to switch MTAs, they > > will need to run alternatives --set, preferably via the MTA config > > scripts. > > The cron package is also affected. Its postinstall script sets a symlink > /usr/sbin/sendmail -> /usr/bin/cronlog if sendmail does not exist. This would > break alternatives setting in MTA configure script because alternatives would > never replace the existing symlink. > > Possible workaround: Add rm -f /usr/sbin/sendmail ... to MTA configure > scripts. I was going to mention that and suggest to add another alternative in cron-config /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/bin/cronlog 0 That way all cases are treated uniformly. I don't dispute that it may be safer to rm the old (pre alternatives) sendmail, mailq, etc links before installing with alternatives I am fine with the proposal for exim, except that I was not planning to add rmail, rsmtp, and runq Those are for compatibility with smail. I never included them in the cygwin distribution and nobody has ever complained. Also exim itself can run perfectly fine if the mta alternatives is set to another mta, except that mailq and sendmail won't call exim. So in exim-config I was going to present the current mta alternative to the user, explain the above, and ask if it should be changed. Pierre
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
On 2014-10-08 11:32, Christian Franke wrote: The cron package is also affected. Its postinstall script sets a symlink /usr/sbin/sendmail -> /usr/bin/cronlog if sendmail does not exist. This would break alternatives setting in MTA configure script because alternatives would never replace the existing symlink. Good catch. Possible workaround: Add rm -f /usr/sbin/sendmail ... to MTA configure scripts. Yes, before running alternatives. Yaakov
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Yaakov Selkowitz wrote: On 2014-10-08 07:52, Corinna Vinschen wrote: On Oct 6 17:19, Yaakov Selkowitz wrote: Because MTAs must be user-configured, and we certainly don't want to lose the selection during package upgrades, the alternatives cannot be handled in package postinst/prerm. I think the only way to make this work is for each MTA config script to handle these instead by including the following snippets in the respective MTA config scripts. Please review this carefully in case I missed anything. The ssmtp part looks ok to me. Two questions: - Don't we have to add something to preremove as well? No, because we don't distinguish between removing and upgrading a package in preremove. Whenever a user wishes to switch MTAs, they will need to run alternatives --set, preferably via the MTA config scripts. The cron package is also affected. Its postinstall script sets a symlink /usr/sbin/sendmail -> /usr/bin/cronlog if sendmail does not exist. This would break alternatives setting in MTA configure script because alternatives would never replace the existing symlink. Possible workaround: Add rm -f /usr/sbin/sendmail ... to MTA configure scripts. Christian
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
On 2014-10-08 07:52, Corinna Vinschen wrote: On Oct 6 17:19, Yaakov Selkowitz wrote: Because MTAs must be user-configured, and we certainly don't want to lose the selection during package upgrades, the alternatives cannot be handled in package postinst/prerm. I think the only way to make this work is for each MTA config script to handle these instead by including the following snippets in the respective MTA config scripts. Please review this carefully in case I missed anything. The ssmtp part looks ok to me. Two questions: - Don't we have to add something to preremove as well? No, because we don't distinguish between removing and upgrading a package in preremove. Whenever a user wishes to switch MTAs, they will need to run alternatives --set, preferably via the MTA config scripts. - What if the user installs multiple MTA packages at the same time? That's why we need both --install and --set, to make these manually configured. Trying to let alternatives auto-configure this will just lead to problems. Yaakov
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Hi Yaakov, On Oct 6 17:19, Yaakov Selkowitz wrote: > Corinna, Christian, Daniel, Pierre, > > Because MTAs must be user-configured, and we certainly don't want to lose > the selection during package upgrades, the alternatives cannot be handled in > package postinst/prerm. I think the only way to make this work is for each > MTA config script to handle these instead by including the following > snippets in the respective MTA config scripts. > > Please review this carefully in case I missed anything. The ssmtp part looks ok to me. Two questions: - Don't we have to add something to preremove as well? - What if the user installs multiple MTA packages at the same time? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpFAVz9IRDyj.pgp Description: PGP signature
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Christian Franke wrote: Yaakov Selkowitz wrote: Corinna, Christian, Daniel, Pierre, Because MTAs must be user-configured, and we certainly don't want to lose the selection during package upgrades, the alternatives cannot be handled in package postinst/prerm. I think the only way to make this work is for each MTA config script to handle these instead by including the following snippets in the respective MTA config scripts. Please review this carefully in case I missed anything. ... postfix: /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/postfix.exe 0 \ --slave /usr/lib/sendmail mta-sendmail /usr/sbin/postfix.exe \ --slave /usr/bin/mailq mta-mailq /usr/sbin/postfix.exe \ --slave /usr/bin/newaliases mta-newaliases /usr/sbin/postfix.exe /usr/sbin/alternatives --set mta /usr/sbin/postfix.exe "postfix" is the control program, there is a separate "sendmail" command for sendmail emulation. Attached is the alternatives part of the /etc/postinstall/postfix.sh from the current draft postfix package. It also provides links for the related man pages. Forgot to mention: This will be moved from postinstall to the configure script as requested.
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Yaakov Selkowitz wrote: Corinna, Christian, Daniel, Pierre, Because MTAs must be user-configured, and we certainly don't want to lose the selection during package upgrades, the alternatives cannot be handled in package postinst/prerm. I think the only way to make this work is for each MTA config script to handle these instead by including the following snippets in the respective MTA config scripts. Please review this carefully in case I missed anything. ... postfix: /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/postfix.exe 0 \ --slave /usr/lib/sendmail mta-sendmail /usr/sbin/postfix.exe \ --slave /usr/bin/mailq mta-mailq /usr/sbin/postfix.exe \ --slave /usr/bin/newaliases mta-newaliases /usr/sbin/postfix.exe /usr/sbin/alternatives --set mta /usr/sbin/postfix.exe "postfix" is the control program, there is a separate "sendmail" command for sendmail emulation. Attached is the alternatives part of the /etc/postinstall/postfix.sh from the current draft postfix package. It also provides links for the related man pages. The Fedora postfix package also provides alternatives for man5/aliases.5.gz and man8/smtpd.8.gz. Is this needed on Cygwin? Thanks, Christian /usr/sbin/alternatives \ --install /usr/sbin/sendmail mta /usr/sbin/sendmail.postfix.exe 0 \ --slave /usr/lib/sendmail mta-sendmail /usr/sbin/sendmail.postfix.exe \ --slave /usr/bin/mailq mta-mailq /usr/sbin/sendmail.postfix.exe \ --slave /usr/bin/newaliases mta-newaliases /usr/sbin/sendmail.postfix.exe \ --slave /usr/share/man/man1/sendmail.1.gz mta-sendmail-man /usr/share/man/man1/sendmail.postfix.1.gz \ --slave /usr/share/man/man1/mailq.1.gz mta-mailq-man /usr/share/man/man1/sendmail.postfix.1.gz \ --slave /usr/share/man/man1/newaliases.1.gz mta-newaliases-man /usr/share/man/man1/sendmail.postfix.1.gz /usr/sbin/alternatives --set mta /usr/sbin/sendmail.postfix.exe
MTA packaging (exim, postfix, sendmail, ssmtp)
Corinna, Christian, Daniel, Pierre, Because MTAs must be user-configured, and we certainly don't want to lose the selection during package upgrades, the alternatives cannot be handled in package postinst/prerm. I think the only way to make this work is for each MTA config script to handle these instead by including the following snippets in the respective MTA config scripts. Please review this carefully in case I missed anything. exim: = /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/bin/exim 0 \ --slave /usr/lib/sendmail mta-sendmail /usr/bin/exim \ --slave /usr/bin/mailq mta-mailq /usr/bin/exim \ --slave /usr/bin/newaliases mta-newaliases /usr/bin/exim \ --slave /usr/bin/rmail mta-rmail /usr/bin/exim \ --slave /usr/bin/rsmtp mta-rsmtp /usr/bin/exim \ --slave /usr/bin/runq mta-runq /usr/bin/exim /usr/sbin/alternatives --set mta /usr/bin/exim postfix: /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/postfix.exe 0 \ --slave /usr/lib/sendmail mta-sendmail /usr/sbin/postfix.exe \ --slave /usr/bin/mailq mta-mailq /usr/sbin/postfix.exe \ --slave /usr/bin/newaliases mta-newaliases /usr/sbin/postfix.exe /usr/sbin/alternatives --set mta /usr/sbin/postfix.exe sendmail: /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/sendmail-real.exe 0 \ --slave /usr/lib/sendmail mta-sendmail /usr/sbin/sendmail-real.exe \ --slave /usr/bin/mailq mta-mailq /usr/sbin/sendmail-real.exe \ --slave /usr/bin/newaliases mta-newaliases /usr/sbin/sendmail-real.exe \ --slave /usr/bin/rmail mta-rmail /usr/sbin/sendmail-real.exe /usr/sbin/alternatives --set mta /usr/sbin/sendmail-real.exe ssmtp: = /usr/sbin/alternatives --install /usr/sbin/sendmail mta /usr/sbin/ssmtp.exe 0 \ --slave /usr/lib/sendmail mta-sendmail /usr/sbin/ssmtp.exe \ --slave /usr/bin/mailq mta-mailq /usr/sbin/ssmtp.exe \ --slave /usr/bin/newaliases mta-newaliases /usr/sbin/ssmtp.exe /usr/sbin/alternatives --set mta /usr/sbin/ssmtp.exe HTH, Yaakov
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Hi Yaakov,
Yaakov Selkowitz wrote:
>
> Corinna, Christian, Daniel, Pierre,
>
> While I'm working out the details of allowing all your MTA packages to
> coexist, it would be helpful if you could clarify under what
> circumstances, if any, you expect that your MTA could function as
> /usr/sbin/sendmail for the purposes of sending outgoing mail without any
> configuration on the part of users.
Sendmail needs to be started as a service. If you mean the Cygwin user (she who
installs Sendmail), I included a postinstall script. It installs the 'CYGWIN
sendmail' service, creates the Sendmail unprivileged user ('smmsp') and sets
permissions, needed by sendmail. Permissions are set on the following
directories
and files:
/usr/sbin/sendmail.exe
/var/empty (only if sshd is not installed)
/etc/mail/
/var/spool/clientmqueue
/var/spool/mqueue
Also, I included a /usr/bin/sendmail-config script, which checks the full
hostname
of the box. If the hostname cannot be used as a fully qualified domain name, the
script suggests to change the Primary DNS suffix of the box.
If you mean the e-mail user who sends mail, no configuration is needed.
My source package will also be compiled by Ubuntu, Suze and Raspbian (Raspberry
PI)
users. These OS-es are very likely to use alternatives also.
To avoid overriding any symlinks, I am considering changing the Makefile, so it
will
install the binaries and system binaries like so:
/usr/sbin -> /usr/libexec
/usr/bin -> only if non-existant
Your thoughts on this?
Daniel
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Yaakov Selkowitz wrote: On 2014-08-29 13:45, Christian Franke wrote: Attached is a tar -t output of current draft postfix package (excluding the -doc and -debug packages). The conflicting names already have a .postfix extension. Was that automatic or of your own doing? automatically done by src_install() from my own postfix.cygport script :-)
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
On 2014-08-29 13:45, Christian Franke wrote: Attached is a tar -t output of current draft postfix package (excluding the -doc and -debug packages). The conflicting names already have a .postfix extension. Was that automatic or of your own doing? Yaakov
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
Yaakov Selkowitz wrote: On 2014-08-28 18:25, Yaakov Selkowitz wrote: Corinna, Christian, Daniel, Pierre, While I'm working out the details of allowing all your MTA packages to coexist, it would be helpful if you could clarify under what circumstances, if any, you expect that your MTA could function as /usr/sbin/sendmail for the purposes of sending outgoing mail without any configuration on the part of users. The postfix sendmail emulation would at least require that postfix is running as service/daemon. With default configuration, postfix sends email directly to destination MX server. This won't work in many use cases (direct access blocked by firewall, destination port 25 blocked by anti-virus application or ISP, connections from dynamic IP addresses rejected by MX, ...). Christian, I know you're still working on some runtime issues with postfix, but could you provide a file list so I can see what your package may look like when it's ready? Attached is a tar -t output of current draft postfix package (excluding the -doc and -debug packages). The conflicting names already have a .postfix extension. Christian etc/ etc/defaults/ etc/defaults/etc/ etc/defaults/etc/postfix/ etc/defaults/etc/postfix/access etc/defaults/etc/postfix/aliases etc/defaults/etc/postfix/canonical etc/defaults/etc/postfix/generic etc/defaults/etc/postfix/header_checks etc/defaults/etc/postfix/main.cf etc/defaults/etc/postfix/master.cf etc/defaults/etc/postfix/relocated etc/defaults/etc/postfix/transport etc/defaults/etc/postfix/virtual etc/postfix/ etc/postfix/bounce.cf.default etc/postfix/main.cf.default etc/postfix/makedefs.out etc/postinstall/ etc/postinstall/postfix.sh etc/preremove/ etc/preremove/postfix.sh usr/ usr/bin/ usr/bin/mailq.postfix usr/bin/newaliases.postfix usr/lib/ usr/libexec/ usr/libexec/postfix/ usr/libexec/postfix/anvil.exe usr/libexec/postfix/bounce.exe usr/libexec/postfix/cleanup.exe usr/libexec/postfix/discard.exe usr/libexec/postfix/dnsblog.exe usr/libexec/postfix/error.exe usr/libexec/postfix/flush.exe usr/libexec/postfix/lmtp.exe usr/libexec/postfix/local.exe usr/libexec/postfix/master.exe usr/libexec/postfix/nqmgr.exe usr/libexec/postfix/oqmgr.exe usr/libexec/postfix/pickup.exe usr/libexec/postfix/pipe.exe usr/libexec/postfix/post-install usr/libexec/postfix/postfix-files usr/libexec/postfix/postfix-script usr/libexec/postfix/postfix-wrapper usr/libexec/postfix/postmulti-script usr/libexec/postfix/postscreen.exe usr/libexec/postfix/proxymap.exe usr/libexec/postfix/qmgr.exe usr/libexec/postfix/qmqpd.exe usr/libexec/postfix/scache.exe usr/libexec/postfix/showq.exe usr/libexec/postfix/smtp.exe usr/libexec/postfix/smtpd.exe usr/libexec/postfix/spawn.exe usr/libexec/postfix/tlsmgr.exe usr/libexec/postfix/tlsproxy.exe usr/libexec/postfix/trivial-rewrite.exe usr/libexec/postfix/verify.exe usr/libexec/postfix/virtual.exe usr/sbin/ usr/sbin/postalias.exe usr/sbin/postcat.exe usr/sbin/postconf.exe usr/sbin/postdrop.exe usr/sbin/postfix.exe usr/sbin/postkick.exe usr/sbin/postlock.exe usr/sbin/postlog.exe usr/sbin/postmap.exe usr/sbin/postmulti.exe usr/sbin/postqueue.exe usr/sbin/postsuper.exe usr/sbin/sendmail.postfix.exe usr/share/ usr/share/doc/ usr/share/doc/postfix/ usr/share/doc/postfix/COPYRIGHT usr/share/doc/postfix/HISTORY usr/share/doc/postfix/LICENSE usr/share/doc/postfix/TLS_LICENSE usr/share/man/ usr/share/man/man1/ usr/share/man/man1/mailq.postfix.1.gz usr/share/man/man1/newaliases.postfix.1.gz usr/share/man/man1/postalias.1.gz usr/share/man/man1/postcat.1.gz usr/share/man/man1/postconf.1.gz usr/share/man/man1/postdrop.1.gz usr/share/man/man1/postfix.1.gz usr/share/man/man1/postkick.1.gz usr/share/man/man1/postlock.1.gz usr/share/man/man1/postlog.1.gz usr/share/man/man1/postmap.1.gz usr/share/man/man1/postmulti.1.gz usr/share/man/man1/postqueue.1.gz usr/share/man/man1/postsuper.1.gz usr/share/man/man1/sendmail.postfix.1.gz usr/share/man/man5/ usr/share/man/man5/access.5.gz usr/share/man/man5/aliases.5.gz usr/share/man/man5/body_checks.5.gz usr/share/man/man5/bounce.5.gz usr/share/man/man5/canonical.5.gz usr/share/man/man5/cidr_table.5.gz usr/share/man/man5/generic.5.gz usr/share/man/man5/header_checks.5.gz usr/share/man/man5/ldap_table.5.gz usr/share/man/man5/lmdb_table.5.gz usr/share/man/man5/master.5.gz usr/share/man/man5/memcache_table.5.gz usr/share/man/man5/mysql_table.5.gz usr/share/man/man5/nisplus_table.5.gz usr/share/man/man5/pcre_table.5.gz usr/share/man/man5/pgsql_table.5.gz usr/share/man/man5/postconf.5.gz usr/share/man/man5/postfix-wrapper.5.gz usr/share/man/man5/regexp_table.5.gz usr/share/man/man5/relocated.5.gz usr/share/man/man5/socketmap_table.5.gz usr/share/man/man5/sqlite_table.5.gz usr/share/man/man5/tcp_table.5.gz usr/share/man/man5/transport.5.gz usr/share/man/man5/virtual.5.gz usr/share/man/man8/ usr/share/man/man8/anvil.8.gz usr/share/man/man8/bounce.8.gz usr/share/man/man8/cleanup.8.gz usr/share/man/man8/defer.8.gz usr/share/man/man8/discard.8.gz usr/sh
RE: MTA packaging (exim, postfix, sendmail, ssmtp)
> -Original Message- > From: Yaakov Selkowitz > Sent: Thursday, August 28, 2014 19:25 > > Corinna, Christian, Daniel, Pierre, > > While I'm working out the details of allowing all your MTA packages to > coexist, it would be helpful if you could clarify under what circumstances, if > any, you expect that your MTA could function as /usr/sbin/sendmail for the > purposes of sending outgoing mail without any configuration on the part of > users. Exim could send outgoing mail out of the box if the destination server can be reached using dns. With many ISPs blocking port 25, a gateway must usually be configured. Of course a MTA does much more than sending outgoing mail, and that requires configuring a service etc... Because of that Exim is not currently packaged to do anything without requiring configuration (in fact, out of the box exim is a symlink to exim-config) , but it would not be hard to allow it. Pierre
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
On Aug 28 18:25, Yaakov Selkowitz wrote: > Corinna, Christian, Daniel, Pierre, > > While I'm working out the details of allowing all your MTA packages to > coexist, it would be helpful if you could clarify under what circumstances, > if any, you expect that your MTA could function as /usr/sbin/sendmail for > the purposes of sending outgoing mail without any configuration on the part > of users. For ssmtp, I don't think there's any default way to operate without the admin running ssmtp-config. Ssmtp is not exactly an MTA, but rather just a forwarder to a smarthost. So, to function at all, it requires the admin to specify that smarthost. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpZgzRWR0nrk.pgp Description: PGP signature
Re: MTA packaging (exim, postfix, sendmail, ssmtp)
On 2014-08-28 18:25, Yaakov Selkowitz wrote: Corinna, Christian, Daniel, Pierre, While I'm working out the details of allowing all your MTA packages to coexist, it would be helpful if you could clarify under what circumstances, if any, you expect that your MTA could function as /usr/sbin/sendmail for the purposes of sending outgoing mail without any configuration on the part of users. Christian, I know you're still working on some runtime issues with postfix, but could you provide a file list so I can see what your package may look like when it's ready? Yaakov
MTA packaging (exim, postfix, sendmail, ssmtp)
Corinna, Christian, Daniel, Pierre, While I'm working out the details of allowing all your MTA packages to coexist, it would be helpful if you could clarify under what circumstances, if any, you expect that your MTA could function as /usr/sbin/sendmail for the purposes of sending outgoing mail without any configuration on the part of users. Yaakov
