Highlighted
Honored Contributor.
Honored Contributor.
1471 views

What does an MTA do with messages it cannot process?

Scenario:
My primary domain holds the single post office
A secondary domain hosts the GWIA and a third domain hosts web access.

Yesterday, I added yet another domain to host a second web access agent and site.
In the process of setting it up, I screwed up the link configurations.

In the link configuration between the primary MTA and the MTA for the GWIA, I put in the IP address of the new webaccess domain's MTA.

After the creation of the new domain and web access, I had noted a huge number of messages like this in the logs:
17:43:24 776 MTP: <domain name>: Returning acknowledge (11)

This was before I was aware of the problem I had created for myself.

When I look at the web console for the new domain, the status page lists 35,000 messages routed and 1878 undeliverable.
I find no messages in any of the domain folders.
I don't think this is version-specific, but I'm not positive about that.

So if this webaccess's MTA starts receiving messages meant for a GWIA that it does not host, what does it do?
Does it reject them or hold them somewhere?

Would the MTA for the primary domain/post office be aware of the problem, or does it only care that the messages have been transferred to the other MTA?
Labels (2)
0 Likes
6 Replies
Highlighted
Visitor.

Re: What does an MTA do with messages it cannot process?

Logs may tell you... /var/log/novell/groupwise/...

Is it possible the messages were delivered to the POA... eventually?

In other words, make sure you are not proving a negative...

-- Bob
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: What does an MTA do with messages it cannot process?

Hi.


Am 20.11.2014 01:16, schrieb gathagan:
>
> Yesterday, I added yet another domain to host a second web access agent
> and site.


Looking at the group we're in, are we really talking about GW2012? Cause
in GW2012, webaccess isn't hosted by domains, and has no agent. It talks
to the POAs only directly via SOAP, and needs no domain at all.

Just FTR...

> In the process of setting it up, I screwed up the link configurations.
>
> In the link configuration between the primary MTA and the MTA for the
> GWIA, I put in the IP address of the new webaccess domain's MTA.
>
> After the creation of the new domain and web access, I had noted a huge
> number of messages like this in the logs:
> -17:43:24 776 MTP: <domain name>: Returning acknowledge (11)-
>
> This was before I was aware of the problem I had created for myself.
>
> When I look at the web console for the new domain, the status page lists
> 35,000 messages routed and 1878 undeliverable.
> I find no messages in any of the domain folders.
> I don't think this is version-specific, but I'm not positive about
> that.


Ok, but have you seen any problems, like messages not arriving at their
destination?


There are two options: Either the MTA outright rejects the wrong
connection, or it accepts it and routes the messages where they belong
(if possible, which in your case it sounds as if it could).

If you don't see queued messages in the web interface > links of any of
the domains, then the latter is it.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: What does an MTA do with messages it cannot process?

Oops, sorry!
You are correct; wrong forum.

As to what happened to the messages:
It appears that messages going out to other systems via SMTP were delivered, but the item in users' "Sent Items" folder still shows as pending.
For email coming in from other systems, the webaccess MTA would attempt to deliver them to the primary domain, but they don't appear anywhere in logs past the web access domain.
Nothing in the primary MTA logs or the POA logs.

This is an example of what I see in the logs during that period.
I freely admit that I'm not sure I'm keying on the correct identifier for the message.
In this example, I believe it's 546C24FC.103:56:53507
If I'm correct, the message comes into the GWIA, routes from the GWIA's MTA to the webaccess MTA, which attempts to deliver it to the primary domain
After 9 attempts, it stops and, apparently, deletes the file.

GWIA
19:04:43 244 DMN: MSG 5863690 Accepted connection: [10.0.1.9] (spam firewall)
19:04:43 244 DMN: MSG 5863690 SMTP upgraded to a secure connection.
19:04:43 244 DMN: MSG 5863690 Receiving file: GATEWAY/SYS:\IDOMAIN\WPGATE\GWIA\receive\b489b645.841
19:04:43 244 DMN: MSG 5863690 SMTP session ended: [10.0.1.9] (spam firewall)
19:05:00 240 MSG 5863690 Processing inbound message: GATEWAY/SYS:\IDOMAIN\WPGATE\GWIA\receive\B489B645.841
19:05:00 240 MSG 5863690 Sender: editorial@open-foodscience.com
19:05:00 240 MSG 5863690 Recipient: <user address>
19:05:00 240 MSG 5863690 Queuing to MTA
19:05:00 240 MSG 5863690 File: GATEWAY/SYS:\IDOMAIN\WPGATE\GWIA\wpcsin\4\446b985c.v91 Message Id: (546C24FC.103:56:53507) Size: 18.9 Kb


GWIA MTA
19:05:09 ARR MSG,editorial,546C24FC.103:56:53507,x0000905D,open-foodscience.com,,,GWIA,19372,4,OFS,0,0,domain1.postoffice1{1}
19:05:10 QUE x0000905D,HOP,domain1,1
19:15:08 TRN domain1,x0000905D,19372,60


Webaccess MTA
19:15:08 168 RTR: web7dom: 0000240b.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/0000240b.V94 (19 kb)
19:15:08 168 RTR: web7dom: 0000240b.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:08 168 RTR: web7dom: 0000240b.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/0000240b.001

19:15:11 168 RTR: web7dom: 0000240d.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/0000240d.V94 (19 kb)
19:15:11 168 RTR: web7dom: 0000240d.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:11 168 RTR: web7dom: 0000240d.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/0000240d.001

19:15:19 168 RTR: web7dom: 00002411.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/00002411.V94 (19 kb)
19:15:19 168 RTR: web7dom: 00002411.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:19 168 RTR: web7dom: 00002411.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/00002411.001

19:15:27 168 RTR: web7dom: 00002415.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/00002415.V94 (19 kb)
19:15:27 168 RTR: web7dom: 00002415.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:27 168 RTR: web7dom: 00002415.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/00002415.001

19:15:36 168 RTR: web7dom: 00002419.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/00002419.V94 (19 kb)
19:15:36 168 RTR: web7dom: 00002419.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:36 168 RTR: web7dom: 00002419.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/00002419.001

19:15:40 168 RTR: web7dom: 0000241c.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/0000241c.V94 (19 kb)
19:15:40 168 RTR: web7dom: 0000241c.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:40 168 RTR: web7dom: 0000241c.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/0000241c.001

19:15:44 168 RTR: web7dom: 0000241f.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/0000241f.V94 (19 kb)
19:15:44 168 RTR: web7dom: 0000241f.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:44 168 RTR: web7dom: 0000241f.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/0000241f.001
19:15:45 544 MTP: gw7mail.cc.hawaii.edu: Transmitting file /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/0000241f.001, Size: 19444

19:15:45 168 RTR: web7dom: 00002421.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/00002421.V94 (19 kb)
19:15:45 168 RTR: web7dom: 00002421.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:45 168 RTR: web7dom: 00002421.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/00002421.001

19:15:47 168 RTR: web7dom: 00002423.V94: Routing /opt/novell/groupwise/web7dom/mslocal/gwinprog/4/00002423.V94 (19 kb)
19:15:47 168 RTR: web7dom: 00002423.V94 Priority 4 546C24FC.103:56:53507 : Transfer to domain1
19:15:47 168 RTR: web7dom: 00002423.V94: Message queued: /opt/novell/groupwise/web7dom/mslocal/mshold/dom59e7/4/00002423.001



Since I had a good idea of the time frame, I ended up going into my anti-spam system and re-delivering all of the items that passed muster during that time frame.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: What does an MTA do with messages it cannot process?

Hi.

Am 20.11.2014 19:36, schrieb gathagan:
>
> Oops, sorry!
> You are correct; wrong forum.


So, dare I ask, what GW version is it? 😉

> As to what happened to the messages:
> It appears that messages going out to other systems via SMTP were
> delivered, but the item in users' "Sent Items" folder still shows as
> pending.
> For email coming in from other systems, the webaccess MTA would attempt
> to deliver them to the primary domain, but they don't appear anywhere in
> logs past the web access domain.
> Nothing in the primary MTA logs or the POA logs.
>
> This is an example of what I see in the logs during that period.
> I freely admit that I'm not sure I'm keying on the correct identifier
> for the message.
> In this example, I believe it's *546C24FC.103:56:53507*
> If I'm correct, the message comes into the GWIA, routes from the GWIA's
> MTA to the webaccess MTA, which attempts to deliver it to the primary
> domain
> After 9 attempts, it stops and, apparently, deletes the file.



Of course that *shouldn't* happen. Loks like this might be a bug.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Honored Contributor.
Honored Contributor.

Re: What does an MTA do with messages it cannot process?

It's version 8.
Starting this evening, I'm moving everything that's still on NetWare to Linux and then upgrading to 2012.
As such, I've spent the last several weeks getting used to how everything works on Linux.
As well as things work in general on Linux, there are still oddities that pop up every once in a while.
This one, however, was all on my head.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: What does an MTA do with messages it cannot process?

Am 22.11.2014 03:06, schrieb gathagan:
>
> It's version 8.
> Starting this evening, I'm moving everything that's still on NetWare to
> Linux and then upgrading to 2012.
> As such, I've spent the last several weeks getting used to how
> everything works on Linux.
> As well as things work in general on Linux, there are still oddities
> that pop up every once in a while.
> This one, however, was all on my head.


And, of course, I seruously doubt it makes a difference if it's on linux
or netware. I suspect it would behave exactly the same.

CU,
--
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.