Howdy,
Just a thought, in the next DBMail version, I mean in 2.5x, why not update
Gmime to 2.6?
This may have new things that turn to be interesting for DBMail!
http://jeffreystedfast.blogspot.com/2009/04/making-gmime-even-more-awesome.h
tml
Jorge,
> Don't us MS Products - Thats My Motto! I don't recall the whole thing
Well, right now I do, but didn't in the past.
But 90% of people use it as you know, that's the problem!!
> on
> what gmime is good - which is bad. I have gmime-2.2.23 on my system
> without issue. But then again, I don't get
Jorge Bastos wrote:
>
> I ask this ‘cause I have with 2.3.6 some problems on the From:
> address’s, on MSoutlook 2007, it show’s the encoded string instead of
> the correct value.
>
Don't us MS Products - Thats My Motto! I don't recall the whole thing on
what gmime is good - which is bad. I have
Hi there,
When there was a big discursion about gmime conversion problems, I remember
Paul saying that there was some gmime problems in ealier versions than
2.2.23.
Am I correct? If someone has this on his memory please answer :P
I ask this 'cause I have with 2.3.6 some problems on the From:
Paul Stevens wrote:
>> Is anyone using gmime 2.4x with dbmail, or is dbmail ready for it?
>
> I'm not. Should be safe though.
Hi Paul,
This is what I get when I try to compile 2.3.5 with gmime-2.4.
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions
Jorge Bastos wrote:
Hi,
Is anyone using gmime 2.4x with dbmail, or is dbmail ready for it?
I'm not. Should be safe though.
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP
Hi,
Is anyone using gmime 2.4x with dbmail, or is dbmail ready for it?
Thanks,
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Ok, I updated SVN again -- pine was still puking on empty lists -- such
as the common "Undisclosed-recipients: ;" -- so I've special cased it
(but it's not a hack, it's just checking for a "(NIL)" result string :-)
I tested on an INBOX with about 20k messages, and pine is happy now.
Aaron
On Tue
Turns out this is caused by us not at all handling Gmime's
InternetAddress/InternetAddressList data type correctly -- a pretty bad
case of following the wrong side of a union.
I've updated dbmail_imap_append_alist_as_plist in dm_imaputil.c to try
to be more correct. Now in SVN. Please report back
I get the following results with the code below. Only the first is
usable, of course. The latter two are causing Pine to blow chunks. I'm
on Gmime 2.2.1 (latest is 2.2.3, however).
((NIL NIL "i_am_not" "broken.org"))
(("Break me" NIL NIL
"��
On Tue, 2006-08-08 at 12:31 -0700, [EMAIL PROTECTED] wrote:
> I'm trying to upgrade to 2.1.7 with gmime 2.1.19 or 2.2.3 but getting
> the following error in dbmail make install.
>
> dbmail-mailbox.c: In function `_merge_search':
> dbmail-mailbox.c:1363: error: `G_TRAVERSE_LEAVES' undeclared (firs
I'm trying to upgrade to 2.1.7 with gmime 2.1.19 or 2.2.3 but getting
the following error in dbmail make install.
dbmail-mailbox.c: In function `_merge_search':
dbmail-mailbox.c:1363: error: `G_TRAVERSE_LEAVES' undeclared (first use
in this function)
dbmail-mailbox.c:1363: error: (Each undeclar
Aaron Stone wrote:
> Do you know what the representation of 3-4 Received headers looks like in
> that single-valued return from g_mime_object_get_header? I'm curious to
> see if they've just concatenated each instance of the header, or just used
> the first or who knows what.
iirc, it returns th
On Tue, Feb 14, 2006, Paul J Stevens <[EMAIL PROTECTED]> said:
Aaron Stone wrote:
>> Paul,
>>
>> How does GMime handle headers with multiple values? Received, for
>> example, typically has 3-5 header-value pairs in a given message. But
>> the GMime function we're using returns only a single char
Aaron Stone wrote:
> Paul,
>
> How does GMime handle headers with multiple values? Received, for
> example, typically has 3-5 header-value pairs in a given message. But
> the GMime function we're using returns only a single char *
Yeah I know. That's what the GRelation *headers was meant for
or
Paul,
How does GMime handle headers with multiple values? Received, for
example, typically has 3-5 header-value pairs in a given message. But
the GMime function we're using returns only a single char *
gchar * dbmail_message_get_header(
const struct DbmailMessage *self, const char *header
which seems a little like overkill to me.
That does seem like overkill. Gmime docs say it only
requires GNU make/
autotools, glib, and pkg-config. I don't have X on my box and
gmime compiles
cleanly..
yeah it's overkill - but only if you build it from an unmodified
ports makefile :)
I just
which seems a little like overkill to me.
That does seem like overkill. Gmime docs say it only
requires GNU make/
autotools, glib, and pkg-config. I don't have X on my box and
gmime compiles
cleanly..
yeah it's overkill - but only if you build it from an unmodified
ports makefile :)
I just
> > which seems a little like overkill to me.
>
> That does seem like overkill. Gmime docs say it only
> requires GNU make/
> autotools, glib, and pkg-config. I don't have X on my box and
> gmime compiles
> cleanly..
yeah it's overkill - but only if you build it from an unmodified
ports ma
On Tue, Nov 09, 2004 at 11:57:32AM -0800, Sean Chittenden wrote:
> Anyway, in trying HEAD, I unpleasantly discovered that dbmail now
> depends on glib and gmime2 (yuk!). gmime requires imake, which
> requires xorg-libraries. On FreeBSD, the list of packages required for
> gmime to operate corr
dbmail_2_0_branch is broken at the moment so I'm trying to use HEAD,
which, incidentally, doesn't seem to have the same problem with
spinning indefinitely (yay!) *rolls HEAD out to production*
Is there a better branch to use?
Anyway, in trying HEAD, I unpleasantly discovered that dbmail now
21 matches
Mail list logo
