Re: [Dbmail-dev] Uidvalidity not changing
Geo Carncross wrote: Now, I recommend that servers make FETCH+ENVELOPE fast, and client implementers should use: x FETCH 1:* ENVELOPE *Very* cheap in dbmail atm. -- Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlandshttp://www.nfg.nl
Re: [Dbmail-dev] dbmail-pop3d and order
Just kidding, I broke my subversion client's SSL linkage. Will try to get this committed tomorrow. On Mon, 2006-09-18 at 14:40 -0700, Aaron Stone wrote: Done. On Mon, 2006-09-18 at 16:14 -0400, Geo Carncross wrote: Put message_idnr ASC first. Don't order by status; Consider what happens if another client changes the status after UIDL but before TOP? If they exclusively use POP3 clients, they'll see it ordered by status anyway (because new messages will be at the bottom). ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Re: [Dbmail-dev] building ubuntu packages
Paul J Stevens [EMAIL PROTECTED] schrieb: Lars Kneschke wrote: Hello! I like to have dbmail and libsieve packages for ubuntu. Bulding dbmail packages itself is quite easy. It works out of the box. But building libsieve is a little bit tricky. So far there exists no working deb package. libsieve is now part of debian/unstable. It's called libsieve2-1 Thanks! I have downloaded the source files and rebuild the packages under ubuntu.
[Dbmail-dev] Forwarding from Client
Hi I am using DBMail + postfix for the past one year. Have settled down to 2.0.9 version for the past few months. The system is very much stable and hence and havent done any digging of late. 1. My boss wants me to implement a system where all the mails are downloaded by one person and then forward it to the various users/departments. A facility is needed to mark a mail as 'to-be-replied' by a particular user, while forwarding. A report need to be generated with all the e-mails which was marked to-be-replied and that was not replied in 2 days. 2. The forwared mails should have the actual 'sender' in-tact, ie, the receiver should as if receive it as if from the original sender, not the intermediate person. The second one, I had successfully implemented by modifying 'Phoenix Mail' email client. But I need a more generic solution from the dbmail side. Plz suggest ways to do these. regards Nataraj
Re: [Dbmail-dev] Forwarding from Client
You need some sort of ticket system? I wouldn't use dbmail itself for this kind of sorting but some kind of script. What do you mean with downloading? from a pop-source? If you use fetchmail, the original sender stays intact. For checking if the message is replied within 2 days you can check everyday if the imap replied flag has been set, And compare it with the message-date. You'd need to create a cron script for this. /marc
[Dbmail-dev] Re dbmail bug report 405
Paul,
even though these warning are harmless they should be fixed, this is
minor yes but still will save you and aaron and the list time not
answering this question again so I belive this is the best fix:
diff -urNb dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c
dbmail-svn-2.1.8-2270/modules/dbmysql.c
--- dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c2006-09-18
14:27:31.0 -0400
+++ dbmail-svn-2.1.8-2270/modules/dbmysql.c 2006-09-19
07:17:57.0 -0400
@@ -236,7 +236,7 @@
return NULL;
}
- if ((row = db_num_rows()) || (field = db_num_fields())) {
+ if ((row db_num_rows()) || (field db_num_fields())) {
trace(TRACE_WARNING, %s, %s:
row = %u, field = %u, bigger than size of result set,
__FILE__, __func__, row, field);
@@ -266,7 +266,7 @@
result = last_row[field];
if (result == NULL)
- trace(TRACE_WARNING, %s,%s: result is null\n,
+ trace(TRACE_DEBUG, %s,%s: result is null\n,
__FILE__, __func__);
return result;
}
the first diff is because you get a erounous bigger than size of result
set for row == 0 and field == 0 which is not what I belive that warning
was ment for. and the second addresses report 405 and just makes it a
debuging message only if you and aaron don't want to remove that
completly.
as always just my 0.02 :)
Thanks,
Leif
Re: [Dbmail-dev] Forwarding from Client
Seems like shared folders are the way to go here; having one person have access to everyone elses' INBOX directly. What's the status on shared folders in DBMail? The IMAP Followup flag is almost universally supported, so it can be used for to-be-replied. For tracking if messages have been replied to, well I would use a shim. On Qmail this is very easy to do; simply put recordio in front of qmail-smtpd and egrep for Message-ID|References|In-Reply-To. This log could be used to determine if a message was replied to, and when it was received, for the purposes of reporting. I'm sure it would be fairly trivial to adapt this for postfix or dbmail's smtpd. Awk and grep are a beautiful thing. On Tue, 2006-09-19 at 16:45 +0530, Nataraj S Narayan wrote: Hi I am using DBMail + postfix for the past one year. Have settled down to 2.0.9 version for the past few months. The system is very much stable and hence and havent done any digging of late. 1. My boss wants me to implement a system where all the mails are downloaded by one person and then forward it to the various users/departments. A facility is needed to mark a mail as 'to-be-replied' by a particular user, while forwarding. A report need to be generated with all the e-mails which was marked to-be-replied and that was not replied in 2 days. 2. The forwared mails should have the actual 'sender' in-tact, ie, the receiver should as if receive it as if from the original sender, not the intermediate person. The second one, I had successfully implemented by modifying 'Phoenix Mail' email client. But I need a more generic solution from the dbmail side. Plz suggest ways to do these. regards Nataraj ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev -- Internet Connection High Quality Web Hosting http://www.internetconnection.net/
Re: [Dbmail-dev] Re dbmail bug report 405
fix applied (to dbpgsql.c as well).
thanks,
Leif Jackson wrote:
Paul,
even though these warning are harmless they should be fixed, this is
minor yes but still will save you and aaron and the list time not
answering this question again so I belive this is the best fix:
diff -urNb dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c
dbmail-svn-2.1.8-2270/modules/dbmysql.c
--- dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c2006-09-18
14:27:31.0 -0400
+++ dbmail-svn-2.1.8-2270/modules/dbmysql.c 2006-09-19
07:17:57.0 -0400
@@ -236,7 +236,7 @@
return NULL;
}
- if ((row = db_num_rows()) || (field = db_num_fields())) {
+ if ((row db_num_rows()) || (field db_num_fields())) {
trace(TRACE_WARNING, %s, %s:
row = %u, field = %u, bigger than size of result set,
__FILE__, __func__, row, field);
@@ -266,7 +266,7 @@
result = last_row[field];
if (result == NULL)
- trace(TRACE_WARNING, %s,%s: result is null\n,
+ trace(TRACE_DEBUG, %s,%s: result is null\n,
__FILE__, __func__);
return result;
}
the first diff is because you get a erounous bigger than size of result
set for row == 0 and field == 0 which is not what I belive that warning
was ment for. and the second addresses report 405 and just makes it a
debuging message only if you and aaron don't want to remove that
completly.
as always just my 0.02 :)
Thanks,
Leif
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlandshttp://www.nfg.nl
Re: [Dbmail-dev] Re dbmail bug report 405
can you please also get the row is NULL above the result is NULL I missed
that in my patch.
Thanks,
Leif
On Tue, September 19, 2006 9:23 am, Paul J Stevens wrote:
fix applied (to dbpgsql.c as well).
thanks,
Leif Jackson wrote:
Paul,
even though these warning are harmless they should be fixed, this is
minor yes but still will save you and aaron and the list time not
answering this question again so I belive this is the best fix:
diff -urNb dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c
dbmail-svn-2.1.8-2270/modules/dbmysql.c ---
dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c2006-09-18
14:27:31.0 -0400
+++ dbmail-svn-2.1.8-2270/modules/dbmysql.c 2006-09-19
07:17:57.0 -0400
@@ -236,7 +236,7 @@
return NULL; }
- if ((row = db_num_rows()) || (field = db_num_fields())) {
+ if ((row db_num_rows()) || (field db_num_fields())) {
trace(TRACE_WARNING, %s, %s: row = %u, field = %u, bigger than size
of result set, __FILE__, __func__, row, field);
@@ -266,7 +266,7 @@
result = last_row[field]; if (result == NULL) -
trace(TRACE_WARNING, %s,%s: result is null\n, +
trace(TRACE_DEBUG, %s,%s: result is null\n, __FILE__, __func__);
return result; }
the first diff is because you get a erounous bigger than size of result
set for row == 0 and field == 0 which is not what I belive that
warning was ment for. and the second addresses report 405 and just makes
it a debuging message only if you and aaron don't want to remove that
completly.
as always just my 0.02 :)
Thanks,
Leif
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlandshttp://www.nfg.nl
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Re: [Dbmail-dev] Re dbmail bug report 405
ok.
Leif Jackson wrote:
can you please also get the row is NULL above the result is NULL I missed
that in my patch.
Thanks,
Leif
On Tue, September 19, 2006 9:23 am, Paul J Stevens wrote:
fix applied (to dbpgsql.c as well).
thanks,
Leif Jackson wrote:
Paul,
even though these warning are harmless they should be fixed, this is
minor yes but still will save you and aaron and the list time not
answering this question again so I belive this is the best fix:
diff -urNb dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c
dbmail-svn-2.1.8-2270/modules/dbmysql.c ---
dbmail-svn-2.1.8-2270.orig/modules/dbmysql.c2006-09-18
14:27:31.0 -0400
+++ dbmail-svn-2.1.8-2270/modules/dbmysql.c 2006-09-19
07:17:57.0 -0400
@@ -236,7 +236,7 @@
return NULL; }
- if ((row = db_num_rows()) || (field = db_num_fields())) {
+ if ((row db_num_rows()) || (field db_num_fields())) {
trace(TRACE_WARNING, %s, %s: row = %u, field = %u, bigger than size
of result set, __FILE__, __func__, row, field);
@@ -266,7 +266,7 @@
result = last_row[field]; if (result == NULL) -
trace(TRACE_WARNING, %s,%s: result is null\n, +
trace(TRACE_DEBUG, %s,%s: result is null\n, __FILE__, __func__);
return result; }
the first diff is because you get a erounous bigger than size of result
set for row == 0 and field == 0 which is not what I belive that
warning was ment for. and the second addresses report 405 and just makes
it a debuging message only if you and aaron don't want to remove that
completly.
as always just my 0.02 :)
Thanks,
Leif
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlandshttp://www.nfg.nl
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
___
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
--
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlandshttp://www.nfg.nl
Re: [Dbmail-dev] outlook/outlook express with sieve
Aaron, I've missed your input about this sofar. Did you mis my last 2 emails? /Marc Op 10-sep-2006, om 5:13 heeft Aaron Stone het volgende geschreven: I inserted your script in my testing database, sent myself an email, and received the vacation reply. Looks great in Evolution. Here's some information about Outlook: http://trac.edgewall.org/ticket/1065 In particular, this comment looked useful: This is a pure Outlook error. It can be solved by seetting an option in MS Outlook. You can find the option here (don't know the exact english phrases, I have a German Outlook): Extras -- Options... -- Email format -- Fonts ... -- International Fonts ... Highlight Unicode in the language list, select Courier New as the proportional font, and chose Unicode (UTF-8) as encoding. Maybe that'll work for you? If every person who uses Outlook and receives your messages has to make this settings change, it's not quite so good as just having it work in the first place... but let me know if this does resolve the issue. Aaron On Sun, 2006-09-10 at 00:36 +0200, Marc Dirix wrote: Hi, It took me some time, to find a free M$ computer, but attached are the message files. I did an select on the dbmail_sieve table, for the actual script I inserted. Als a select on dbmail_messageblks with the message being ready to be popped by the outlook client. The I saved the message after it being popped by outlook 2003, found the message headers missing and saved the to a seperate file. Hope this helps in any way, best regards, Marc Dirix ___ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://twister.fastxs.net/mailman/listinfo/dbmail-dev
Re: [Dbmail-dev] outlook/outlook express with sieve
Marc Dirix wrote: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Have you tried setting up your encoding differently? 8bit messages I have in my mailbox just contain: Content-Type: text/plain Content-Transfer-Encoding: 8bit So perhaps leaving out the charset is enough. Your mutt experiment seems to confirm this. -- Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlandshttp://www.nfg.nl
