[Dovecot] Running mailfront under dovecot2.x service supervision
Hello, Hello,
I'm trying to run mailfront SMTP (http://untroubled.org/mailfront/) under Dovecot 2.x process/service supervision
My intention was to utilize the fact that dovecot2.x seems to have some kind of generic process/service supervision as well as builtin ssl support. But I cannot get the most simple generic service setup (without ssl) to work.
Currently running dovecot 2.0.11 on FreeBSD 8.1
service smtp-auth { executable = /usr/local/bin/smtpfront-qmail inet_listener smtp-auth { port = 587 ssl = no } }
I have added the above to dovecot.conf
Once I start dovecot everything seems fine - no errors in the log But at the first attempt to telnet to localhost port 587 - I instantly get the indication of never ending forks in the dovecot log (see below) - neither do I get the SMTP prompt that I expected in my telnet session - it just hangs.
Apr 19 10:05:34 smtp-auth: Error: mailfront[43539]: bytes in: 0 bytes out: 29 Apr 19 10:05:34 smtp-auth: Error: mailfront[43541]: bytes in: 0 bytes out: 29 Apr 19 10:05:34 smtp-auth: Error: mailfront[43543]: bytes in: 0 bytes out: 29 Apr 19 10:05:34 smtp-auth: Error: mailfront[43545]: bytes in: 0 bytes out: 29
Question is if I've misconfigured something or if it is impossible to utilize dovecot2.x this way ?
PS: Now I know that I could use daemontools or such for this task - but I like the dovecot ssl handling and would like to end up by wrapping this smtp service inside same dovecot ssl that I use for IMAPS.
Any feedback is more than welcome - I'm stuck
Thanks in advance Uffe
-- View this message in context: http://old.nabble.com/Running-mailfront-under-dovecot2.x-service-supervision... Sent from the Dovecot mailing list archive at Nabble.com.
Am 19.04.2011 12:23, schrieb Uffe Jakobsen:
Hello,
I'm trying to run mailfront SMTP (http://untroubled.org/mailfront/) under Dovecot 2.x process/service supervision
My intention was to utilize the fact that dovecot2.x seems to have some kind of generic process/service supervision as well as builtin ssl support. But I cannot get the most simple generic service setup (without ssl) to work.
Currently running dovecot 2.0.11 on FreeBSD 8.1
service smtp-auth { executable = /usr/local/bin/smtpfront-qmail inet_listener smtp-auth { port = 587 ssl = no } }
I have added the above to dovecot.conf
Once I start dovecot everything seems fine - no errors in the log But at the first attempt to telnet to localhost port 587 - I instantly get the indication of never ending forks in the dovecot log (see below) - neither do I get the SMTP prompt that I expected in my telnet session - it just hangs.
Apr 19 10:05:34 smtp-auth: Error: mailfront[43539]: bytes in: 0 bytes out: 29 Apr 19 10:05:34 smtp-auth: Error: mailfront[43541]: bytes in: 0 bytes out: 29 Apr 19 10:05:34 smtp-auth: Error: mailfront[43543]: bytes in: 0 bytes out: 29 Apr 19 10:05:34 smtp-auth: Error: mailfront[43545]: bytes in: 0 bytes out: 29
Question is if I've misconfigured something or if it is impossible to utilize dovecot2.x this way ?
PS: Now I know that I could use daemontools or such for this task - but I like the dovecot ssl handling and would like to end up by wrapping this smtp service inside same dovecot ssl that I use for IMAPS.
Any feedback is more than welcome - I'm stuck
Thanks in advance Uffe
i ve got confused, dovecot is no smtp server what are you trying to goal ?
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Robert Schetterer wrote:
i ve got confused, dovecot is no smtp server what are you trying to goal ?
Correct dovecot is not an smtp server. My goal is what I wrote in the initial email - but I try to explain in other words.
Dovecot2.0.x has the ability to setup somewhat generic supervised services ala daemontools services if you know that tool. Dovecot uses these services internally to wrap an ordinary imap session into an ssl session. And that is exactly what I would like to do with my mailfront session - wrap it into a ssl session using the generic service setup present in dovecot 2.0.x
As far as I can see - the services that you define inside dovecot.conf does not have to relate to imap at all and since smtp and imap go hand in hand in order to have a fully working email setup - then why not have dovecot control all the services ?
/Uffe
-- View this message in context: http://old.nabble.com/Running-mailfront-under-dovecot2.x-service-supervision... Sent from the Dovecot mailing list archive at Nabble.com.
Am 19.04.2011 14:19, schrieb Uffe Jakobsen:
Robert Schetterer wrote:
i ve got confused, dovecot is no smtp server what are you trying to goal ?
Correct dovecot is not an smtp server. My goal is what I wrote in the initial email - but I try to explain in other words.
Dovecot2.0.x has the ability to setup somewhat generic supervised services ala daemontools services if you know that tool. Dovecot uses these services internally to wrap an ordinary imap session into an ssl session. And that is exactly what I would like to do with my mailfront session - wrap it into a ssl session using the generic service setup present in dovecot 2.0.x
As far as I can see - the services that you define inside dovecot.conf does not have to relate to imap at all and since smtp and imap go hand in hand in order to have a fully working email setup - then why not have dovecot control all the services ?
/Uffe
understand , but this is a "must Timo response" i guess
-- Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
Robert Schetterer wrote:
Am 19.04.2011 14:19, schrieb Uffe Jakobsen:
understand , but this is a "must Timo response" i guess
I agree with you :-)
View this message in context: http://old.nabble.com/Running-mailfront-under-dovecot2.x-service-supervision... Sent from the Dovecot mailing list archive at Nabble.com.
On Tue, 2011-04-19 at 03:23 -0700, Uffe Jakobsen wrote:
I'm trying to run mailfront SMTP (http://untroubled.org/mailfront/) under Dovecot 2.x process/service supervision
My intention was to utilize the fact that dovecot2.x seems to have some kind of generic process/service supervision as well as builtin ssl support. But I cannot get the most simple generic service setup (without ssl) to work.
service smtp-auth { executable = /usr/local/bin/smtpfront-qmail
The services have to be written explicitly for Dovecot, using Dovecot's lib-master library.
Is smtpfront-qmail trying to use inetd-style execution? Maybe Dovecot could some day support that, but it's not really in my near future plans.
PS: Now I know that I could use daemontools or such for this task - but I like the dovecot ssl handling and would like to end up by wrapping this smtp service inside same dovecot ssl that I use for IMAPS.
Also the service is supposed to do the SSL itself internally, so you really can't do any of this.
Hi Timo,
Timo Sirainen wrote:
Is smtpfront-qmail trying to use inetd-style execution? Maybe Dovecot could some day support that, but it's not really in my near future plans.
Yes smtpfront-qmail relies upon "standard" inetd-style execution. I hoped that this was the way dovecots internal services was behaving :-)
It would be really nice if future dovecot could support inetd-style services limitations/delay etc...
- seems that you have most of the setup in place. Process limits - respawn
I would definitely vote for this feature :-)
Timo Sirainen wrote:
The services have to be written explicitly for Dovecot, using Dovecot's lib-master library.
Aha ok I see - will try to look into that... when time permits
Timo Sirainen wrote:
Also the service is supposed to do the SSL itself internally, so you really can't do any of this.
ok...
Thanks for your answer.
-- View this message in context: http://old.nabble.com/Running-mailfront-under-dovecot2.x-service-supervision... Sent from the Dovecot mailing list archive at Nabble.com.
participants (3)
-
Robert Schetterer
-
Timo Sirainen
-
Uffe Jakobsen