From: markus schnalke <meillo@marmaro.de>
  To  : <masqmail@marmaro.de>
  Date: Tue, 15 Nov 2011 23:38:28 +0100

Re: [masqmail] problem using wrapper option for smtp.google.com

Hoi,

let's come back to that issue, in order to finally close it. This
evening, I dug into the issue and found the bug ... or better: the
solution. :-)


[2011-11-04 20:33] Pierre Frenkiel <pierre.frenkiel@gmail.com>
> 
>    Nothing works for me. I took the config given by Juergen, with the
>    following gmail.route file:
> 
>       instant_helo=true
>       wrapper="/usr/bin/openssl s_client -quiet -starttls smtp -connect smtp.gmail.com:25 2>/dev/null"
>       auth_name = "login"
>       auth_login = "pierre.frenkiel@gmail.com"
>       auth_secret =  "xxxxxxxx"
>       map_return_path_addresses = "frenkiel: pierre.frenkiel@gmail.com"
>       map_h_from_addresses = "frenkiel: Pierre Frenkiel <pierre.frenkiel@gmail.com>"

First of all: Thanks for the information you gave me (also off-list).
This helped a lot.


>    I just get in the masqmail log file, sending with pine, the 3 lines
> 
>       1RMOHZ-4eF-00 <= <pierre.frenkiel@gmail.com> with ESMTP
>       detected online configuration gmail
>       1RMOHZ-4eF-00 using '/local/etc/masqmail/gmail.route'
> 
>    and the job stays in the queue.
>    if I use mailx, I get:
> 
>       1RMOSz-11Q-00 <= <frenkiel@localhost> with local
>       detected online configuration gmail
>       1RMOSz-11Q-00 using '/local/etc/masqmail/gmail.route'
> 
>    I expected to see some useful information using tcpdump, and I was surprised
>    to see that there was not a single packet to or from gmail. Can that
>    lead to the solution?.

I get the same, when I use masqmail-0.3.3.

>    I also tried to run "masqmail -q": I got alternativly
>    (the lock directory being empty):
>       masqmail-q  ==> spool file 1RMPFE-5bS-00 is locked
>       masqmail-q  ==> Memory fault
>       masqmail-q  ==> spool file 1RMPFE-5bS-00 is locked
>       masqmail-q  ==> Memory fault
>        . . .

Similar here. The mail is queued and when you process the queue, it
alters between ``is locked'' and ``segfault''. (The lock file also
gets created and removed in alteration.)

The real problem is the segfault, which leaves the spool file locked
when the process dies. The next time, no delivery is tried, just the
lock file gets removed. And so on.

The cause for the segfault is changeset 412385b57dc4. I discovered
this problem on October 25 and fixed it in changeset b0708fac99dd. The
current version on hg.marmaro.de/masqmail has the problem fixed.


Pierre, could you please try current tip and verify that it works for
you. Either clone the mercurial repo:

	hg clone http://hg.marmaro.de/masqmail

or use this tarball:

	http://hg.marmaro.de/masqmail/archive/b0708fac99dd.tar.gz


meillo