External Accounts in Client 24.3 Not Working Reliably

This is a difficult issue to describe. We run GW CE 24.3.0. We have a GW domain that can send and receive email fine. GW Client users also have set up what I call external accounts using the top menu options [Accounts] and [Account Options]. Users can then set up access to Outlook and Comcast accounts (and others) by entering the POP, IMAP, and SMTP credentials. This works fine for incoming mail. However, occasionally, there is a glitch with outgoing mail.

Normally, if you select to use an external account in the [From] option on the client to send an outgoing message and you click the [send/retrieve] button, the outgoing message is sent through the external account servers. This must be as intended. When this works, it works great.

Sometimes, however, the GW Domain, notwithstanding the selection of an external account in the [From] field, takes hold of the mail message and tries to send it. This results in an error:

"Item to user(s) at gwdom was undeliverable, subject:___"

All users access the GW system in Online mode, not Cache mode.

Is there a way to fix this? As mentioned, it seems to happen 10% of the time, which significantly impacts our system's functionality. 90% of mail to an external domain works fine.

  • Verified Answer

    +1  

    Is there any commonality of the target(To:) domains, and/or if in address book?

    I could see that if the destination domain/address is in an address book for use by GroupWise that it would do what you are seeing.   Look for reproducibility for a given message From-To pairing, as that would point strongly at a root cause.

    I am assuming that all the external accounts are set for sending on other than port 25, something along the lines of 587 or such.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to   

    Bingo. Thanks much.  All users were set to authenticate to 587 port on their external accounts for the particular provider. Checked with the provider and it decided a few weeks ago to switch to port 465. [Didn't tell anyone though.] Provider noted online on a blog that port 587 would continue to work, but intermittently might not. Exactly what was happening.   Very frustrating. Anyway, set the users to all authenticate on port 465. Problem appears to be solved.

  • 0   in reply to 

    Why would they effectively communicate such things,  especially when they can see who is using such ports?

    In today's fire hose of information, tracking that stuff is such a pain. Key providers that have good blogs get monitored with an RSS reader, to have a better chance at catching such things.

    Glad to have pointed the way.

    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.