MAIL-E-OPENOUT insufficient privilege or file protection violation

[The Brit]

Maurizio,
I think if you set the ownership on the files to the correct owner then it might work.

$ set file /owner=TCPIP$SMTP SYS$SPECIFIC:[000000]TCPIP$SMTP.DIR
$ set file /owner=TCPIP$SMTP SYS$SPECIFIC:[TCPIP$SMTP...]*.*.*

Should do it.

Dave.

[Maurizio Rondina]

Dave,

after the set file /own command i gave last thursday, i solved the error message on the subject of this discussion.

But there are still problems due to network LAN infrastructure.

If users send out to an external mail domain eg. "mauriziorondina.it" all go well, if they send to the customer domain "custom.it" on the TCPIP$SMTP_LOGFILE.COM appear the following errors:
554 %TCPIP-E-SMTP_XFAIL, remote transaction failure, custom.it
550 %TCPIP-E-SMTP_NOSUCHUSER, no such user, SMTP%"postmaster@custom.it"

So i changed the "MAIL FROM" and "from:" parameters on the smtp message, and now mails seem go well, both in internal and external mail domain.

Strange that there are differences between "custom.it" and other domains, but this workaround seems good.

[Maurizio Rondina]

sometimes sending to the mailboxes at the customer domain "custom.it" the mails still aren't received.

In these cases on the TCPIP$SMTP_LOGFILE.COM appear the following error:
554 %TCPIP-E-SMTP_XFAIL, remote transaction failure, custom.it

Other times mails to "custom.it" domain, goes well.

[Maurizio Rondina]

I traced the smtp operations with

define/system tcpip$smtp_symb_trace 1
TCPIP STOP MAIL
WAIT 00:01:00
TCPIP START MAIL

sended a new mail

TCPIP STOP MAIL
WAIT 00:01:00
TCPIP START MAIL

In the cases when mails go wrong on TCPIP$SMTP_COMMON:TCPIP$SMTP_LOGFILE.LOG;-1

the last lines of the message are

recv buf=554 Transaction Failed Spam Message not queued.\d\a
send buf=QUIT\d\a
recv buf=221 Service closing transmission channel closing connection\d\a
554 %TCPIP-E-SMTP_XFAIL, remote transaction failure, custom.it

Now i ask to the administrator of mx.custom.it to leave free, the public ip of my alphaserver from his antispam filter

[Hoff]

Sounds like your DNS is messed up.

[Maurizio Rondina]

Hoff,

wasn't a DNS problem, only a mail server anti-spam problem for mail domain "custom.it".
Now is all ok.

Thanks.

[Hoff]

One of the usual triggers for detecting spam is bogus DNS; that the sending host lacks a valid and matching reverse DNS, for instance.

[Maurizio Rondina]

Ok, but i haven't changed nothing on OpenVms's DNS and all go well. The problem was on external mail server that manage "custom.it" domain. That administrators made the change of their antispam configuration, and now is all good.

[Maurizio Rondina]

See my last replies, on the discussion.