Dear all
I need an opinion.
It seems infeasible to retain qmail as the mail-server for our mailing lists. That's because implementing SPF (required by major domains, eg google and such) _REQUIRES_ us to implement SRS, which is not compiled into qmails by default.
Postfix is reasonably easy to configure and with postsrs, an SRS solution exists. And it works, I use it on my private server. Also, we'd get the benefit of being able to use more advances spam filtering, because viable solutions that don't need a Ph.D. in configure-by-source-code-patching-and-editing exists.
Does this sound sane or should I make an effort to retain qmail? (The quicker the responses are, the quicker I can make the move).
Best regards -Tobias
Sorry for asking a dumb question -- does qmail have anything to do with our mailing list console and archive, at:
http://lists.squeakfoundation.org/mailman/listinfo/squeak-dev
?
I do like that system for its Linux-industrial nature. Its archive is accessible and search-engine indexed. I don't know about Postfix or any other solution, but I would be hesitant to introduce a disruption into the archive (could it be imported into Postfix?) or the subscriptions or anything else to fix something that ain't broke..
On Fri, Oct 14, 2016 at 1:24 PM, Tobias Pape Das.Linux@gmx.de wrote:
Dear all
I need an opinion.
It seems infeasible to retain qmail as the mail-server for our mailing lists. That's because implementing SPF (required by major domains, eg google and such) _REQUIRES_ us to implement SRS, which is not compiled into qmails by default.
Postfix is reasonably easy to configure and with postsrs, an SRS solution exists. And it works, I use it on my private server. Also, we'd get the benefit of being able to use more advances spam filtering, because viable solutions that don't need a Ph.D. in configure-by-source-code-patching-and-editing exists.
Does this sound sane or should I make an effort to retain qmail? (The quicker the responses are, the quicker I can make the move).
Best regards -Tobias
Hi,
On 14.10.2016, at 21:12, Chris Muller asqueaker@gmail.com wrote:
Sorry for asking a dumb question -- does qmail have anything to do with our mailing list console and archive, at:
http://lists.squeakfoundation.org/mailman/listinfo/squeak-dev
?
No, that interface is being generated by mailman itself. What I talk about is the software that receives mail and delivers it to mailman and to, for example, you :)
Best regards -Tobias
I do like that system for its Linux-industrial nature. Its archive is accessible and search-engine indexed. I don't know about Postfix or any other solution, but I would be hesitant to introduce a disruption into the archive (could it be imported into Postfix?) or the subscriptions or anything else to fix something that ain't broke..
On Fri, Oct 14, 2016 at 1:24 PM, Tobias Pape Das.Linux@gmx.de wrote:
Dear all
I need an opinion.
It seems infeasible to retain qmail as the mail-server for our mailing lists. That's because implementing SPF (required by major domains, eg google and such) _REQUIRES_ us to implement SRS, which is not compiled into qmails by default.
Postfix is reasonably easy to configure and with postsrs, an SRS solution exists. And it works, I use it on my private server. Also, we'd get the benefit of being able to use more advances spam filtering, because viable solutions that don't need a Ph.D. in configure-by-source-code-patching-and-editing exists.
Does this sound sane or should I make an effort to retain qmail? (The quicker the responses are, the quicker I can make the move).
Best regards -Tobias
We really need SPF, so go with postfix if that's the best solution.
Levente
On Fri, 14 Oct 2016, Tobias Pape wrote:
Dear all
I need an opinion.
It seems infeasible to retain qmail as the mail-server for our mailing lists. That's because implementing SPF (required by major domains, eg google and such) _REQUIRES_ us to implement SRS, which is not compiled into qmails by default.
Postfix is reasonably easy to configure and with postsrs, an SRS solution exists. And it works, I use it on my private server. Also, we'd get the benefit of being able to use more advances spam filtering, because viable solutions that don't need a Ph.D. in configure-by-source-code-patching-and-editing exists.
Does this sound sane or should I make an effort to retain qmail? (The quicker the responses are, the quicker I can make the move).
Best regards -Tobias
On 18.10.2016, at 01:32, Levente Uzonyi leves@caesar.elte.hu wrote:
We really need SPF, so go with postfix if that's the best solution.
SRS is set up postfix wiggled around, spamfilter and virusfilter installed. On to the beast called mailman… Then: updating the SPF records
Levente
On Fri, 14 Oct 2016, Tobias Pape wrote:
Dear all
I need an opinion.
It seems infeasible to retain qmail as the mail-server for our mailing lists. That's because implementing SPF (required by major domains, eg google and such) _REQUIRES_ us to implement SRS, which is not compiled into qmails by default.
Postfix is reasonably easy to configure and with postsrs, an SRS solution exists. And it works, I use it on my private server. Also, we'd get the benefit of being able to use more advances spam filtering, because viable solutions that don't need a Ph.D. in configure-by-source-code-patching-and-editing exists.
Does this sound sane or should I make an effort to retain qmail? (The quicker the responses are, the quicker I can make the move).
Best regards -Tobias
box-admins@lists.squeakfoundation.org