Exchange 2010 with Forefront, can't receive large attachments from outside ONLY.

I am able to send and receive large files internally now. Also I am able to send large files to the outside. But I can't receive anything larger then defaulted 10mb. My Environment is 2 Edge boxes, 2 cas HT boxes, 2 mx DB boxes.
I was asked to increase the size of the emails my organization can receive, I went ahead and adjusted the following:
EDGE
1. Receive and Send connectors, set to 40mb.
2. Forefront -->Advanced Options--> Threshold Levels--> all max sized are at 50mb.
CASHT
1. Organization Configuration--> Hub Transport -->Send Connectors and GLOBAL SETTINGS
2. Server Configuration--> HUB Transport--> all the connectors
3. Recipient Configuration--> Mailbox --> users.
All sizes are set to 40mg!
I am able to send large files (24354K), but not able to receive
The following is output from Get-TransportConfig:
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage   :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 40 MB (41,943,040 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage   :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 40 MB (41,943,040 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo :
LegacyJournalingMigrationEnabled : False
MaxDumpsterSizePerDatabase   : 60 MB (62,914,560 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : unlimited
MaxRecipientEnvelopeLimit : unlimited
MaxSendSize : unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
Rfc2231EncodingEnabled : False
ShadowHeartbeatRetryCount : 12
ShadowHeartbeatTimeoutInterval : 00:15:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowRedundancyEnabled : True
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList   : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled   : True
HeaderPromotionModeSetting   : NoCreate
Xexch50Enabled : True
Also my antispam cloud service sent me the following logs:
10:10:38.662 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: MAIL FROM:<[email protected]> SIZE=34140018
10:10:38.771 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 250 2.1.0 Sender OK
10:10:38.771 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY
10:10:38.896 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 250 2.1.5 Recipient OK
10:10:38.896 4 SMTP-037868(workemail.com.smtpip.com:25)
cmd: DATA
10:10:39.021 4 SMTP-037868(workemail.com.smtpip.com:25)
rsp: 354 Start mail input; end with <CRLF>.<CRLF>
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
abort request
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
write failed. Error Code=socket aborted
10:13:57.661 3 SMTP-037868(workemail.com.smtpip.com:25)
[1959469085] failed to send. Error Code=socket aborted
AND
Also another error from Appriver:
08:48:34.798 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: MAIL FROM:<[email protected]> SIZE=34148430
08:48:34.907 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 250 2.1.0 Sender OK
08:48:34.907 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY
08:48:35.032 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 250 2.1.5 Recipient OK
08:48:35.032 4 SMTP-929371(workemail.com.smtpip.com:25)
cmd: DATA
08:48:35.157 4 SMTP-929371(workemail.com.smtpip.com:25)
rsp: 354 Start mail input; end with <CRLF>.<CRLF>
08:53:34.718 3 SMTP-929371(workemail.com.smtpip.com:25)
write failed. Error Code=connection reset by peer
08:53:34.718 3 SMTP-929371(workemail.com.smtpip.com:25)
[1959495450] failed to send. Error Code=connection reset by peer
I am out of options here, wondering if anyone know's anything about this?
Vladimir

Cara,
Yes I have looked at smtp receive protocol logs, below is a log from one failed transmission, I don't see anything that jumps out at me:
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,MAIL FROM:<[email protected]> SIZE=24042643,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,08D0340D4EB7692B;2013-06-10T18:41:06.863Z;1,receiving message
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:06
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.0 Sender OK,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.097Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
+,,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:07
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
+,,
2013-06-10T18:41:07.191Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:07
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.207Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,"RCPT TO:<[email protected]> NOTIFY=FAILURE,DELAY",
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 2.1.5 Recipient OK,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
<,EHLO server45.appriver.com,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-SIZE 42949632,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-PIPELINING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-DSN,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
>,250-STARTTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-AUTH,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-X-EXPS NTLM,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-8BITMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-BINARYMIME,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-CHUNKING,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250-XEXCH50,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,250 XSHADOW,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,DATA,
2013-06-10T18:41:07.332Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,354 Start mail input; end with <CRLF>.<CRLF>,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,<,QUIT,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,>,221 2.0.0 Service closing transmission channel,
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,-,,Local
2013-06-10T18:41:07.441Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,,Ignored X-OriginatorOrg header value 'outside.com' because session capabilities do no
2013-06-10T18:41:07.457Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
,*,,Ignored X-OriginatorOrg header value 'outside.com' because session capabilities do no
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,+,,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeader
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,"220 YPIEDGE1.edge.local Microsoft ESMTP MAIL Service ready at Mon, 10 Jun 2013 14:41:
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,<,EHLO YPICASHT1.YPI.com,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-YPIEDGE1.edge.local Hello [IP ADDRESS],
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-SIZE 42949632,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-PIPELINING,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-DSN,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-ENHANCEDSTATUSCODES,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
4,>,250-STARTTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-X-ANONYMOUSTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-AUTH,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-X-EXPS NTLM,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-8BITMIME,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-BINARYMIME,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-CHUNKING,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250-XEXCH50,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,250 XSHADOW,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,<,X-ANONYMOUSTLS,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,>,220 2.0.0 SMTP server ready,
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Sending certificate
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CN=YPIEDGE1,Certificate subject
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CN=YPIEDGE1,Certificate issuer name
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,7CERT#,Certificate serial number
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CERT,Certificate thumbprint
2013-06-10T18:41:11.222Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,YPIEDGE1;YPIEDGE1.edge.local,Certificate alternate names
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Received certificate
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,CERT,Certificate thumbprint
2013-06-10T18:41:11.253Z,
YPIEDGE1\Default internal receive connector YPIEDGE1,
94,*,,Received DirectTrust certificate
Vladimir

Similar Messages

IMS 5.2 Can't receive .pdf attachments

I get the following errors when sending emails to anyone on my iMS 5.2 email system.
This is a delivery status notification, automatically generated by MTA stc-imail.southeasterntech.edu on Fri, 26 Aug 2005 14:42:21 -0400 Regarding recipient(s) : [email protected]
Delivery status : Failed. Did not receive the expected protocol response. (students.southeasterntech.edu).
We have been attempting delivery for 5 times.
Maximum delivery tries attempted. Please contact your administrator to contact the destination domain or resend your message. Delivery failed.
Message Information:
Sender : [email protected]
Recipient : [email protected]
MTA Response :4.4.1
The original message headers are included as attachment.
Reporting-MTA: dns; stc-imail.southeasterntech.edu
Final-Recipient: rfc822;[email protected]
Diagnostic-Code: smtp; 4.4.1 Did not receive the expected protocol response.
Action: failed
Status: 4.0.0
We are running iMS 5.2
I can send .pdf attachments from my iMS system to other systems and other users on the iMS system. I just can't receive .pdf attachments from other systems.
Any Ideas?

Ok, first, YOU NEED to install 5.2p2. You can get it here:
http://javashoplm.sun.com/ECom/docs/Welcome.jsp?StoreId=11&PartDetailId=MsgSvr-5.2p2-OTH-G-TP&TransactionId=Try
Second, it would really, truly help me to help you, if you'd answer the rest of my questions.
Does this happen with EVERY pdf attachment, or is it size related?
I would first patch your iMS, then put debug logging on the channel you're receiving the mail through.
set in your imta.cnf, in the channel definition for the channel your mail comes in trough. Add the keywords, "master_debug slave_debug"
then add this to the end of the option.dat file:
mm_debug=5
run:
imsimta cnbuild
imsimta restart
now, you'll get a debug log for every message. Send a test message with a pdf. Save the log file, and post it here.
remove the debug settings, so you don't fill your disk. re-run the two commands above.

Can't receive calendar request from ical (MAC) in MS Outlook 2010

We have local calendar in outlook and ical from MAC users. Now i am not able to receive calendar/meeting request in outlook 2010 from ical (MAC) users, nor they are able to receive my calendar/meeting request.

What's your account type in your Outlook? Does the issue only happen to meeting request? How about sending or receiveing emails?
Please check whether the meeting request can be send and receive in Webmail. Also check whether you can send/receive meeting request from Windows users.

BIS and Exchange 2010 with TMG

Dear all,
I stumped into this problem whereby my client has an Exchange 2010 with mixed-mode mobile users of Active Sync and BlackBerry.
They have this [url]https://mail.***.com.my[/url] as their OWA URL and credentials should be entered as:
Username: Domain\Username
Password: Password
This convention is the same irregardless users accessing from OWA or to setup Active Sync or BlackBerry.
Question are:
1. How do I setup BIS account on my BlackBerry? Method I use is log into my telco portal but the credentials I entered does not recognised by the system.
2. Alternatively, I tried to set it direct on my BlackBerry but was prompt the same error as above which is 'Username must be at least 4 characters'.
3. Does naming convention setup same for Active Sync users and BlackBerry users?
Any help would be greatly appreciated.

Hi and Welcome to the Forums!
rizauden wrote:
1. How do I setup BIS account on my BlackBerry? Method I use is log into my telco portal but the credentials I entered does not recognised by the system.
2. Alternatively, I tried to set it direct on my BlackBerry but was prompt the same error as above which is 'Username must be at least 4 characters'.
BIS itself is provided to you by your wireless service provider. With hundreds of different carriers in the world and dozens of different methods each, there's no way to be sure how to guide you with specifics. I suggest you ring them up and talk to them about how to enable BIS on your BB.
rizauden wrote:
3. Does naming convention setup same for Active Sync users and BlackBerry users?
I'm not sure how ActiveSync works, but the configuration instructions for OWA are here:
KB03133How to integrate a Microsoft Outlook Web Access email address with a BlackBerry Internet Service account
And here are some further helpful KBs on the topic:
KB15173Locate the mailbox name for a Microsoft Outlook Web Access 2007 email account
KB02858Unable
to integrate a Microsoft Outlook Web Access or IBM Lotus Domino Web
Access email address with a BlackBerry Internet Service account
KB04804Error message appears when attempting to integrate a Microsoft Outlook Web Access 5.5 or 2010 account
KB18567BlackBerry
Internet Service cannot connect to a Microsoft Outlook Web Access
account using Microsoft Exchange 2007 or Microsoft Exchange 2010
Good luck and let us know!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Can't receive emails sent from Windows Mobile

After much troubleshooting, I've found that I can't receive emails sent from Windows Mobile users. I never noticed the issue until recently, but I can't pinpoint when the problem began: Leopard 10.5.2, Mail 3.2... not sure.
When a Windows Mobile user sends me an email, it just doesn't show up in my inbox. It does show up in a web client, my iPhone, and in Thunderbird, so I know the mail is being delivered to my mailbox on the server. However, there is no corresponding message located in ~/Library/Mail, so it looks like the message isn't being downloaded from the server. I have emails before and after the stubborn email message, so it hasn't interfered with anything else that I can tell.
Anyone else been able to pinpoint this issue and figure out a fix or workaround? Anyone have any ideas?

I am experiencing precisely the same issues. Messages from Windows Mobiles v.6 (more than just a single handset) are not being displayed in Mac Mail 3.2
I have tried rebuilding mailboxes and changing the IMAP port connecting with Exchange server. The mail is there as I can see it in Outlook, OWA, and OMA
Similar situation to you in that I have no idea when this started to happen, but it can only be in the last 3-4 weeks max.
Please, if anybody has a fix or workaround, or knows what changes have been made to Mac Mail in the last few weeks.
Thanks in advance.

Limit in Mail on receiving large attachments?

Noticed someone else had a problem with receiving large attachments in Mail and my friend and I also have it now.
My question is if anyone knows of a limit to size for recieving attachments in Mail. I noticed that Apple has set a default 10 MB limit on their server versions and thought maybe this is so also in ordinary OS X Mail? If so -- how do I change this in OS X?
(It is really ridiculous that one should not be able to send a small 15 MB file with e-mail any longer -- it is not like we are all getting slower connections, less hard drive space and slower processors all the time, so why does things like this happen?)
Yes, I know the problem is not releated to ISPs, Mail Servers, Firewalls as I have tested for that in most respects. (No problem sending such a file nor downloading it via web mail, etc.) It could be related to IMAP and Apple Mail.
/Jerry (in Sweden where you cannot specify decimals on paper sizes under Mac OS X ... )

Yes, I know the problem is not releated to ISPs, Mail Servers,
Firewalls as I have tested for that in most respects.
Yes it is related since this is not a limitation or problem with the Mail.app or with any email client.
Most ISPs and email account providers have limits on overall message size for received and sent messages similar to the .Mac account message size limit for received and sent messages.
Your ISP or email account provider may not have such a limit (which is unusual) but the recipient's ISP or email account provider may impose a limit.
Have you checked with your ISP or email account provider for this account regarding a message size limit imposed for received and sent messages?
In case you aren't aware, message attachments must be encoded before being sent. The Mail.app uses MIME 1.0 for attachment encoding which is the internet standard. The pre-encoded size of the attachment is increased by 50% or so after the encoding process. A 15MB file will be roughly 22.5MB after the encoding process.
Check What is the maximum size of email attachments? for information on the attachment encoding process.

Can't receive the data from my hardware device by LAN

Hi!
background: For a testing task, I set up a hardware testing platform that including of a power supply device, a hardware to be tested(Device Under Test), a power Meter and a PC.   i build a program to control the hardwares, and they communicate with each other by LAN. at first, the program as a client can normally communicates with my hardware after initializing all hardwares. And then the program turns off the power of my device and turn on power again after delay 60 seconds. after initiantion, my hardware can execute the command which is received from the program, but the program can't receive the data from my hardware. Why my program cannot receive the data from my hardware, after the second time turn on the power of my hardware? the program as client code as below:
int CVICALLBACK ClientRRH (unsigned handle, int event, int error, void *callbackData)
char temp[64]={0};
int ReceiveSize=0;
char *Pos;
switch(event)
   case TCP_DATAREADY:
    if( (ReceiveSize=ClientTCPRead (rrhHandle, readRRHBuffer, 4096, 2000))<0)
                 SetCtrlVal (panelHandle, PANEL_TEXTBOX_INFO,"Read RRH trace error!\n");
                return 0;
    else
     if (ReceiveSize>4096)
      readRRHBuffer[4096]= '\0';
     else
       readRRHBuffer[ReceiveSize] = '\0';
    if (Flag)
      Pos = strstr(readRRHBuffer,orderString);
      if(Pos)
       //strncpy(temp,(Pos+ strlen(orderString)),maxSize);
       _mbsnbcpy(temp,(Pos+ strlen(orderString)),maxSize);
       sprintf(receData,temp);
       *temp=0;
       Flag=0;
       maxSize=0;
       *orderString=0;
    SetCtrlVal (panelHandle, PANEL_TEXTBOX_INFO,readRRHBuffer);
    *readRRHBuffer=0;
            break;
         case TCP_DISCONNECT:
   rrhHandle =error;
            SetCtrlVal (panelHandle, PANEL_TEXTBOX_INFO,"TCP Clienterver has closed connection!\n");
            SetCtrlVal (panelHandle, PANEL_LED_RRH, 0);
            break;
return 0;
int RRH_ini(char *RRH_address)
    ViChar Buffer[200];
    char temp[200];
    int status =0;
if((ConnectToTCPServer (&rrhHandle, 7006, rrhAddr, ClientRRH, NULL, 1000)<0))
    SetCtrlVal(panelHandle,PANEL_LED_RRH,0);
    SetCtrlVal(panelHandle,PANEL_TEXTBOX_INFO,"Connection to RRH fail...\n");
    else
     SetCtrlVal(panelHandle,PANEL_LED_RRH,1);
     SetTCPDisconnectMode (rrhHandle, TCP_DISCONNECT_AUTO);
     sprintf(RRHCommand,"%s\n","asb");
     ClientTCPWrite (rrhHandle, RRHCommand, strlen(RRHCommand), 0);
     Delay(0.2);
     sprintf(RRHCommand,"%s\n","asb#1234");
     ClientTCPWrite(rrhHandle,RRHCommand,strlen(RRHCommand),0);
     Delay(0.2);
     SetCtrlVal(panelHandle,PANEL_TEXTBOX_INFO,"Connection to RRH successful!\n");
   return 0;

Yes that's exactly my problem. The reader sends bytes but without a delimiter. So for example the greeting message I've mentioned earlier "iiAWID..." happens to be 32 bytes, therefore I made the following changes to the code:
public void receive(int x){     // x = expected length of bytes being received
boolean done = false ;
int limit = x ;
int counter = 0;
try {
while (!done)
if (in.ready())
buffer.add(in.read()) ;
counter = counter + 1 ;
if (counter == limit)
done = true ;
}catch(IOException e) { // some code for handling}
and this works fine, however, I'll probably have problems reusing this method later on, because some commands that I will send to the reader will result in responses of indefinite sizes. So I may have a response of length 12 one time and of length 8 the other. but between each response there's a maximum delay of 100ms... is there any way I can utilize that piece of information to improve my code?

I can't receive text msgs from Iphone users-what gives?

Hi, I have had this issue for weeks. I have been trying to find a solution through t-mobile but so far I still can't receive text messages from Iphone users. It is across the board. I know about 5 people with Iphones and I can't get text messages from any of them. Does anyone know why? By the way, they all can receive my text msgs, no problem, but I can't receive theirs. Is it because I don't have internet service on my blackberry? But my friend who has an old Nokia phone with no internet capability receives texts from Iphone users, no problem?? Please help.
Thanks!

Sounds like you are on the right track. But dealing with carriers is, well, frustrating at best. And inconsistent. If you get a CSR that says they can do nothing. Hang up and call back...until you get someone who can really help.
And maybe try different paths into support -- for instance, on the BIS login page for VZW, there is a number listed there that is different than any other of their support numbers. I had a problem with BIS once, called there and they got it fixed within 5 minutes. My account rep and other CSR's had been telling me that there was nothing they could do. So persistence wins out.
Best.
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Can't receive text msgs from other carriers

My carrier is Verizon, and I'm able to receive text msgs from other Verizon carriers. But my problem is that I can't receive text messages from other carriers, such as Tmobile. They can receive my text messages though. I have tried restarting, shutting down and reopening the phone. I've tried calling support, and I logged a ticket. Any idea what to do?

Hello and welcome to the forums;
I would let Verizon follow up on the ticket you opened with them. Does the incoming text never show up at all? Were you ever a customer of another wireless company and either migrated to Verizon or bought out by Verizon (such as Alltel)? Were you able to get texts on your last phone or is this your first Verizon phone?
Let us know how the ticket goes,
TreoAide

TS3276 I am unable to send large attachments such as video or pictures. No problem when using windows 7. How can I send large attachments? Thanks, ..Sam

How can I send large attachments such as pictures or home videos?.....with windows 7 it asked me to send using Skydrive. I downloaded Skydrive and still no better........
Thanks
Sam

How big of a file you can send over an email, is not determined by Apple, but rather by your email service provider. For example, if you have a Gmail email address, they let you send up to 25 MB of data
http://support.google.com/mail/answer/8770?hl=en.
To find out how big of a file your email service provider will let you send, do a google search for "your email provider maximum file size".
If you need to send larger files, look into something like "Drop Box" -
https://www.dropbox.com.

TS2755 i can't receive any photos from anyone and they said whenever they send it it says "Not delivered" ???

please help ! i can't receive any photos from anyone and they said whenever they send a picture it says "Not delivered" ?? pleas ehelp

How large are the files? It is possible your e-mail provider has put a limit on attachments to e-mail.

TS4268 I CAN NOT RECEIVE TEXT MESSAGES FROM PEOPLE USING IMESSAGE - I HAVE MY IMESSAGE TURNED OFF BECAUSE I DO NOT WANT TEXTS GOING TO ALL MY ACCOUNTS - HOW DO I RESOLVE THIS PLEASE HELP - MISSING SEVERAL IMPORTANT COMMUNICATIONS...

I CAN NOT RECEIVE TEXT MESSAGES FROM PEOPLE USING IMESSAGE

On an iPhone your iMessages will go to your phone number.
You can select another email to use on iPod or iPad.
Go to settings
Messages
Send and receive
Check your phone number and uncheck the common Apple ID you share so your messages will not go to other devices.

I was quit group by command. But I had not quit and I can't receive any info from that group.

I was quit group by command. But I have not quit and I can't receive any info from that group.so I can't quit and add again. also receive info. This is very funny.

Bump

Can't receive text messages from other iphone users but can receive them from non-iphone users

I had to recently reinstall mavericks to my MacBook and suddenly I haven't been able to receive text messages from iphone users on my iphone. I can send them but not receive them. Recently I was able to receive a text from an iphone user who turned off his imessages before he texted me. That came through. Of course, this would be difficult to ask every iphone user i know to turn off imessages in order text me. I've also tried to turn off my imessage on my macbook, iphone and ipad and still can't receive them. Lastly, I've also tried resetting my networking settings and that didn't help either. Any suggestions???

I am having the same problem minus the fact that I don't have a Mac computer I just can't receive any messages from iPhone users and I can't turn my iMessage back on at all it keeps just turning it off every time I try to turn it on. any help would be greatly appreciated.

I am facing problem in using viber...can not receive any call from Viber whn keypad is locked and whn i unlock phone thn on opening viber i can see the missed call notification... kindly guide me there is any setting so0 tht i can receive viber calls

I am facing problem in using viber...can not receive any call from Viber whn keypad is locked and whn i unlock phone thn on opening viber i can see the missed call notification... kindly guide me there is any setting so0 tht i can receive viber calls whn my phone is locked even as i can receive calls on HTC

Hi,
This is an official representative of Viber Media.
Unfortunately we cannot change this feature due to Apple's restrictions. :/
For more questions or technical support, please visit our official HelpDesk.
Thanks,
Viber

Exchange 2010 with Forefront, can't receive large attachments from outside ONLY.

Similar Messages

Maybe you are looking for