I see .. but this kind of problems could be moved to the script if you submit the current POP command e.g.:
pop.out.tab: "scriptname" "@@FILE" "@@POPCMD" When @@POPCMD is e.g. LIST, the script injects the file listing to the POP conversation, RETR returns the message content etc. Moving all command handling into the programmer's hands will also allow custom commands for modifed POP clients. There would be no limits if we just have 2 things: The hook and a way to inject data into the POP conversation. If performance is an issue, we could use a global switch to disable POP customization for those who don't need it. Just some ideas - I know .. IMAP has priority ... ;) --Harald > -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Im Auftrag von Davide Libenzi > Gesendet: Dienstag, 12. Juli 2005 15:41 > An: xmail@xmailserver.org > Betreff: [xmail] Re: AW: Re: POP box scripting hooks ? > > > > On Tue, 12 Jul 2005, Harald Schneider wrote: > > > > >> - one before the POP message is retieved by the client??? For > >> what? You > >> have the chance to do your homework when you store it. > > > > If you store it in a compressed format or in a database, > you'll need this > > hook to retreive the orginal message before download. > Otherwise you'll need > > to write your own modified POP server. > > Ohh, but then you have a whole sort of associated problems, like file > system listing, stat information, etc. It is not a matter of hook. > > > - Davide > > - > To unsubscribe from this list: send the line "unsubscribe xmail" in > the body of a message to [EMAIL PROTECTED] > For general help: send the line "help" in the body of a message to > [EMAIL PROTECTED] > - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
