Originally Posted by
veronica 
Zimbra MTA component is used to send and recieve mail.
This I understand
Originally Posted by
veronica Since you have zimbra MTA installed as seperate component why not use them for sending?
The issue comes down to user experience and client configuration. If I configure the ZImbra Desktop app with a 'Zimbra' account, there is no place I can see to set an outgoing mail server, as it tries to use the MailStore/LDAP server. If I configure the account as an IMAP account, I can set the outgoing server as one of the MTAs, and it works fine. The same issue arises with the Web Client; I cannot send mail through the web client. Here is the message I get:
Code:
method: SendMsgRequest
msg: system failure: MessagingException
code: service.FAILURE
detail: soap:Receiver
trace: btpool0-0:1244484217245:f2bed5455876bbe8
request:
Body: {
SendMsgRequest: {
_jsns: "urn:zimbraMail",
m: {
e: [
0: {
a: "traim@yahoo.ca",
add: 1,
t: "t"
},
1: {
a: "tim@rbase.ca",
p: "Tim Molloy",
t: "f"
},
2: {
a: "tim@rbase.ca",
p: "Tim Molloy",
t: "r"
}
],
idnt: "12c08b65-69f2-436c-a760-dd9a993f40ad",
mp: [
0: {
content: {
_content: "test
--
Tim Molloy
Proprieter, rBase Communications
tim@rbase.ca
"
},
ct: "text/plain"
}
],
su: {
_content: "test"
}
},
suid: 1244484248075
}
},
Header: {
context: {
_jsns: "urn:zimbra",
account: {
_content: "tim@rbase.ca",
by: "name"
},
authToken: "(removed)",
format: {
type: "js"
},
sessionId: {
_content: 1156,
id: 1156
},
userAgent: {
name: "ZimbraWebClient - FF3.0 (Win)",
version: "5.0.16_GA_2921.RHEL5"
}
}
} Another issue I can think of that might come up is if the MTA configured in the client fails, then they will lose the ability to send email without either changing their MTA to the secondary manually or waiting until the primary MTA is back online.
LinkBack URL
About LinkBacks
[SOLVED] Question about configuration
