Sure! I recall ago I sent a patch that block "oem" string in crond.c if BB sendmail is chosen in config. That patch was NAKed...
Besides, BB sendmail had -i option in the past, it was removed by the last clearance patch (circa March). There was a discussion about which compatibility options should BB sendmail support. Ones told one, others other. It seems there is no free letter (for option) in latin that sendmail shouldn't support :) Will anyone on the list take care of making clear statement on it? For to me, existing BB sendmail works just fine. Best regards, -- Vladimir 2009/10/1, Natanael Copa <[email protected]>: > On Thu, 2009-10-01 at 17:48 +0400, Vladimir Dronnikov wrote: >> > sendmail: invalid option -- i >> >> Try replacing line #96 of sendmail.c: >> opts = getopt32(argv, "tf:o:w:H:S:a::", &opt_from, NULL, &timeout, >> &opt_connect, &opt_connect, &list); >> with >> opts = getopt32(argv, "tf:o:w:H:S:a::i", &opt_from, NULL, &timeout, >> &opt_connect, &opt_connect, &list); >> >> Regards, > > Before I even try that, miscutils/crond.c has this: > > #ifndef SENDMAIL_ARGS > #define SENDMAIL_ARGS "-ti", "oem" > #endif > > will sendmail be able to handle that "oem"? I doubt it. Maybe we should > change that in cron too, to "-oem"? (googling tells me its an exim > thing?) > > We probably need to fix both. > >> -- >> Vladimir > > _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
