[EMAIL PROTECTED]:
>
> > - Understand that Postfix refuses [EMAIL PROTECTED]:port as an email
> > destination.
> >
> > Wietse
> >
>
> Ok Wietse, thanks for the info... Do you know if there's any GPL mail
> server accepting [EMAIL PROTECTED]:port as an email destination?
That would be a sec
> - Understand that Postfix refuses [EMAIL PROTECTED]:port as an email
> destination.
>
> Wietse
>
Ok Wietse, thanks for the info... Do you know if there's any GPL mail
server accepting [EMAIL PROTECTED]:port as an email destination?
Thanks
Antonio
[EMAIL PROTECTED]:
> > [EMAIL PROTECTED]:
> >> voidrecipient_list_add(RECIPIENT_LIST *list, long offset,
> >> const char *dsn_orcpt, int dsn_notify,
> >> const char *orig_rcpt, const char *rcpt)
> >
> > You can't change the rcpt argume
> [EMAIL PROTECTED]:
>> voidrecipient_list_add(RECIPIENT_LIST *list, long offset,
>> const char *dsn_orcpt, int dsn_notify,
>> const char *orig_rcpt, const char *rcpt)
>
> You can't change the rcpt argument.
>
>> {
>> int n
>> [EMAIL PROTECTED]:
>>> > [EMAIL PROTECTED]:
>>> >> , postfix reload; and postfix stills working as always.
>>> >
>>> > Show actual evidence of behavior that does not change, and show
>>> > actual evidence based on which it should have changed.
>>> >
>>> > Wietse
>>> >
>>>
>>> It's easy. On my
[EMAIL PROTECTED]:
> voidrecipient_list_add(RECIPIENT_LIST *list, long offset,
> const char *dsn_orcpt, int dsn_notify,
> const char *orig_rcpt, const char *rcpt)
You can't change the rcpt argument.
> {
> int new_avail;
[EMAIL PROTECTED]:
> > [EMAIL PROTECTED]:
> >> > [EMAIL PROTECTED]:
> >> >> , postfix reload; and postfix stills working as always.
> >> >
> >> > Show actual evidence of behavior that does not change, and show
> >> > actual evidence based on which it should have changed.
> >> >
> >> > Wietse
> >>
> [EMAIL PROTECTED]:
>> > [EMAIL PROTECTED]:
>> >> , postfix reload; and postfix stills working as always.
>> >
>> > Show actual evidence of behavior that does not change, and show
>> > actual evidence based on which it should have changed.
>> >
>> >Wietse
>> >
>>
>> It's easy. On my modified l
[EMAIL PROTECTED]:
> > [EMAIL PROTECTED]:
> >> , postfix reload; and postfix stills working as always.
> >
> > Show actual evidence of behavior that does not change, and show
> > actual evidence based on which it should have changed.
> >
> > Wietse
> >
>
> It's easy. On my modified library, I
> [EMAIL PROTECTED]:
>> , postfix reload; and postfix stills working as always.
>
> Show actual evidence of behavior that does not change, and show
> actual evidence based on which it should have changed.
>
> Wietse
>
It's easy. On my modified library, I modify recipient_list_add(...)
functi
[EMAIL PROTECTED]:
> , postfix reload; and postfix stills working as always.
Show actual evidence of behavior that does not change, and show
actual evidence based on which it should have changed.
Wietse
> [EMAIL PROTECTED]:
>> Thank you. I try that some days ago but it didn't work.
>
> It works only if you understand its limitations.
>
> The import_environment feature executes AFTER the run-time linker
> completes execution. Therefore, import_environment cannot affect
> the run-time linker perform
[EMAIL PROTECTED]:
> Thank you. I try that some days ago but it didn't work.
It works only if you understand its limitations.
The import_environment feature executes AFTER the run-time linker
completes execution. Therefore, import_environment cannot affect
the run-time linker performance for the
Thank you. I try that some days ago but it didn't work.
I'll retry it!
Antonio G. Artime
http://www.postfix.org/postconf.5.html#import_environment
http://www.postfix.org/postconf.5.html#export_environment
Wietse
Hello everybody:
I'm trying to modify some functions on postfix source and then preload
them by using LD_PRELOAD. To get it work, I've modified
/etc/postfix/postfix-script as follows:
[...]
overlay)
export LD_LIBRARY_PATH=./:/usr/local/lib/:$LD_LIBRARY_PATH
export LD_PRELOAD=/home/antoni
16 matches
Mail list logo
