Ok... so maybe this is more of a C'ish question, but here's where I'm at:
I've added my define to libs/comctlfile.h:
#define COMCTLFILE_SENDERUID 'u'
In submit.C, I've added global CStrings which let me store those arguments as seen in
main, and access them later for log writing, etc. (not saying this is the best way,
but I'm not a C guru - educational tips welcome)
//MSC Global ARGV pointer
CString myArgv2("");
CString myArgv3("");
Here I initialize them:
+//MSC
+//Copy to global space
+if (argc > 2) {
+myArgv2 = argv[2];
+}
+if (argc > 3) {
+myArgv3 = argv[3];
+} else {
+myArgv3 = "EXTERNAL";
+}
And I've got other code that spits them out in mail headers, and so on... So they are
there, and working.
I figured out the "extern" reference I needed in submit2.C to access the CStrings from
submit.C...
NOW. What I've got is logging to the control files most of what I need eg:
For an authenticated relay client:
uAUTH: LOGIN [EMAIL PROTECTED]
For a remote non-authenticated sender (to a local domain):
uEXTERNAL
For a unix user id:
uuid 12394
Does anyone consider this to be of value BESIDES ME?
It's a relatively minor patch, but I'd like to avoid conflicting with future
extensions to the control file with my lower-case "u" record type.
Best way of course would be to get it incorporated to the system right?
What this does for me is allow processing of counts, send quotas, etc. - Ideally with
Vladmirs desires, I wouldn't be worried about people using someone elses IP to avoid
their bandwidth charges, but at least this way I can account for OUTGOING mail - which
is where most of the expense comes from.
Could send the complete patch if someone see's value.
Thanks.
m/
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Sam
Varshavchik
Sent: Saturday, March 15, 2003 12:32 PM
To: [EMAIL PROTECTED]
Subject: [courier-users] Re: Additional Q information needed - If I
build it, is it worthy of inclusion?
Mitch \(WebCob\) writes:
> NOW FOR THE QUESTIONS:
> 1) If I add a new record type do I have to add parsing code for it somewhere
> else? I just want it to be ignored except by my filters and admin programs -
> is that ok or will it break something else?
Nothing special needs to be done.
> 2) Is this information currently passed from submit to submit2? If not, can
> you give me some idea of how to do so without breaking things? (I'm sorry,
> but I humbly admit my C is not my strongest skill) If it is, does it come in
> the same fashion (as arvg variables?).
There's only one submit.
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
