Karl67 said:

But how do I configure SMG to deliver oubound e-mail to the gateway

Have you told SMG to use a Relay Server?

In SMG Administration, drill down:
Module Management
-Mail Relay Module Manager

On the right side: if there is no SMPT interface add one or drill down:
SMTP Interface
- External Delivery

Enable: Use relay server
Specify: Relay Hosts

Karl67 said:

and inbound e-mail to the GWIA?

In SMG Administration, drill down:
Module Management
-Interfaces
- - SMTP Interface Manager

On the right side, if there is no SMTP Relay Target List, add one. This is where you specify where SMG delivers inbound email

That was a real drill ... .

I now have 2 smtp-interfaces (inbound and outbound) and 2 relay-modules (inbound and outbound). Does this make sense?

Outbound e-mails now can be sent from GroupWise, but inbound E-Mails do not reach the GWIA.

The SMG-SMTP-log shows for the inbound e-mail:

[140217960843008] 2024-06-17 19:52:00 (SMTP) Processing SMTP client connection from 172.16.x.y (client count 1)
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Client connected from known address (internal/trusted)
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Processing started for interface log reference 11012.5
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Processing connection from 172.16.x.y
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Skipping connection drop tests for 172.16.x.y
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [g->c] 220 abc.de SecureMessagingGateway
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [c->g] EHLO srv.abc.de
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [g->c] 250 abc.de
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [c->g] MAIL FROM:<karlxyz@some.com>
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [g->c] 250 Sender accepted
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [c->g] RCPT TO:<test@domain2.>
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Validating RCPT address against target hosts
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Requesting host connection
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Creating new host server connection
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [g->c] 250 Ok
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [c->g] DATA
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [g->c] 354 Ready to receive data
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Spooling inbound DATA to: /opt/opentext/smg/smg-smtp/private/1_11012/temp/~3vgs4ruho0.91j70tu021t898168p7q9.tmp
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Decoding inbound DATA to: /opt/opentext/smg/smg-smtp/private/1_11012/temp/~3vgs4ruho0.a1j70tu021t8aungcfo5.tmp
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Data received (5504 bytes)
[140217960843008] 2024-06-17 19:52:00 (CORE) Attempting to connect to GWAVA scan engine 'Message filter engine' at 172.16.y.z:4929
[140217960843008] 2024-06-17 19:52:00 (CORE) Connection established to GWAVA scan engine 'Message filter engine' at 172.16.y.z:4929
[140217960843008] 2024-06-17 19:52:00 (CONN)<5> Detected local connection to GWAVA scan engine
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Using local connection for scan
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Message direction computed as inbound
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Requesting message scan from smg-scanner service
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Message scan completed, inspecting results
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Message allowed
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> Successfully forwarded data to MTA that does not support DSN
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> DSN message not sent.
[140217960843008] 2024-06-17 19:52:00 (SMTP)<5> [g->c] 250 Data received
[140217960843008] 2024-06-17 19:52:01 (SMTP)<5> [c->g] QUIT
[140217960843008] 2024-06-17 19:52:01 (SMTP)<5> [g->c] 221 Service closing transmission channel
[140217960843008] 2024-06-17 19:52:01 (SMTP)<5> Processing complete for connection from 172.16.x.y
[140217960843008] 2024-06-17 19:52:01 (SMTP)<5> Processing completed for interface log reference 11012.5
[140217960843008] 2024-06-17 19:52:01 (SMTP)<5> SMTP client connection finished processing (client count 0)

The IP 172.16.x.y is the gateway to the ISP, 172.16.y.z is the SMG itself, what I miss here is the connection to ths GWIA with its IP or hostname.

Do you have a clue?

Regards

Karl

Karl67 said:

Do you have a clue?

Look at the message tracker. You are tracking inbound messages, aren't you?

You should see a Scan Result showing none. That means the the message was forwarded on somewhere. Check your GWIA logs for incoming messages and see what happened to the message. You may want to set your GWIA log level to Diagnostic if you need more information.

I activated the message tracker and while the outbound e-mails run through fine the inbound e-mails still get stuck im SMG.

I am quite sure I got your explanation wrong on how to configure the inbound direction in SMPT Interface. Can you be more explicit on this?

Do I really need a second SMTP Interface?

Regards

Karl

Karl, I think you need something like this.

You have to create a record for your domain. Which SMTP host will get these messages (probably GWIA).

I prefer to use security and an authenticated user to login to my gwia. If you have filled out all these fields then you can run a test (=empty yellow field on the right)

Diethmar Rimser said:

You have to create a record for your domain. Which SMTP host will get these messages (probably GWIA).

Thank you Diethmar. I don't know what I was thinking when I replied to Karl.

@Karl67, I apologize for misleading you with my response. Diethmar is, of course, correct.

That did the trick, this type-setting was set to "discard".

Thanks for giving the kick into to right direction.

Karl

Never mind. Fiddling around with this relay-setting gave some insight and solved the question how to get e-mails OUT to the gateway, which failed also before.

So feel hugged, too.

Regards

Karl