[Mailman-Users] Fwd: Using gmail SMTP and mailman together
mandtprice at gmail.com
Tue Apr 25 19:17:14 CEST 2006
Thanks to you and Patrick both for your time on this request.
The need to be able to connect to a remote, tls speaking MTA has been
eliminated by a little program called ssmtp that I found in the debian
repository. All it does is impersonate the sendmail binary on the
client end while piping the message to 'real' smtp server over tcp/ip.
It supports tla and authentication so that is a relief. The only
unknow is speed, since ssmtp doesn't do any spooling it could be quite
a wait if one has to wait for 200 individual SMTP transactions to
I keep poking at mailman since the problem got a whole lot easier
after I found this program.
Thanks again for your time.
On 4/25/06, Mark Sapiro <msapiro at value.net> wrote:
> Matthew Price wrote:
> >The one mailing list feature that I absolutely need is the ability to
> >make each message appear to be individually sent; I don't want every
> >subscriber to see the addresses of every other subscriber. I already
> >checked that functionality in gmail and its group feature just pastes
> >the associated addresses into the recipients' list.
> If you are only trying to protect the privacy of the list and not the
> fact that there is a list involved, check out
> <http://groups.yahoo.com/>, <http://groups.google.com/> or
> <http://lists.topica.com/>. For various reasons, I can't really
> recommend Topica and I have no list management experience with the
> If you are trying to make each recipient's message look like a personal
> message addressed to the recipient, then perhaps Mailman on your
> laptop could be a solution, but there are potential stumbling blocks.
> In your OP, you asked if Mailman can use Gmail's secure SMTP service
> for outgoing mail. Mailman itself doesn't support SSL and I don't know
> anything about adding this layer between Mailman and the outside.
> There is a post at
> that gives a patch for adding user/password smtp authentication to
> Mailman's outgoing SMTP, but this is not the same thing.
> Also, there are issues with using a remote outgoing SMTP server "on the
> road". You will undoubtedly encounter in your travels, public access
> points that redirect all port 25 (and perhaps secure smtp ports too)
> connects to their own SMTP server, thus thwarting your attempts to
> reach your preferred server.
> Putting your own outgoing SMTP server on your laptop may help, but
> there are issues like the above here too, as well as issues with the
> recipient's server possibly not liking the way your server identifies
> itself or the fact that its claimed identity doesn't match its current
> Mark Sapiro <msapiro at value.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
Is life so dear, or peace so sweet, as to be purchased at the price of
chains and slavery? Forbid it, Almighty God! I know not what course
others may take; but as for me, give me liberty or give me death!
More information about the Mailman-Users