Groupwise 7.02 "550 relaying denied"

Groupwise 7.02 Server (one domain and post office)
We use an student information system that allows for us to send parent reports, etc. to the email address listed in the contact infomation.  When we try to send a message, we get the following error message:
An error occurred while sending emails.  Server returned '550 relaying denied'
I understand that the Groupwise server is set to not allow relaying.  However, is there a way to adjust it to allow this specific use.  If so, where are the settings located.  Thanks.
Who is Participating?
ShineOnConnect With a Mentor Commented:
I take it the Student Information System is a web-based tool of some sort?

What is it using to do the emailing - is it using its own SMTP engine, and passing the email directly to GWIA, expecting it to relay the mail?

What is the sender field on the mails sent by the student information system?  If you use a legitimate GroupWise user ID, you could use a sendmail/postfix alias to send the mail via the GroupWise post office, so there would not be an SMTP mail relay involved, and there'd be no chance an RBL site would pick up on the relay and blacklist your GWIA.

Aternatively, (and to answer your question) you can set SMTP relay in ConsoleOne in the GWIA object Properties.  Select the Access Control tab.  You should be able to add it as an exception, with a "from" entry of the hostname or IP address of the student information system.  I don't know if you can do *@*.* in the "to" or if you have to add a bunch of exceptions for all of the "to" TLD's, or even if wildcards are accepted in a "to" address in a relay exception.
krusebrAuthor Commented:
Yes it is a web-based SIS.
Under the ADMINISTRATION OPTIONS there is a place to add the follow email information....
Sending Email:
SMTP server:
SMTP server requires authentication
      Acct. ID:
I added our SMTP server and also added the authentication info.1
I added the exception to the the RELAY section in GWIA.  
It seems to be working now but 1 out of 3 attempts wiill fail because of the following error:
server returned '501 authentication failed'
Also, I unsure if we will now be blacklisted as a relay.  Listed below is the "sender field" on one of the emails sent.  Are we OK?  Thanks.
Received: (qmail 29497 invoked from network); 1 Aug 2007 01:37:23 -0000
Received: from unknown (HELO ([])
          (envelope-sender <my school email acct >)
          by (qmail-ldap-1.03) with SMTP
          for <parent email address>; 1 Aug 2007 01:37:23 -0000
Received: (qmail 16902 invoked from network); 1 Aug 2007 01:37:23 -0000
Received: from unknown (HELO 'our email server') (['ip adress of our email server'])
          (envelope-sender <'my school email acct'>)
          by (qmail-ldap-1.03) with SMTP
          for <'parent email address'>; 1 Aug 2007 01:37:22 -0000
Received: from our email server ([] ('this is the inside IP of the computer using SIS')
 by 'our email server' with ESMTP; Tue, 31 Jul 2007 20:36:32 -0500
From: "my school acct" <my school acct>
To: "parent name" <parent email address>
Subject: test
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Nonspam: Whitelist

krusebrAuthor Commented:
When message fails to send and the school information system shows a "server returned '501 authentication failed'....
the GWIA log shows the following:
successful login with client/server access (lists my ip address of the workstation using the SIS software to send)
Inbound AUTH Failure (D019)

I know there's a way to add a tag to relayed mail, but it's still relayed mail.

I'm sure there are Experts out there that have done this kind of mail relay through GroupWise.  I'd have to do a bunch of digging to get you any clear answers, and it's past my bedtime ;) so I won't be able to think about thinking about it until tomorrow.

Hopefully we'll see more than just me posting...
steveoskhConnect With a Mentor Commented:
Blacklisted?  You should not be, since you have relay turned off and only your internal site has relay open.  You can always run relay tests and check to make sure you are not listed.
Shot in the dark on the auth failure, try fully qualifying the user name.  "user.postOffice.Domain"  or something to that effect.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.