Hi Hans-Joachim,

From my experience this is not possible. The reason being that you are unable to query distribution lists and nicknames and thus will reject legitimate e-mail. I stand to be corrected on this, of course, but have personally never gotten my Cisco IronPorts to play nicely with GroupWise in this area.

Sorry :(

Cheers,

Hello Hans-Joachim,
I would expect that this is done by your IronPort like described over here in the Step 2:
https://www.webdigi.co.uk/blog/2009/how-to-check-if-an-email-address-exists-without-sending-an-email/

cu SveN

Maybe something like this: https://supportforums.cisco.com/discussion/12490851/ironport-recipient-validation-without-ldap

Hans-Joachim,

why don't you just use SMTP? The Ironport will contact the GWIA and one of the first steps is to check if the RCPT is valid. If not, the GWIA will reply with an error and the Ironport can do with the mail whatever it is configured to do. Ours is leaving thconnection to the sending SMTP process open while it checks with the GWIA and will issue an error as well.

Uwe

--
Novell Knowledge Partner
Please don't send me support related e-mail unless I ask you to do so.

Hans-Joachim,

why don't you just use SMTP? The Ironport will contact the GWIA and one of the first steps is to check if the RCPT is valid. If not, the GWIA will reply with an error and the Ironport can do with the mail whatever it is configured to do. Ours is leaving thconnection to the sending SMTP process open while it checks with the GWIA and will issue an error as well.

Uwe

--
Novell Knowledge Partner
Please don't send me support related e-mail unless I ask you to do so.

Hans-Joachim,

why don't you just use SMTP? The Ironport will contact the GWIA and one of the first steps is to check if the RCPT is valid. If not, the GWIA will reply with an error and the Ironport can do with the mail whatever it is configured to do. Ours is leaving thconnection to the sending SMTP process open while it checks with the GWIA and will issue an error as well.

Uwe

--
Novell Knowledge Partner
Please don't send me support related e-mail unless I ask you to do so.

buckesfeld;2402534 wrote:
Hans-Joachim,

why don't you just use SMTP? The Ironport will contact the GWIA and one of the first steps is to check if the RCPT is valid. If not, the GWIA will reply with an error and the Ironport can do with the mail whatever it is configured to do. Ours is leaving thconnection to the sending SMTP process open while it checks with the GWIA and will issue an error as well.

Uwe

--
Novell Knowledge Partner
Please don't send me support related e-mail unless I ask you to do so.

Thanks Uwe,

we don't use SMTP, because the GWIA is configured to accept all Recipients @mycompany.de. Switches and APC`s can send Mails to our Admins without an own Mailaddress.


Hans-Joachim

Hans-Joachim wrote on 08/06/2015 10:16 AM:
> we don't use SMTP, because the GWIA is configured to accept all
> Recipients @mycompany.de. Switches and APC`s can send Mails to our
> Admins without an own Mailaddress.

That's the default. Your GWIA will always accept any mail to its own internet domain, regardless the sender. Senders don't need a valid mail address anyway.
I don't see how this should stop you from letting the ironport do the same.

It should work. Ironport is exposed to the internet, MX record for your domain probably pointing to the Ironport. Receives a mail from let's say, me. My mail server opens the SMTP connection with the Ironport, and when my server sends the RCPT TO, Ironport will open a connection to the GWIA and forward the commands to the GWIA. If the GWIA replies to the RCPT TO with an OK, the Ironport sends it to my mail server and the communication continues. After the Ironport is finished doing its job, it will continue (or start again) the communication with the GWIA.

Uwe

--
Novell Knowledge Partner
Please don't send me support related e-mail unless I ask you to do so.