Is kolab srewing up other people's gnupg signatures?
kloecker at kde.org
Mon Apr 21 21:54:15 CEST 2008
On Monday 21 April 2008, Johannes Graumann wrote:
> Ingo Klöcker wrote:
> > On Saturday 19 April 2008, Johannes Graumann wrote:
> >> Ingo Klöcker wrote:
> >> > On Wednesday 16 April 2008, Johannes Graumann wrote:
> >> >> > Something in the kolab suite might/is messing up the message
> >> >> > header and invalidates thereby the signature. How might I
> >> >> > track this? Who's a likely perpetrator? Do other people see
> >> >> > this or is it something I messed up in the configuration?
> >> >>
> >> >> And btw: looking at the message source at googlemail: they have
> >> >> it right, so Kolab definitely is to blame ...
> >> >
> >> > Definitely? It could as well be fetchmail. How do you insert the
> >> > message into Kolab via fetchmail?
> >> Like this:
> >> set postmaster "postmaster at morannon.homelinux.org"
> >> poll imap.gmail.com with
> >> proto imap
> >> user "johannes.graumann at googlemail.com"
> >> pass "<I'M NOT TELLING>"
> >> is "johannes.graumann at morannon.homelinux.org"
> >> here
> >> no keep
> >> ssl
> >> smtpaddress "morannon.homelinux.org"
> >> limit 100000000
> >> mimedecode
> > The only peculiar thing seems to be the 'mimedecode' option. Have
> > you tried without?
> It's one of the attempts to deal with the problem ... it doesn't
> change anything.
Hmm. Did you already try Bernhard's suggestion? He wrote:
> Next you would need to proof which component damages the email.
> There are several ways to do this. One is to sniff the network
> connections and see if the incoming email to Kolab's postfix is still
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 194 bytes
Desc: This is a digitally signed message part.
More information about the users