Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: DBMail: dev

New Idea

 

 

DBMail dev RSS feed   Index | Next | Previous | View Threaded


mysql.jorge at decimal

Jun 12, 2009, 6:05 AM

Post #1 of 24 (3892 views)
Permalink
New Idea

Hi there Paul,

I'd like to ask you "permission" for something,

Can I write a patch (I'm going to try to do it since I'm not a big C coder),
to:



.. Add an extra field for the dbmail_users table, named "last_ip". I
think this is a useful info, aswell the last_login is a very good info, and
very handy sometimes for me.

.. Where the last_login field is updated, make it update the last_ip
field



Do you think this can go to the main dev?

I could do this only for me but, this may be public interest too.



Will you add this?



Jorge,


jesse at kci

Jun 12, 2009, 7:59 AM

Post #2 of 24 (3806 views)
Permalink
Re: New Idea [In reply to]

That's exactly what dbmail_pbsp does already, just in a separate table.
Maybe you just need to enable pbsp in your config file? (I don't
remember that support being removed, but it's possible. It's still in
the sql schema though.)


On Fri, 2009-06-12 at 14:05 +0100, Jorge Bastos wrote:
> Hi there Paul,
>
> I’d like to ask you “permission” for something,
>
> Can I write a patch (I’m going to try to do it since I’m not a big C
> coder), to:
>
>
>
> · Add an extra field for the dbmail_users table, named
> “last_ip”. I think this is a useful info, aswell the last_login is a
> very good info, and very handy sometimes for me.
>
> · Where the last_login field is updated, make it update the
> last_ip field
>
>
>
> Do you think this can go to the main dev?
>
> I could do this only for me but, this may be public interest too.
>
>
>
> Will you add this?
>
>
>
> Jorge,
>
>
>
>
>
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
--
Jesse Norell
Kentec Communications, Inc.
jesse [at] kci
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


James at host-it

Jun 12, 2009, 7:59 AM

Post #3 of 24 (3807 views)
Permalink
Re: New Idea [In reply to]

Just a quick note. Whoever codes this we would also be interested in this field. We often have POP3 customers complain that they cannot see their mail via imap/webmail only to find that someone else in their office is collecting via pop3. They deny this until we provide them with the IP address collecting via POP3 from dbmail-pop3d logs.

Kind Regards

James Greig

From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-bounces [at] dbmail] On Behalf Of Jorge Bastos
Sent: 12 June 2009 14:05
To: 'DBMAIL Developers Mailinglist'
Subject: [Dbmail-dev] New Idea

Hi there Paul,
I'd like to ask you "permission" for something,
Can I write a patch (I'm going to try to do it since I'm not a big C coder), to:


* Add an extra field for the dbmail_users table, named "last_ip". I think this is a useful info, aswell the last_login is a very good info, and very handy sometimes for me.

* Where the last_login field is updated, make it update the last_ip field

Do you think this can go to the main dev?
I could do this only for me but, this may be public interest too.

Will you add this?

Jorge,


vulture at netvulture

Jun 12, 2009, 9:55 AM

Post #4 of 24 (3799 views)
Permalink
Re: New Idea [In reply to]

Jesse Norell wrote:
> That's exactly what dbmail_pbsp does already, just in a separate table.
> Maybe you just need to enable pbsp in your config file? (I don't
> remember that support being removed, but it's possible. It's still in
> the sql schema though.)
>
The pbsp is only used with the pop3 daemon. Also, there is no attachment
of user to ip in that table. Just the timestamp and IP is stored so that
the smtp can determine that the sending IP did authenticate recently.

A better approach to this would probably be a security log table.
user_idnr, service, login_time, logout_time, session_id, session_status,
ip_address, tcp_port.
This essentially would require a new table, and some db_update calls in
the right places.

Cleaning of this table would be manual -or manually(cron) via dbmail-util.

-Jon

--
Scanned for viruses and dangerous content by MailScanner

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 12, 2009, 10:06 AM

Post #5 of 24 (3811 views)
Permalink
Re: New Idea [In reply to]

I would like to go that way.
I must say, for my experience that POP-before-SMTP is a dead tech.

> -----Original Message-----
> From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-
> bounces [at] dbmail] On Behalf Of Jesse Norell
> Sent: sexta-feira, 12 de Junho de 2009 16:00
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] New Idea
>
> That's exactly what dbmail_pbsp does already, just in a separate table.
> Maybe you just need to enable pbsp in your config file? (I don't
> remember that support being removed, but it's possible. It's still in
> the sql schema though.)
>
>
> On Fri, 2009-06-12 at 14:05 +0100, Jorge Bastos wrote:
> > Hi there Paul,
> >
> > I’d like to ask you “permission” for something,
> >
> > Can I write a patch (I’m going to try to do it since I’m not a big C
> > coder), to:
> >
> >
> >
> > · Add an extra field for the dbmail_users table, named
> > “last_ip”. I think this is a useful info, aswell the last_login is a
> > very good info, and very handy sometimes for me.
> >
> > · Where the last_login field is updated, make it update the
> > last_ip field
> >
> >
> >
> > Do you think this can go to the main dev?
> >
> > I could do this only for me but, this may be public interest too.
> >
> >
> >
> > Will you add this?
> >
> >
> >
> > Jorge,
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Dbmail-dev mailing list
> > Dbmail-dev [at] dbmail
> > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
> --
> Jesse Norell
> Kentec Communications, Inc.
> jesse [at] kci
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


jesse at kci

Jun 12, 2009, 10:08 AM

Post #6 of 24 (3801 views)
Permalink
Re: New Idea [In reply to]

On Fri, 2009-06-12 at 09:55 -0700, Jonathan Feally wrote:
> Jesse Norell wrote:
> > That's exactly what dbmail_pbsp does already, just in a separate table.
> > Maybe you just need to enable pbsp in your config file? (I don't
> > remember that support being removed, but it's possible. It's still in
> > the sql schema though.)
> >
> The pbsp is only used with the pop3 daemon.

There are both pop_before_smtp and imap_before_smtp config values
(though I can't say that they still work, but on the ancient version
we're running they do).

> Also, there is no attachment
> of user to ip in that table. Just the timestamp and IP is stored so that
> the smtp can determine that the sending IP did authenticate recently.

Doh, indeed that's true; I misread that earlier.


> A better approach to this would probably be a security log table.
> user_idnr, service, login_time, logout_time, session_id, session_status,
> ip_address, tcp_port.
> This essentially would require a new table, and some db_update calls in
> the right places.

Agreed, that'd be a more useful setup. Also consider marking failed
login attempts (though you might resort to syslog for non-matching
usernames). There have been requests for logging the above as well as
messages/bytes transferred stats and such in the past, I have no idea
where things are at on that front, but could put those counters in as
well.


--
Jesse Norell
Kentec Communications, Inc.
jesse [at] kci
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 12, 2009, 10:10 AM

Post #7 of 24 (3807 views)
Permalink
Re: New Idea [In reply to]

> A better approach to this would probably be a security log table.
> user_idnr, service, login_time, logout_time, session_id,
> session_status,
> ip_address, tcp_port.
> This essentially would require a new table, and some db_update calls in
> the right places.
>
> Cleaning of this table would be manual -or manually(cron) via dbmail-
> util.

That's something good also, for me I would clean it monthly.
Apart from that, a simple approach for this is the "last_ip" on the
dbmail_users table, for now it's simpler and will fit for almost everybody I
think.

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 12, 2009, 10:13 AM

Post #8 of 24 (3810 views)
Permalink
Re: New Idea [In reply to]

> Agreed, that'd be a more useful setup. Also consider marking failed
> login attempts (though you might resort to syslog for non-matching
> usernames). There have been requests for logging the above as well as
> messages/bytes transferred stats and such in the past, I have no idea
> where things are at on that front, but could put those counters in as
> well.

I was the one who started that need to log that info, that and log something
like:

User,message_from,message_to,date_time,bytes (and something else)

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


vulture at netvulture

Jun 12, 2009, 5:26 PM

Post #9 of 24 (3798 views)
Permalink
Re: New Idea [In reply to]

Here is a preliminary patch.
It adds the dbmail_authlog table
Records the read and write byte counts as well.
Fixes pop3 client bailout process as well.

-Jon

Jorge Bastos wrote:
>> Agreed, that'd be a more useful setup. Also consider marking failed
>> login attempts (though you might resort to syslog for non-matching
>> usernames). There have been requests for logging the above as well as
>> messages/bytes transferred stats and such in the past, I have no idea
>> where things are at on that front, but could put those counters in as
>> well.
>>
>
> I was the one who started that need to log that info, that and log something
> like:
>
> User,message_from,message_to,date_time,bytes (and something else)
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
>
>


--
Scanned for viruses and dangerous content by MailScanner
Attachments: 0001-Add-dbmail_authlog-table-and-code-to-record-logins-a.patch (17.2 KB)


mysql.jorge at decimal

Jun 13, 2009, 2:57 AM

Post #10 of 24 (3783 views)
Permalink
Re: New Idea [In reply to]

Paul?


John, why on dbmail-imapsession.c ?

> Here is a preliminary patch.
> It adds the dbmail_authlog table
> Records the read and write byte counts as well.
> Fixes pop3 client bailout process as well.
>
> -Jon
>

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 13, 2009, 3:02 AM

Post #11 of 24 (3776 views)
Permalink
Re: New Idea [In reply to]

> John, why on dbmail-imapsession.c ?
>

Ops, sorry john, didn't saw the part on pop3.c, I'm still sleepy :-)



_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 13, 2009, 3:25 AM

Post #12 of 24 (3785 views)
Permalink
Re: New Idea [In reply to]

John,
Testing, it seems that there's only one small issue, doing a login and
logout, I get:

INSERT INTO `dbmail_authlog` (`id`, `userid`, `service`, `login_time`,
`logout_time`, `ip_address`, `src_port`, `session_id`, `session_status`,
`bytes_rx`, `bytes_tx`) VALUES (3, 'test [at] albergaria', 'imap', '2009-06-13
11:23:30', '2009-06-13 11:23:32', '192.168.1.221', 54672, '0x9e9ade8',
'closed', 166319344, 91);

"166319344" bytes RX, well not possible!!

Trying 192.168.1.221...
Connected to flecha.
Escape character is '^]'.
* OK imap 4r1 server (dbmail 2.3.6)
aa login test [at] albergaria 123456
aa OK LOGIN completed
aa logout
* BYE
aa OK LOGOUT completed
Connection closed by foreign host.



> -----Original Message-----
> From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-
> bounces [at] dbmail] On Behalf Of Jorge Bastos
> Sent: sbado, 13 de Junho de 2009 11:03
> To: 'DBMAIL Developers Mailinglist'
> Subject: Re: [Dbmail-dev] New Idea
>
> > John, why on dbmail-imapsession.c ?
> >
>
> Ops, sorry john, didn't saw the part on pop3.c, I'm still sleepy :-)
>
>
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


vulture at netvulture

Jun 13, 2009, 1:26 PM

Post #13 of 24 (3774 views)
Permalink
Re: New Idea [In reply to]

Jorge Bastos wrote:
> "166319344" bytes RX, well not possible!!
>
I assumed that the values would start at 0. I have set them to 0 at the
clientbase_t creation so give that a shot.

-Jon

--
Scanned for viruses and dangerous content by MailScanner
Attachments: 0001-Add-dbmail_authlog-table-and-code-to-record-logins-a.patch (17.6 KB)


mysql.jorge at decimal

Jun 13, 2009, 1:49 PM

Post #14 of 24 (3767 views)
Permalink
Re: New Idea [In reply to]

It seems to me perfect now.
John, could it possible for you, just to add a configuration parameter to
the [dbmail] section on dbmail.conf, to enable/disable this facility?

Paul,
Could you include this for 2.3.6?



> -----Original Message-----
> From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-
> bounces [at] dbmail] On Behalf Of Jonathan Feally
> Sent: sbado, 13 de Junho de 2009 21:26
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] New Idea
>
> Jorge Bastos wrote:
> > "166319344" bytes RX, well not possible!!
> >
> I assumed that the values would start at 0. I have set them to 0 at the
> clientbase_t creation so give that a shot.
>
> -Jon
>
> --
> Scanned for viruses and dangerous content by MailScanner


_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 13, 2009, 2:07 PM

Post #15 of 24 (3774 views)
Permalink
Re: New Idea [In reply to]

> It seems to me perfect now.
> John, could it possible for you, just to add a configuration parameter
> to
> the [dbmail] section on dbmail.conf, to enable/disable this facility?


Ops, not perfect, it dies on logout, both pop3 and imap, traces for pop3 and
imap below:

(gdb) run -D
Starting program: /usr/local/sbin/dbmail-pop3d -D
[Thread debugging using libthread_db enabled]
[New Thread 0xb75166c0 (LWP 18264)]
[New Thread 0xb74fcb90 (LWP 18271)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb75166c0 (LWP 18264)]
db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
1786 if (msg->virtual_messagestatus !=
msg->messagestatus) {
(gdb) bt
#0 db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
#1 0x0804a0e0 in pop3_session_cleanup (arg=0x8c8a540) at pop3.c:252
#2 0xb7d62ace in client_session_bailout (session=0xbfb1e37c) at
clientsession.c:111
#3 0x0804b721 in pop3_cb_write (arg=0x8c8a540) at pop3.c:217
#4 0xb7d62b7e in socket_write_cb (fd=16, what=4, arg=0x8c8a540) at
clientsession.c:167
#5 0xb7df1d50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
#6 0xb7df1f49 in event_loop () from /usr/lib/libevent-1.4.so.2
#7 0xb7df1f6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
#8 0xb7d618b1 in server_run (conf=0xbfb1e5c0) at server.c:637
#9 0xb7d625d9 in server_mainloop (config=0xbfb1e5c0, service=0x804c253
"POP",
servicename=0x804c602 "dbmail-pop3d") at server.c:761
#10 0x0804b7d8 in main (argc=2, argv=0xbfb216a4) at pop3d.c:58
(gdb) f0
Undefined command: "f0". Try "help".
(gdb) f 0
#0 db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
1786 if (msg->virtual_messagestatus !=
msg->messagestatus) {
(gdb) f 1
#1 0x0804a0e0 in pop3_session_cleanup (arg=0x8c8a540) at pop3.c:252
252 if (db_update_pop(session) == DM_SUCCESS) r
= 1;
(gdb) f 2
#2 0xb7d62ace in client_session_bailout (session=0xbfb1e37c) at
clientsession.c:111
111 if(c->session_cleanup) c->session_cleanup(c);
(gdb) f 3
#3 0x0804b721 in pop3_cb_write (arg=0x8c8a540) at pop3.c:217
217 client_session_bailout(&session);
(gdb) f 4
#4 0xb7d62b7e in socket_write_cb (fd=16, what=4, arg=0x8c8a540) at
clientsession.c:167
167 session->ci->cb_write(session);
(gdb) f 5
#5 0xb7df1d50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
(gdb) f 6
#6 0xb7df1f49 in event_loop () from /usr/lib/libevent-1.4.so.2
(gdb) f 7
#7 0xb7df1f6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
(gdb) f 8
#8 0xb7d618b1 in server_run (conf=0xbfb1e5c0) at server.c:637
637 event_dispatch();
(gdb) f 9
#9 0xb7d625d9 in server_mainloop (config=0xbfb1e5c0, service=0x804c253
"POP",
servicename=0x804c602 "dbmail-pop3d") at server.c:761
761 while (server_run(config)) {
(gdb) f 10
#10 0x0804b7d8 in main (argc=2, argv=0xbfb216a4) at pop3d.c:58
58 result = server_mainloop(&config, "POP", "dbmail-pop3d");
(gdb)



(gdb) run -D
Starting program: /usr/local/sbin/dbmail-imapd -D
[Thread debugging using libthread_db enabled]
[New Thread 0xb75516c0 (LWP 18279)]
[New Thread 0xb7537b90 (LWP 18282)]
[New Thread 0xb6d37b90 (LWP 18283)]
[New Thread 0xb6537b90 (LWP 18284)]
[New Thread 0xb5d37b90 (LWP 18285)]
[New Thread 0xb5537b90 (LWP 18286)]
[New Thread 0xb4d37b90 (LWP 18287)]
[New Thread 0xb4537b90 (LWP 18288)]
[New Thread 0xb3d37b90 (LWP 18289)]
[New Thread 0xb3537b90 (LWP 18290)]
[New Thread 0xb2d37b90 (LWP 18291)]
[New Thread 0xb2537b90 (LWP 18292)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb75516c0 (LWP 18279)]
0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
dbmail-imapsession.c:166
166 db_update("UPDATE %sauthlog SET logout_time=NOW(),
session_status='closed', bytes_rx='%d', bytes_tx='%d' WHERE ip_address='%s'
AND src_port='%d' AND session_status='active' AND session_id='%p'",
(gdb) bt
#0 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
dbmail-imapsession.c:166
#1 0x0804ea4b in imap_session_bailout (session=0x80d9960) at imap4.c:98
#2 0xb7e2cd50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
#3 0xb7e2cf49 in event_loop () from /usr/lib/libevent-1.4.so.2
#4 0xb7e2cf6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
#5 0xb7d9c8b1 in server_run (conf=0xbfcb53c0) at server.c:637
#6 0xb7d9d5d9 in server_mainloop (config=0xbfcb53c0, service=0x805c9b4
"IMAP",
servicename=0x805f867 "dbmail-imapd") at server.c:761
#7 0x0805c447 in main (argc=2, argv=0xbfcb84a4) at imapd.c:70
(gdb) f0
Undefined command: "f0". Try "help".
(gdb) f 0
#0 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
dbmail-imapsession.c:166
166 db_update("UPDATE %sauthlog SET logout_time=NOW(),
session_status='closed', bytes_rx='%d', bytes_tx='%d' WHERE ip_address='%s'
AND src_port='%d' AND session_status='active' AND session_id='%p'",
(gdb) f 1
#1 0x0804ea4b in imap_session_bailout (session=0x80d9960) at imap4.c:98
98 dbmail_imap_session_delete(session);
(gdb) f 2
#2 0xb7e2cd50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
(gdb) f 3
#3 0xb7e2cf49 in event_loop () from /usr/lib/libevent-1.4.so.2
(gdb) f 4
#4 0xb7e2cf6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
(gdb) f 5
#5 0xb7d9c8b1 in server_run (conf=0xbfcb53c0) at server.c:637
637 event_dispatch();
(gdb) f 6
#6 0xb7d9d5d9 in server_mainloop (config=0xbfcb53c0, service=0x805c9b4
"IMAP",
servicename=0x805f867 "dbmail-imapd") at server.c:761
761 while (server_run(config)) {
(gdb) f 7
#7 0x0805c447 in main (argc=2, argv=0xbfcb84a4) at imapd.c:70
70 result = server_mainloop(&config, "IMAP", "dbmail-imapd");
(gdb)

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


vulture at netvulture

Jun 13, 2009, 5:17 PM

Post #16 of 24 (3772 views)
Permalink
Re: New Idea [In reply to]

Hmm... Did you issue a quit or logout? Or just close the connection?
Does that make any difference? Adding an enable flag would be possible.

-Jon

Jorge Bastos wrote:
>> It seems to me perfect now.
>> John, could it possible for you, just to add a configuration parameter
>> to
>> the [dbmail] section on dbmail.conf, to enable/disable this facility?
>>
>
>
> Ops, not perfect, it dies on logout, both pop3 and imap, traces for pop3 and
> imap below:
>
> (gdb) run -D
> Starting program: /usr/local/sbin/dbmail-pop3d -D
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb75166c0 (LWP 18264)]
> [New Thread 0xb74fcb90 (LWP 18271)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb75166c0 (LWP 18264)]
> db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
> 1786 if (msg->virtual_messagestatus !=
> msg->messagestatus) {
> (gdb) bt
> #0 db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
> #1 0x0804a0e0 in pop3_session_cleanup (arg=0x8c8a540) at pop3.c:252
> #2 0xb7d62ace in client_session_bailout (session=0xbfb1e37c) at
> clientsession.c:111
> #3 0x0804b721 in pop3_cb_write (arg=0x8c8a540) at pop3.c:217
> #4 0xb7d62b7e in socket_write_cb (fd=16, what=4, arg=0x8c8a540) at
> clientsession.c:167
> #5 0xb7df1d50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> #6 0xb7df1f49 in event_loop () from /usr/lib/libevent-1.4.so.2
> #7 0xb7df1f6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> #8 0xb7d618b1 in server_run (conf=0xbfb1e5c0) at server.c:637
> #9 0xb7d625d9 in server_mainloop (config=0xbfb1e5c0, service=0x804c253
> "POP",
> servicename=0x804c602 "dbmail-pop3d") at server.c:761
> #10 0x0804b7d8 in main (argc=2, argv=0xbfb216a4) at pop3d.c:58
> (gdb) f0
> Undefined command: "f0". Try "help".
> (gdb) f 0
> #0 db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
> 1786 if (msg->virtual_messagestatus !=
> msg->messagestatus) {
> (gdb) f 1
> #1 0x0804a0e0 in pop3_session_cleanup (arg=0x8c8a540) at pop3.c:252
> 252 if (db_update_pop(session) == DM_SUCCESS) r
> = 1;
> (gdb) f 2
> #2 0xb7d62ace in client_session_bailout (session=0xbfb1e37c) at
> clientsession.c:111
> 111 if(c->session_cleanup) c->session_cleanup(c);
> (gdb) f 3
> #3 0x0804b721 in pop3_cb_write (arg=0x8c8a540) at pop3.c:217
> 217 client_session_bailout(&session);
> (gdb) f 4
> #4 0xb7d62b7e in socket_write_cb (fd=16, what=4, arg=0x8c8a540) at
> clientsession.c:167
> 167 session->ci->cb_write(session);
> (gdb) f 5
> #5 0xb7df1d50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> (gdb) f 6
> #6 0xb7df1f49 in event_loop () from /usr/lib/libevent-1.4.so.2
> (gdb) f 7
> #7 0xb7df1f6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> (gdb) f 8
> #8 0xb7d618b1 in server_run (conf=0xbfb1e5c0) at server.c:637
> 637 event_dispatch();
> (gdb) f 9
> #9 0xb7d625d9 in server_mainloop (config=0xbfb1e5c0, service=0x804c253
> "POP",
> servicename=0x804c602 "dbmail-pop3d") at server.c:761
> 761 while (server_run(config)) {
> (gdb) f 10
> #10 0x0804b7d8 in main (argc=2, argv=0xbfb216a4) at pop3d.c:58
> 58 result = server_mainloop(&config, "POP", "dbmail-pop3d");
> (gdb)
>
>
>
> (gdb) run -D
> Starting program: /usr/local/sbin/dbmail-imapd -D
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb75516c0 (LWP 18279)]
> [New Thread 0xb7537b90 (LWP 18282)]
> [New Thread 0xb6d37b90 (LWP 18283)]
> [New Thread 0xb6537b90 (LWP 18284)]
> [New Thread 0xb5d37b90 (LWP 18285)]
> [New Thread 0xb5537b90 (LWP 18286)]
> [New Thread 0xb4d37b90 (LWP 18287)]
> [New Thread 0xb4537b90 (LWP 18288)]
> [New Thread 0xb3d37b90 (LWP 18289)]
> [New Thread 0xb3537b90 (LWP 18290)]
> [New Thread 0xb2d37b90 (LWP 18291)]
> [New Thread 0xb2537b90 (LWP 18292)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb75516c0 (LWP 18279)]
> 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
> dbmail-imapsession.c:166
> 166 db_update("UPDATE %sauthlog SET logout_time=NOW(),
> session_status='closed', bytes_rx='%d', bytes_tx='%d' WHERE ip_address='%s'
> AND src_port='%d' AND session_status='active' AND session_id='%p'",
> (gdb) bt
> #0 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
> dbmail-imapsession.c:166
> #1 0x0804ea4b in imap_session_bailout (session=0x80d9960) at imap4.c:98
> #2 0xb7e2cd50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> #3 0xb7e2cf49 in event_loop () from /usr/lib/libevent-1.4.so.2
> #4 0xb7e2cf6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> #5 0xb7d9c8b1 in server_run (conf=0xbfcb53c0) at server.c:637
> #6 0xb7d9d5d9 in server_mainloop (config=0xbfcb53c0, service=0x805c9b4
> "IMAP",
> servicename=0x805f867 "dbmail-imapd") at server.c:761
> #7 0x0805c447 in main (argc=2, argv=0xbfcb84a4) at imapd.c:70
> (gdb) f0
> Undefined command: "f0". Try "help".
> (gdb) f 0
> #0 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
> dbmail-imapsession.c:166
> 166 db_update("UPDATE %sauthlog SET logout_time=NOW(),
> session_status='closed', bytes_rx='%d', bytes_tx='%d' WHERE ip_address='%s'
> AND src_port='%d' AND session_status='active' AND session_id='%p'",
> (gdb) f 1
> #1 0x0804ea4b in imap_session_bailout (session=0x80d9960) at imap4.c:98
> 98 dbmail_imap_session_delete(session);
> (gdb) f 2
> #2 0xb7e2cd50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> (gdb) f 3
> #3 0xb7e2cf49 in event_loop () from /usr/lib/libevent-1.4.so.2
> (gdb) f 4
> #4 0xb7e2cf6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> (gdb) f 5
> #5 0xb7d9c8b1 in server_run (conf=0xbfcb53c0) at server.c:637
> 637 event_dispatch();
> (gdb) f 6
> #6 0xb7d9d5d9 in server_mainloop (config=0xbfcb53c0, service=0x805c9b4
> "IMAP",
> servicename=0x805f867 "dbmail-imapd") at server.c:761
> 761 while (server_run(config)) {
> (gdb) f 7
> #7 0x0805c447 in main (argc=2, argv=0xbfcb84a4) at imapd.c:70
> 70 result = server_mainloop(&config, "IMAP", "dbmail-imapd");
> (gdb)
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
>
>


--
Scanned for viruses and dangerous content by MailScanner

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 13, 2009, 5:30 PM

Post #17 of 24 (3762 views)
Permalink
Re: New Idea [In reply to]

Issued the exit command for both, QUIT for pop3d and "aa LOGOUT" for imap.

About the enable flag in dbmail.config, I think it's better and maybe this
convince Paul to add this to the main line and for 2.3.6 :)




> -----Original Message-----
> From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-
> bounces [at] dbmail] On Behalf Of Jonathan Feally
> Sent: domingo, 14 de Junho de 2009 1:18
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] New Idea
>
> Hmm... Did you issue a quit or logout? Or just close the connection?
> Does that make any difference? Adding an enable flag would be possible.
>
> -Jon
>
> Jorge Bastos wrote:
> >> It seems to me perfect now.
> >> John, could it possible for you, just to add a configuration
> parameter
> >> to
> >> the [dbmail] section on dbmail.conf, to enable/disable this
> facility?
> >>
> >
> >
> > Ops, not perfect, it dies on logout, both pop3 and imap, traces for
> pop3 and
> > imap below:
> >
> > (gdb) run -D
> > Starting program: /usr/local/sbin/dbmail-pop3d -D
> > [Thread debugging using libthread_db enabled]
> > [New Thread 0xb75166c0 (LWP 18264)]
> > [New Thread 0xb74fcb90 (LWP 18271)]
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0xb75166c0 (LWP 18264)]
> > db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
> > 1786 if (msg->virtual_messagestatus !=
> > msg->messagestatus) {
> > (gdb) bt
> > #0 db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
> > #1 0x0804a0e0 in pop3_session_cleanup (arg=0x8c8a540) at pop3.c:252
> > #2 0xb7d62ace in client_session_bailout (session=0xbfb1e37c) at
> > clientsession.c:111
> > #3 0x0804b721 in pop3_cb_write (arg=0x8c8a540) at pop3.c:217
> > #4 0xb7d62b7e in socket_write_cb (fd=16, what=4, arg=0x8c8a540) at
> > clientsession.c:167
> > #5 0xb7df1d50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> > #6 0xb7df1f49 in event_loop () from /usr/lib/libevent-1.4.so.2
> > #7 0xb7df1f6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> > #8 0xb7d618b1 in server_run (conf=0xbfb1e5c0) at server.c:637
> > #9 0xb7d625d9 in server_mainloop (config=0xbfb1e5c0,
> service=0x804c253
> > "POP",
> > servicename=0x804c602 "dbmail-pop3d") at server.c:761
> > #10 0x0804b7d8 in main (argc=2, argv=0xbfb216a4) at pop3d.c:58
> > (gdb) f0
> > Undefined command: "f0". Try "help".
> > (gdb) f 0
> > #0 db_update_pop (session_ptr=0x8c8a540) at dm_db.c:1786
> > 1786 if (msg->virtual_messagestatus !=
> > msg->messagestatus) {
> > (gdb) f 1
> > #1 0x0804a0e0 in pop3_session_cleanup (arg=0x8c8a540) at pop3.c:252
> > 252 if (db_update_pop(session) ==
> DM_SUCCESS) r
> > = 1;
> > (gdb) f 2
> > #2 0xb7d62ace in client_session_bailout (session=0xbfb1e37c) at
> > clientsession.c:111
> > 111 if(c->session_cleanup) c->session_cleanup(c);
> > (gdb) f 3
> > #3 0x0804b721 in pop3_cb_write (arg=0x8c8a540) at pop3.c:217
> > 217 client_session_bailout(&session);
> > (gdb) f 4
> > #4 0xb7d62b7e in socket_write_cb (fd=16, what=4, arg=0x8c8a540) at
> > clientsession.c:167
> > 167 session->ci->cb_write(session);
> > (gdb) f 5
> > #5 0xb7df1d50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> > (gdb) f 6
> > #6 0xb7df1f49 in event_loop () from /usr/lib/libevent-1.4.so.2
> > (gdb) f 7
> > #7 0xb7df1f6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> > (gdb) f 8
> > #8 0xb7d618b1 in server_run (conf=0xbfb1e5c0) at server.c:637
> > 637 event_dispatch();
> > (gdb) f 9
> > #9 0xb7d625d9 in server_mainloop (config=0xbfb1e5c0,
> service=0x804c253
> > "POP",
> > servicename=0x804c602 "dbmail-pop3d") at server.c:761
> > 761 while (server_run(config)) {
> > (gdb) f 10
> > #10 0x0804b7d8 in main (argc=2, argv=0xbfb216a4) at pop3d.c:58
> > 58 result = server_mainloop(&config, "POP", "dbmail-
> pop3d");
> > (gdb)
> >
> >
> >
> > (gdb) run -D
> > Starting program: /usr/local/sbin/dbmail-imapd -D
> > [Thread debugging using libthread_db enabled]
> > [New Thread 0xb75516c0 (LWP 18279)]
> > [New Thread 0xb7537b90 (LWP 18282)]
> > [New Thread 0xb6d37b90 (LWP 18283)]
> > [New Thread 0xb6537b90 (LWP 18284)]
> > [New Thread 0xb5d37b90 (LWP 18285)]
> > [New Thread 0xb5537b90 (LWP 18286)]
> > [New Thread 0xb4d37b90 (LWP 18287)]
> > [New Thread 0xb4537b90 (LWP 18288)]
> > [New Thread 0xb3d37b90 (LWP 18289)]
> > [New Thread 0xb3537b90 (LWP 18290)]
> > [New Thread 0xb2d37b90 (LWP 18291)]
> > [New Thread 0xb2537b90 (LWP 18292)]
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0xb75516c0 (LWP 18279)]
> > 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
> > dbmail-imapsession.c:166
> > 166 db_update("UPDATE %sauthlog SET logout_time=NOW(),
> > session_status='closed', bytes_rx='%d', bytes_tx='%d' WHERE
> ip_address='%s'
> > AND src_port='%d' AND session_status='active' AND session_id='%p'",
> > (gdb) bt
> > #0 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
> > dbmail-imapsession.c:166
> > #1 0x0804ea4b in imap_session_bailout (session=0x80d9960) at
> imap4.c:98
> > #2 0xb7e2cd50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> > #3 0xb7e2cf49 in event_loop () from /usr/lib/libevent-1.4.so.2
> > #4 0xb7e2cf6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> > #5 0xb7d9c8b1 in server_run (conf=0xbfcb53c0) at server.c:637
> > #6 0xb7d9d5d9 in server_mainloop (config=0xbfcb53c0,
> service=0x805c9b4
> > "IMAP",
> > servicename=0x805f867 "dbmail-imapd") at server.c:761
> > #7 0x0805c447 in main (argc=2, argv=0xbfcb84a4) at imapd.c:70
> > (gdb) f0
> > Undefined command: "f0". Try "help".
> > (gdb) f 0
> > #0 0x0805c12b in dbmail_imap_session_delete (self=0x80d9960) at
> > dbmail-imapsession.c:166
> > 166 db_update("UPDATE %sauthlog SET logout_time=NOW(),
> > session_status='closed', bytes_rx='%d', bytes_tx='%d' WHERE
> ip_address='%s'
> > AND src_port='%d' AND session_status='active' AND session_id='%p'",
> > (gdb) f 1
> > #1 0x0804ea4b in imap_session_bailout (session=0x80d9960) at
> imap4.c:98
> > 98 dbmail_imap_session_delete(session);
> > (gdb) f 2
> > #2 0xb7e2cd50 in event_base_loop () from /usr/lib/libevent-1.4.so.2
> > (gdb) f 3
> > #3 0xb7e2cf49 in event_loop () from /usr/lib/libevent-1.4.so.2
> > (gdb) f 4
> > #4 0xb7e2cf6e in event_dispatch () from /usr/lib/libevent-1.4.so.2
> > (gdb) f 5
> > #5 0xb7d9c8b1 in server_run (conf=0xbfcb53c0) at server.c:637
> > 637 event_dispatch();
> > (gdb) f 6
> > #6 0xb7d9d5d9 in server_mainloop (config=0xbfcb53c0,
> service=0x805c9b4
> > "IMAP",
> > servicename=0x805f867 "dbmail-imapd") at server.c:761
> > 761 while (server_run(config)) {
> > (gdb) f 7
> > #7 0x0805c447 in main (argc=2, argv=0xbfcb84a4) at imapd.c:70
> > 70 result = server_mainloop(&config, "IMAP", "dbmail-
> imapd");
> > (gdb)
> >
> > _______________________________________________
> > Dbmail-dev mailing list
> > Dbmail-dev [at] dbmail
> > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
> >
> >
>
>
> --
> Scanned for viruses and dangerous content by MailScanner
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


paul at nfg

Jun 14, 2009, 6:19 AM

Post #18 of 24 (3741 views)
Permalink
Re: New Idea [In reply to]

Jonathan Feally wrote:
> Jorge Bastos wrote:
>> "166319344" bytes RX, well not possible!!
>>
> I assumed that the values would start at 0. I have set them to 0 at the
> clientbase_t creation so give that a shot.

Jon,

Not such a strange assumption, since you're using g_new0. Maybe the
unsignedness of the counters comes into play here.

The current patch still needs a bit of work.

- use clientbase_t as the basis
- use two new calls to register and update authlog, i.e.
void ci_authlog_init(clientbase_t *self, const char *username, const
char *status);
static void ci_authlog_close(clientbase_t *self);
- call the latter one only from ci_close (hence the static)

this will make it trivial to use this from /all/ deamons, not just imapd
and popd.

also, what's up with the clientsession_t session_cleanup callback?



>
> -Jon
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 14, 2009, 9:44 AM

Post #19 of 24 (3740 views)
Permalink
Re: New Idea [In reply to]

Thanks for the inclusion of the authlog in the main git Paul!
Will this have a parameter to enable/disable in dbmail.conf?

Jorge,


> -----Original Message-----
> From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-
> bounces [at] dbmail] On Behalf Of Paul J Stevens
> Sent: domingo, 14 de Junho de 2009 14:20
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] New Idea
>
> Jonathan Feally wrote:
> > Jorge Bastos wrote:
> >> "166319344" bytes RX, well not possible!!
> >>
> > I assumed that the values would start at 0. I have set them to 0 at
> the
> > clientbase_t creation so give that a shot.
>
> Jon,
>
> Not such a strange assumption, since you're using g_new0. Maybe the
> unsignedness of the counters comes into play here.
>
> The current patch still needs a bit of work.
>
> - use clientbase_t as the basis
> - use two new calls to register and update authlog, i.e.
> void ci_authlog_init(clientbase_t *self, const char *username, const
> char *status);
> static void ci_authlog_close(clientbase_t *self);
> - call the latter one only from ci_close (hence the static)
>
> this will make it trivial to use this from /all/ deamons, not just
> imapd
> and popd.
>
> also, what's up with the clientsession_t session_cleanup callback?
>
>
>
> >
> > -Jon
> >
> >
> > ---------------------------------------------------------------------
> ---
> >
> > _______________________________________________
> > Dbmail-dev mailing list
> > Dbmail-dev [at] dbmail
> > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
>
>
> --
> ________________________________________________________________
> Paul Stevens paul at nfg.nl
> NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
> The Netherlands________________________________http://www.nfg.nl
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


paul at nfg

Jun 14, 2009, 11:34 AM

Post #20 of 24 (3748 views)
Permalink
Re: New Idea [In reply to]

Jorge Bastos wrote:
> Thanks for the inclusion of the authlog in the main git Paul!
> Will this have a parameter to enable/disable in dbmail.conf?

no problem.

--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


vulture at netvulture

Jun 14, 2009, 11:49 AM

Post #21 of 24 (3755 views)
Permalink
Re: New Idea [In reply to]

Geez! I guess if I fall asleep my patch will get eaten by a Paul Monster.

Good work Paul. I was thinking we might add a server hostname field to
this table. Any other items you think we should record?

-Jon

Jorge Bastos wrote:
> Thanks for the inclusion of the authlog in the main git Paul!
> Will this have a parameter to enable/disable in dbmail.conf?
>
> Jorge,
>
>
>
>> -----Original Message-----
>> From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-
>> bounces [at] dbmail] On Behalf Of Paul J Stevens
>> Sent: domingo, 14 de Junho de 2009 14:20
>> To: DBMAIL Developers Mailinglist
>> Subject: Re: [Dbmail-dev] New Idea
>>
>> Jonathan Feally wrote:
>>
>>> Jorge Bastos wrote:
>>>
>>>> "166319344" bytes RX, well not possible!!
>>>>
>>>>
>>> I assumed that the values would start at 0. I have set them to 0 at
>>>
>> the
>>
>>> clientbase_t creation so give that a shot.
>>>
>> Jon,
>>
>> Not such a strange assumption, since you're using g_new0. Maybe the
>> unsignedness of the counters comes into play here.
>>
>> The current patch still needs a bit of work.
>>
>> - use clientbase_t as the basis
>> - use two new calls to register and update authlog, i.e.
>> void ci_authlog_init(clientbase_t *self, const char *username, const
>> char *status);
>> static void ci_authlog_close(clientbase_t *self);
>> - call the latter one only from ci_close (hence the static)
>>
>> this will make it trivial to use this from /all/ deamons, not just
>> imapd
>> and popd.
>>
>> also, what's up with the clientsession_t session_cleanup callback?
>>
>>
>>
>>
>>> -Jon
>>>
>>>
>>> ---------------------------------------------------------------------
>>>
>> ---
>>
>>> _______________________________________________
>>> Dbmail-dev mailing list
>>> Dbmail-dev [at] dbmail
>>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
>>>
>> --
>> ________________________________________________________________
>> Paul Stevens paul at nfg.nl
>> NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
>> The Netherlands________________________________http://www.nfg.nl
>> _______________________________________________
>> Dbmail-dev mailing list
>> Dbmail-dev [at] dbmail
>> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
>>
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
>
>


--
Scanned for viruses and dangerous content by MailScanner

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


paul at nfg

Jun 14, 2009, 12:02 PM

Post #22 of 24 (3739 views)
Permalink
Re: New Idea [In reply to]

Jonathan Feally wrote:
> Geez! I guess if I fall asleep my patch will get eaten by a Paul Monster.
>

Easy sunday.

> Good work Paul. I was thinking we might add a server hostname field to
> this table. Any other items you think we should record?
>


Mmm, dunno. Hostname makes sense though.

--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


paul at nfg

Jun 14, 2009, 12:02 PM

Post #23 of 24 (3745 views)
Permalink
Re: New Idea [In reply to]

Jonathan Feally wrote:
> Geez! I guess if I fall asleep my patch will get eaten by a Paul Monster.
>

Easy sunday.

> Good work Paul. I was thinking we might add a server hostname field to
> this table. Any other items you think we should record?
>


Mmm, dunno. Hostname makes sense though.

--
________________________________________________________________
Paul Stevens paul at nfg.nl
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands________________________________http://www.nfg.nl
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev


mysql.jorge at decimal

Jun 14, 2009, 2:20 PM

Post #24 of 24 (3738 views)
Permalink
Re: New Idea [In reply to]

Paul,
The email below, I received it twice, my problem or you really sent it
twice?



> -----Original Message-----
> From: dbmail-dev-bounces [at] dbmail [mailto:dbmail-dev-
> bounces [at] dbmail] On Behalf Of Paul J Stevens
> Sent: domingo, 14 de Junho de 2009 20:03
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] New Idea
>
> Jonathan Feally wrote:
> > Geez! I guess if I fall asleep my patch will get eaten by a Paul
> Monster.
> >
>
> Easy sunday.
>
> > Good work Paul. I was thinking we might add a server hostname field
> to
> > this table. Any other items you think we should record?
> >
>
>
> Mmm, dunno. Hostname makes sense though.
>
> --
> ________________________________________________________________
> Paul Stevens paul at nfg.nl
> NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
> The Netherlands________________________________http://www.nfg.nl
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev [at] dbmail
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

DBMail dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.