Kent:
> Hi Wietse,
>
> Thanks - as per my last e-mail, I am getting the errors back.
> It's just the warnings I'm not getting back.
If you are concerned about mistakes, sendmail command line is not
the whole story. There is a lot more that can go wrong.
The MAILLOG file has a complete(*) record
Hi Wietse,
Thanks - as per my last e-mail, I am getting the errors back. It's just the
warnings I'm not getting back.
But, I can live with this as the warnings will be my coding errors - so apart
from my test with intentional issues, it hopefully shouldn't happen.
cheers
Kent.
> On 5/06/
Kent:
> Hi Wietse,
>
> Thanks for your guidance so far.
>
> I'm trying to use the postfix sendmail command line - and have
> this working (code is still rough). However, I'm now trying to
> get any output from the command.
In case of error it returns an exit status as defined in
/usr/include/s
Hi Wietse,
Further to below - after more testing I am getting errors, but not warnings. I
don't know where they are going, but I'm not getting them back at all.
eg. If I call:
> /usr/sbin/sendmail.postfix -g
> sendmail.postfix: invalid option -- 'g'
> sendmail.postfix: invalid option -- 'g'
>
Hi Wietse,
Thanks for your guidance so far.
I'm trying to use the postfix sendmail command line - and have this working
(code is still rough). However, I'm now trying to get any output from the
command.
To simulate an error, I've intentionally added an invalid -N option - which in
my manual
Benny Pedersen:
> how do i get forward solving this ?
Specify both the xn--mumble and UTF8 forms in Postfix configuration
files. As documented Postfix does not automatically convert table
lookup requests.
Wietse
> Mail is sent to m...@mynoc.eu and forwarder to m...@streamservice.nl.
> In that case I want the mail from to be m...@mynoc.eu, I don't
> care about the original address in the mail from during the SMTP
> stage. Every other location where the original mail address is
> listed doesn't have to be ch
