Crystal Wacker Knapp wrote:
I compose emails in SeaMonkey. They are sent through my database,
Sumac, using centurylink server. Both Sumac and Century Link tech
support say that on their respective ends, all is correct and should
be sending and receiving emails accordingly; they say the problem
must be with Sea Monkey.
I have successfully used this system for a year. Until yesterday
emails were delivered. Now, only one-word "Testing" emails go
through.
For the messages that are being rejected, you need two critical pieces
of information -- the exact error message of the rejection, and the ID
of the server doing the rejection.
I've never heard of Sumac, and if it's primarily a database server, it's
odd to use that as a Mail Transport Agent, although I suppose it may
have a small MTA built in, as a way of facilitating outbound mail sent
by stuff originating in a database. However, even if you're the only
user of that mail server, I would strongly discourage you from using
that for any kind of general purpose use -- that is, mail that's not
related to the database, especially stuff you compose in Seamonkey.
It's not clear if your use of Sumac is as a stand-alone SMTP client, or
if it's configured to use CenturyLink as a smart host.
If you're down-line from CenturyLink, then I would encourage you to
reconfigure your outbound mail settings so that they relay through
CenturyLink's server. Although there may be reason for you to use Sumac
as the outbound MTA for your database application, there's no reason for
you to use that for mail that originates outside the database.
I did a quick lookup of Sumac, and the temptation of using its mail
handling capacities bundled with your database package is attractive,
but IMO, it's a mistake. Over a lot of years, I've worked in a similar
database environment and run mail servers, as well, and I can tell you
that expertise in one area doesn't really translate to the other. In
this case, it's likely that Sumac's technical strengths are on the
database side, and where they've figured out email enough to make things
work (more or less), but it wouldn't surprise me if they don't have
anybody who really has an in-depth knowledge of the mechanics of how
email servers work.
In any case, using Sumac's MTA merely complicates troubleshooting of
mail flow issues. It may be possible for you to reconfigure Sumac (and
the supporting server) so that all outbound mail is submitted directly
to CenturyLink's outbound mail server, and where you're not using any of
the mail handling capacities provided by Sumac. If so, I urge you to get
Sumac out of the equation, in the same way you need to have Seamonkey
not trying to send through the Sumac server.
Without error reports from rejected messages, or the identity of
servers, I can't tell where your problems are, but it's a good guess
that the problem is related to your messages getting through the Sumac
server. However, it's common that when these kinds of problems crop up,
it's common for service vendors to claim that their stuff works, and
point fingers at somebody else. And because Seamonkey isn't widely
known, it's easy for both to blame Seamonkey. In reality, it's doubtful
that Seamonkey is the culprit (although not impossible). For the
purposes of external support, you may be better off telling them that
you're running Thunderbird, and not even mentioning Seamonkey -- at the
level of SMTP exchange, they're pretty much identical, and the true
differences at UI level should be entirely irrelevant to a mail service
provider.
Seeing what Sumac is, I'd be curious to find out more about your
organization. Feel free to contact me off-list. My posting address is valid.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
