Incoming mail rejected

My Mail and Entourage mailboxes recently (about 3 months ago) began refusing group email including lists of products from my food buying club. I can receive these messages in a Yahoo mailbox. I have listed the sender in my address book. Since I was having no problem in the past, I assume one of the Tiger updates has installed some kind of spam filter that I don't know about. Does anyone have any idea where this might be and how to adjust it?

Not sure what Mail and Entourage mailboxes refusing
group email means.
These messages aren't downloaded from the server by
the Mail.app or Entourage and this is for a Yahoo
email account?
Or are these messages marked as junk when received by
the Mail.app or Entourage and moved to the account's
Junk mailbox?
Is your Yahoo email account a paid account?
If there was a new spam filter included for the
Mail.app with an OS X or security update (which I
don't believe occurred) and if it did it certainly
would have no effect on Entourage, these messages
would be marked as junk when downloaded/received by
the Mail.app and moved to the account's Junk mailbox.
"Auction" lists of products and numbers are sent to me and 35 other households by a coordinator in a list send. I have been receiving them on this computer since I bought it last July. About three months ago I realized I wasn't receiving the auction emails. Other recipients are receiving them fine. The sender is not aware that they are not received in my mailbox. In trying all kinds of tests I finally got an error message that said "unacceptable content." These messages won't come into my Mail mailbox or my husband's Entourage mailbox. Tech support at my isp said to try a free yahoo mailbox. I did and I can receive the lists to that box.
I have checked the settings in Mail and Entourage for junk mail and the sender is listed in my address book. I don't know what else to do.

Similar Messages

ICloud asked me to reenter my password to get mail and when I did, it rejected my password. I'm trying to reenter in my account information, but it won't let me because the incoming mail server field is blank, but it won't allow me to enter anything.

iCloud asked me to reenter my password to get mail and when I did, it rejected my password. I'm trying to reenter in mail account information, but it won't let me because the incoming mail server field is blank, but I can't enter anything into that field.

No, didn't have to sign out. As I started to, got a messge saying something about losing all my calendar information, which unnerved me so I didn't sign out. It was correcting the password in another email account that corrected the situation for me.

Mail: outgoing and now incoming mail server rejects password

Hello all. Hope you can help with this one.
I was using Mail as normal yesterday. I use the same incoming mail server and SMTP server (my university's Exchange server). Then sending mail suddenly failed. The error message I get is:
The SMTP server “exch.wlv.ac.uk” rejected the password for user “(null)”
Enter your password again or cancel.
The settings are port 995 for outgoing mail, using SSL and requiring password authentication.
I've verified my settings and passwords with IT support. They say they haven't altered anything, and nor have I.
I've tried Connection Doctor: it says Mail connected with the exch. server without any problems. However, under Account Information, the server says (offline).
I've changed ports (to 25 and 587): no success.
I've deleted my password from Keychain and Mail plist and reentered it. No success.
I've verified and repaired permissions.
I'm now not getting incoming mail either: the error message is
There may be a problem with the mail server or network. Verify the settings for account “Staff POP” or try again.
The server returned the error: The connection to host exch.wlv.ac.uk on port 25 failed.
I can send and receive using web-based OWA.
Is there anything else I can do, or is it a server problem?
Thanks,
Aidan

May be no help to you Aidan except comfort in numbers. Mail has started behaving erratically for me in the past week. My inbox and account mail has disappeared and my accounts keep being rejected by the webmail host similar to your problem; password rejected etc. Then Mail closes abruptly telling me there's a problem and offering to send a report to Apple. Mail is version 4.5 and the iMac is 10.6.8. Help!
Maurice

How to block incoming mail with internal domain as sender

Hi all,
Ironport accept incoming mail to internal domains defined in the RAT without verify the sender domain is the same internal domain.
To avoid this I have used a message filter to drop those mails. I can't use the bounce command to avoid to be considered a spammer.
Is there a way to reject those mails with a 5xx error message?
Thanks in advance.
Regards,
Andrea

Securegroup,
jloehler is absolutely correct, when I configure appliances (personally I use a 1 listener config) I set the Default Mailflow Policy to Use the Exception Table ("On") and insure that all incoming mail policies (anything with the ACCEPT action) is set to "Use Default" for this parameter. Then I double check to insure that the RELAY policy is set to "Off" because you don't want to reject outbound messages due to the Exception Table.
Once I've verified that the RELAY is off and Inbound policies are "On" I then populate my exception table with all the internal domains and specify the reject action. Now a quick take away is that the Exception Table only performs the rejection based on the SMTP MAIL FROM not the "From:" header internal to the message itself.
Now with all that said it never fails that there is some internal group that uses 3rd party marketing which spoofs the internal domains so I usually create a new incoming mail flow policy with the Exception Table turned "Off" and create a Sender Group call DOMAINSPOOFLIST which are IPs and Domain names that I allow to spoof internal e-mail addresses with the new mail policy assigned to it.
And that's it.
Sincerely,
Jay Bivens
IronPort Systems

Mail rejects correct Keychain password data

Intermittent problem Number Three with Mail since Leopard 10.5.x: Mail reports that the server rejects log-in data from Keychain (or possibly ignores existing Keychain data).
I've got Mail checking three mail accounts: Two on the same (POP) mail server, and one Gmail (IMAP) account. Sometimes, when checking these accounts, I get an alert that the log-in data were rejected by the server, and am asked to re-enter the data.
If I re-enter the data, it usually just fails repeatedly; the only solution is to cancel the log-in attempt, take the account offline, then back online and check the mail manually. Subsequent automatic log-in attempts are usually successful; unless they fail.
This happens most often with the first of the three accounts, though it's been known to happen with all three.
I have read advice to others with similar problems which points to a corrupted Keychain. This is quite possible, though I've run Keychain diagnostics which return no errors.
This problem began quite some time ago on my Powerbook G4, and has persisted as I migrated my mail data to my new MacBook Pro.
If anyone has any suggestions or insight, I would be interested.

Open Mac Mail then Command , (comma) to open Mail Preferences.
Select the Accounts tab then the Account Information tab.
Type in the correct password under Incoming Mail Server.
Try your email account.
If that didn't help, open Keychain Access located in HD > Applications > Utiliites
Select Passwords on the left.
Use the search field top right corner of the window to locate your email keychain then control click the keychain then click Delete.
Go back to the Mail Account Information window and re type the password under: Incoming Mail Server.
You should be prompted to save that data to a new keychain.

Block incoming mail (spam) overnight?

G5 Mac OS X (10.4.6)
I've noticed that 95% of my spam is delivered to me between 12 am and 8 am. Since friends and collegues rarely send me email during those hours, I was wondering if there is a way to disable Mail during those hours and thereby block the emails from ever making it to my inbox.
I've looked through rules and tried unchecking the "enable this account" box in Preferences but have not found anything that works. Any ideas?
Best,
Lea

Securegroup,
jloehler is absolutely correct, when I configure appliances (personally I use a 1 listener config) I set the Default Mailflow Policy to Use the Exception Table ("On") and insure that all incoming mail policies (anything with the ACCEPT action) is set to "Use Default" for this parameter. Then I double check to insure that the RELAY policy is set to "Off" because you don't want to reject outbound messages due to the Exception Table.
Once I've verified that the RELAY is off and Inbound policies are "On" I then populate my exception table with all the internal domains and specify the reject action. Now a quick take away is that the Exception Table only performs the rejection based on the SMTP MAIL FROM not the "From:" header internal to the message itself.
Now with all that said it never fails that there is some internal group that uses 3rd party marketing which spoofs the internal domains so I usually create a new incoming mail flow policy with the Exception Table turned "Off" and create a Sender Group call DOMAINSPOOFLIST which are IPs and Domain names that I allow to spoof internal e-mail addresses with the new mail policy assigned to it.
And that's it.
Sincerely,
Jay Bivens
IronPort Systems

Mail rejected by Lion Server

Upgraded a test server from snow leopard to lion and have problems with all incoming mail being rejected by the server.
Rejected mail always reads:
Reason: Server rejected MAIL FROM address.
Diagnostic code: smtp;530 5.7.0 Must issue a STARTTLS command first
I've searched for hours and see that there are a couple of explanations. With initial installation I used a self-signed SSL certificate and then removed it according to this discussion. https://discussions.apple.com/thread/3339935?start=0&tstart=0
Also disable spam filters and greylisting.
Reinstalled once and relaized I had the DNS pointing to port 443 and thought that might be the problem and changed DNS with a fresh install. Every time I reinstall Lion Server from scratch going back to the SL install disk and after install under server hardware settings it alwasy initially reads SSL certs for mail (IMAP, POP and SMTP).
Last install I zeroed out drive and reinstalled and still after install it showed certificates for all mail services.
Can't figure out where it could be finding settings to reinstall certificates after they have been completely deleted.
Sending mail works fine.
Any suggestsion? Thanks.

You don't want to do that. In my opinion, smtp should only be accessible via an encrypted connections, ie. TLS. It can represent a security risk and is against best practice.
I have started, building my Lion Server from scratch, rather than migrating it.Things so far seem to be promising. I might be finished by the time Apple releases Mountain Lion Server...
LL

Cannot receive mail - rejected

Hi!
I configured mail service on mac os x server to be reachable from other "internet mail servers". There is a mx dns record for the mail dns name. Port 25 is open on my firewall. My mail server is reachable for other mail servers. I can send emails by my mail server.
The problem is that my mail server does not accept mails from other mail servers. The file mail.log contains the following error code:
Aug 31 23:02:46 mozart postfix/smtpd[18914]: connect from mail.gmx.net[213.165.64.20]
Aug 31 23:02:47 mozart postfix/smtpd[18914]: NOQUEUE: reject: RCPT from mail.gmx.net[213.165.64.20]: 554 Service unavailable; Client host [213.165.64.20] blocked using zen.spamhouse.org; This is not the DNSBL you're looking for.; from=<[email protected]> to=<[email protected]> proto=SMTP helo=<mail.gmx.net>
Aug 31 23:02:47 mozart postfix/smtpd[18914]: disconnect from mail.gmx.net[213.165.64.20]
I installed spamtrainer.
Here is my postconf -n:
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mapsrbldomains =
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,xxx.org
mydomain = xxx.org
mydomain_fallback = localhost
myhostname = mail.xxx.org
mynetworks = 127.0.0.1/32
mynetworks_style = host
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = postdrop
smtpdclientrestrictions = permit_mynetworks rejectrblclient zen.spamhouse.org permit
smtpdpw_server_securityoptions = login,cram-md5,gssapi,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpduse_pwserver = yes
smtpdusetls = no
unknownlocal_recipient_rejectcode = 550
Has anybody an idea what i did wrong.
Thanx in advance
Gerhard

Thank you very much. Incoming mails are not rejected anymore.
But in mail.log I get the following entries:
Sep 1 19:03:43 mozart postfix/smtpd[23431]: connect from mail.gmx.net[213.165.64.20]
Sep 1 19:03:43 mozart postfix/smtpd[23431]: 7ED4F16DF3B: client=mail.gmx.net[213.165.64.20]
Sep 1 19:03:43 mozart postfix/cleanup[23434]: 7ED4F16DF3B: message-id=<[email protected]>
Sep 1 19:03:43 mozart postfix/qmgr[23367]: 7ED4F16DF3B: from=<[email protected]>, size=1077, nrcpt=1 (queue active)
Sep 1 19:03:43 mozart postfix/smtp[23435]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
Sep 1 19:03:43 mozart postfix/smtp[23435]: 7ED4F16DF3B: to=<[email protected]>, relay=none, delay=0, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
Sep 1 19:03:43 mozart postfix/smtpd[23431]: disconnect from mail.gmx.net[213.165.64.20]
Why is the connection to localhost refused? Any ideas? Thanx in advance.
Gerhard

Since installing Yosemite outgoing mail fails. ckd settings all ok. all outgoing servers say (offline) incoming mail ok

Since installing Yosemite outgoing mail fails in Apple Mail. All the servers show (off line) I have checked setting and they are all okay. Incoming mail works. Any help would be appreciated.

Linc,
Hopefull this is what you asked me to do.
READ Nov 16 13:23:23.702 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2abb320
-ERR authorization first
READ Nov 16 13:23:23.702 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
+OK POP3 ready
WROTE Nov 16 13:23:23.702 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
CAPA
WROTE Nov 16 13:23:23.704 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2abb320
APOP ******* af6449209fdef6d4812d2745741609f1
READ Nov 16 13:23:23.711 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fe2e35f1980 -- thread:0x7fe2e2fc4900
* LIST (\Noselect) "/" ""
3.561 OK Completed
WROTE Nov 16 13:23:23.711 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:p03-imap.mail.me.com -- port:993 -- socket:0x7fe2e35f1980 -- thread:0x7fe2e2fc4900
4.561 LOGOUT
READ Nov 16 13:23:23.915 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2abb320
warning: auth_error: authorization failed (authorization failed wrong password)
READ Nov 16 13:23:23.915 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
+OK Capability list follows
EXPIRE 31 USER
TOP
UIDL
USER
XOIP
SASL PLAIN
WROTE Nov 16 13:23:23.915 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
AUTH PLAIN
READ Nov 16 13:23:23.959 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
+
WROTE Nov 16 13:23:23.961 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
READ Nov 16 13:23:23.992 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2abb320
-ERR authorization failed Check your server settings.
INITIATING CONNECTION Nov 16 13:23:23.992 host:pop.secureserver.net -- port:995 -- socket:0x0 -- thread:0x7fe2e2abb320
CONNECTED Nov 16 13:23:24.122 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2b654a0 -- thread:0x7fe2e2f24c70
READ Nov 16 13:23:24.140 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
+OK authentication successful
WROTE Nov 16 13:23:24.141 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
QUIT
WROTE Nov 16 13:23:24.174 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e3c6def0 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:24.198 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2b654a0 -- thread:0x7fe2e2f24c70
+OK <[email protected]>
WROTE Nov 16 13:23:24.198 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2b654a0 -- thread:0x7fe2e2f24c70
CAPA
READ Nov 16 13:23:24.219 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:mail.comcast.net -- port:995 -- socket:0x7fe2e29db980 -- thread:0x7fe2e2b9e030
+OK resmail-po-309v.sys.comcast.net Zimbra POP3 server closing connection
READ Nov 16 13:23:24.484 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2b654a0 -- thread:0x7fe2e2f24c70
-ERR authorization first
WROTE Nov 16 13:23:24.486 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2b654a0 -- thread:0x7fe2e2f24c70
APOP ******** 271ef335c6ede41cf97a027bb2d7c633
CONNECTED Nov 16 13:23:24.565 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
READ Nov 16 13:23:24.585 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4768440 -- thread:0x7fe2e37f2600
250-p3plsmtpa08-04.prod.phx3.secureserver.net hello [73.181.111.109], secureserver.net
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 31457280
250-PIPELINING
250-8BITMIME
250 OK
WROTE Nov 16 13:23:24.586 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4768440 -- thread:0x7fe2e37f2600
AUTH PLAIN ****************************
READ Nov 16 13:23:24.623 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2b654a0 -- thread:0x7fe2e2f24c70
warning: auth_error: authorization failed (authorization failed wrong password)
READ Nov 16 13:23:24.642 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
+OK <***********>
WROTE Nov 16 13:23:24.642 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
USER
READ Nov 16 13:23:24.675 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4768440 -- thread:0x7fe2e37f2600
535 Authentication Failed for jean
INITIATING CONNECTION Nov 16 13:23:24.676 host:smtpout.secureserver.net -- port:465 -- socket:0x0 -- thread:0x7fe2e37f2600
READ Nov 16 13:23:24.921 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
+OK
CONNECTED Nov 16 13:23:24.922 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e30525b0 -- thread:0x7fe2e4855680
READ Nov 16 13:23:24.922 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e3c6def0 -- thread:0x7fe2e06156e0
250-resomta-ch2-04v.sys.comcast.net hello [73.181.111.109], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
READ Nov 16 13:23:24.922 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e30525b0 -- thread:0x7fe2e4855680
220 p3plsmtpa08-10.prod.phx3.secureserver.net ESMTP
WROTE Nov 16 13:23:24.925 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
PASS **********
WROTE Nov 16 13:23:24.927 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e3c6def0 -- thread:0x7fe2e06156e0
AUTH PLAIN (*** 44 bytes hidden ***)
WROTE Nov 16 13:23:24.937 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e30525b0 -- thread:0x7fe2e4855680
EHLO [10.0.0.9]
READ Nov 16 13:23:25.004 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e3c6def0 -- thread:0x7fe2e06156e0
535 5.7.0 ...authentication rejected (6)
WROTE Nov 16 13:23:25.004 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e3c6def0 -- thread:0x7fe2e06156e0
QUIT
INITIATING CONNECTION Nov 16 13:23:25.004 host:smtp.comcast.net -- port:587 -- socket:0x0 -- thread:0x7fe2e06156e0
READ Nov 16 13:23:25.042 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e30525b0 -- thread:0x7fe2e4855680
250-p3plsmtpa08-10.prod.phx3.secureserver.net hello [73.181.111.109], secureserver.net
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 31457280
250-PIPELINING
250-8BITMIME
250 OK
WROTE Nov 16 13:23:25.042 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e30525b0 -- thread:0x7fe2e4855680
QUIT
READ Nov 16 13:23:25.325 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
+OK
WROTE Nov 16 13:23:25.326 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
QUIT
CONNECTED Nov 16 13:23:25.327 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
READ Nov 16 13:23:25.452 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
220 resomta-ch2-10v.sys.comcast.net comcast ESMTP server ready
READ Nov 16 13:23:25.452 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2b654a0 -- thread:0x7fe2e2f24c70
-ERR authorization failed Check your server settings.
WROTE Nov 16 13:23:25.453 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
INITIATING CONNECTION Nov 16 13:23:25.453 host:pop.secureserver.net -- port:995 -- socket:0x0 -- thread:0x7fe2e2f24c70
READ Nov 16 13:23:25.464 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e4826480 -- thread:0x7fe2e2abb320
+OK
READ Nov 16 13:23:25.492 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
250-resomta-ch2-10v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
WROTE Nov 16 13:23:25.492 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
STARTTLS
READ Nov 16 13:23:25.534 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
220 2.0.0 Ready to start TLS
WROTE Nov 16 13:23:25.727 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:25.770 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
250-resomta-ch2-10v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
WROTE Nov 16 13:23:25.772 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
AUTH PLAIN (*** 32 bytes hidden ***)
CONNECTED Nov 16 13:23:25.856 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
READ Nov 16 13:23:25.932 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
+OK <[email protected]>
WROTE Nov 16 13:23:25.932 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
USER *********
READ Nov 16 13:23:26.014 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
+OK
WROTE Nov 16 13:23:26.016 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
PASS **********
READ Nov 16 13:23:26.159 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
+OK
WROTE Nov 16 13:23:26.160 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
QUIT
READ Nov 16 13:23:26.282 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:pop.secureserver.net -- port:995 -- socket:0x7fe2e2c5cb20 -- thread:0x7fe2e2f24c70
+OK
CONNECTED Nov 16 13:23:26.282 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4715e60 -- thread:0x7fe2e37f2600
READ Nov 16 13:23:26.282 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4715e60 -- thread:0x7fe2e37f2600
220 p3plsmtpa11-05.prod.phx3.secureserver.net ESMTP
WROTE Nov 16 13:23:26.282 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4715e60 -- thread:0x7fe2e37f2600
EHLO [10.0.0.9]
READ Nov 16 13:23:27.090 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
535 5.7.0 ...authentication rejected
WROTE Nov 16 13:23:27.090 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e2a6c7e0 -- thread:0x7fe2e06156e0
QUIT
INITIATING CONNECTION Nov 16 13:23:27.090 host:smtp.comcast.net -- port:587 -- socket:0x0 -- thread:0x7fe2e06156e0
CONNECTED Nov 16 13:23:27.133 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
READ Nov 16 13:23:27.141 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4715e60 -- thread:0x7fe2e37f2600
250-p3plsmtpa11-05.prod.phx3.secureserver.net hello [73.181.111.109], secureserver.net
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 31457280
250-PIPELINING
250-8BITMIME
250 OK
WROTE Nov 16 13:23:27.143 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4715e60 -- thread:0x7fe2e37f2600
AUTH PLAIN ************************
READ Nov 16 13:23:27.237 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e4715e60 -- thread:0x7fe2e37f2600
535 Authentication Failed for jean
INITIATING CONNECTION Nov 16 13:23:27.238 host:smtpout.secureserver.net -- port:465 -- socket:0x0 -- thread:0x7fe2e37f2600
CONNECTED Nov 16 13:23:28.514 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
READ Nov 16 13:23:28.514 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
220 p3plsmtpa11-02.prod.phx3.secureserver.net ESMTP
WROTE Nov 16 13:23:28.515 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
EHLO [10.0.0.9]
READ Nov 16 13:23:28.600 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
250-p3plsmtpa11-02.prod.phx3.secureserver.net hello [73.181.111.109], secureserver.net
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 31457280
250-PIPELINING
250-8BITMIME
250 OK
WROTE Nov 16 13:23:28.600 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
AUTH LOGIN
READ Nov 16 13:23:28.680 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
334 VXNlcm5hbWU6
WROTE Nov 16 13:23:28.680 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
amVhbg==
READ Nov 16 13:23:28.761 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
334 UGFzc3dvcmQ6
WROTE Nov 16 13:23:28.764 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
READ Nov 16 13:23:28.848 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
535 Authentication Failed for jean
INITIATING CONNECTION Nov 16 13:23:28.848 host:smtpout.secureserver.net -- port:465 -- socket:0x0 -- thread:0x7fe2e37f2600
CONNECTED Nov 16 13:23:29.250 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
READ Nov 16 13:23:29.250 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
220 p3plsmtpa11-09.prod.phx3.secureserver.net ESMTP
WROTE Nov 16 13:23:29.250 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
EHLO [10.0.0.9]
READ Nov 16 13:23:29.333 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
250-p3plsmtpa11-09.prod.phx3.secureserver.net hello [73.181.111.109], secureserver.net
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 31457280
250-PIPELINING
250-8BITMIME
250 OK
WROTE Nov 16 13:23:29.334 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
AUTH LOGIN
READ Nov 16 13:23:29.413 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
334 VXNlcm5hbWU6
WROTE Nov 16 13:23:29.414 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
amVhbg==
READ Nov 16 13:23:29.494 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
334 UGFzc3dvcmQ6
WROTE Nov 16 13:23:29.497 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
READ Nov 16 13:23:29.587 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e04887b0 -- thread:0x7fe2e37f2600
535 Authentication Failed for jean
INITIATING CONNECTION Nov 16 13:23:29.588 host:smtpout.secureserver.net -- port:465 -- socket:0x0 -- thread:0x7fe2e37f2600
CONNECTED Nov 16 13:23:29.975 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e47ea450 -- thread:0x7fe2e37f2600
READ Nov 16 13:23:29.979 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e47ea450 -- thread:0x7fe2e37f2600
220 p3plsmtpa11-02.prod.phx3.secureserver.net ESMTP
WROTE Nov 16 13:23:29.979 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e47ea450 -- thread:0x7fe2e37f2600
EHLO [10.0.0.9]
READ Nov 16 13:23:30.058 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e47ea450 -- thread:0x7fe2e37f2600
250-p3plsmtpa11-02.prod.phx3.secureserver.net hello [73.181.111.109], secureserver.net
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 31457280
250-PIPELINING
250-8BITMIME
250 OK
WROTE Nov 16 13:23:30.058 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtpout.secureserver.net -- port:465 -- socket:0x7fe2e47ea450 -- thread:0x7fe2e37f2600
QUIT
READ Nov 16 13:23:42.444 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
220 resomta-ch2-03v.sys.comcast.net comcast ESMTP server ready
WROTE Nov 16 13:23:42.445 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:42.488 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
250-resomta-ch2-03v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
WROTE Nov 16 13:23:42.488 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
STARTTLS
READ Nov 16 13:23:42.531 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
220 2.0.0 Ready to start TLS
WROTE Nov 16 13:23:43.261 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:43.309 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
250-resomta-ch2-03v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
WROTE Nov 16 13:23:43.310 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
AUTH LOGIN
READ Nov 16 13:23:43.352 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
334 VXNlcm5hbWU6
WROTE Nov 16 13:23:43.352 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
amNoYXZlejI2
READ Nov 16 13:23:43.390 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
334 UGFzc3dvcmQ6
WROTE Nov 16 13:23:43.391 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
READ Nov 16 13:23:44.496 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
535 5.7.0 ...authentication rejected
WROTE Nov 16 13:23:44.496 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e38bb740 -- thread:0x7fe2e06156e0
QUIT
INITIATING CONNECTION Nov 16 13:23:44.497 host:smtp.comcast.net -- port:587 -- socket:0x0 -- thread:0x7fe2e06156e0
CONNECTED Nov 16 13:23:44.547 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
READ Nov 16 13:23:44.626 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
220 resomta-ch2-07v.sys.comcast.net comcast ESMTP server ready
WROTE Nov 16 13:23:44.626 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:44.670 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
250-resomta-ch2-07v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
WROTE Nov 16 13:23:44.670 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
STARTTLS
READ Nov 16 13:23:44.714 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
220 2.0.0 Ready to start TLS
WROTE Nov 16 13:23:45.553 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:45.617 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
250-resomta-ch2-07v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
WROTE Nov 16 13:23:45.617 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
AUTH LOGIN
READ Nov 16 13:23:45.683 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
334 VXNlcm5hbWU6
WROTE Nov 16 13:23:45.683 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
amNoYXZlejI2
READ Nov 16 13:23:45.722 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
334 UGFzc3dvcmQ6
WROTE Nov 16 13:23:45.723 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
READ Nov 16 13:23:46.847 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
535 5.7.0 ...authentication rejected
WROTE Nov 16 13:23:46.847 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e293f060 -- thread:0x7fe2e06156e0
QUIT
INITIATING CONNECTION Nov 16 13:23:46.847 host:smtp.comcast.net -- port:587 -- socket:0x0 -- thread:0x7fe2e06156e0
CONNECTED Nov 16 13:23:46.892 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
READ Nov 16 13:23:47.256 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
220 resomta-ch2-09v.sys.comcast.net comcast ESMTP server ready
WROTE Nov 16 13:23:47.256 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:47.303 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
250-resomta-ch2-09v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-STARTTLS
250 OK
WROTE Nov 16 13:23:47.303 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
STARTTLS
READ Nov 16 13:23:47.347 [kCFStreamSocketSecurityLevelNone] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
220 2.0.0 Ready to start TLS
WROTE Nov 16 13:23:51.666 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
EHLO [10.0.0.9]
READ Nov 16 13:23:51.714 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
250-resomta-ch2-09v.sys.comcast.net hello [2601:1:9700:1284:b418:17eb:5e03:7cb1], pleased to meet you
250-HELP
250-AUTH LOGIN PLAIN
250-SIZE 36700160
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 OK
WROTE Nov 16 13:23:51.715 [kCFStreamSocketSecurityLevelTLSv1_0] -- host:smtp.comcast.net -- port:587 -- socket:0x7fe2e29c46a0 -- thread:0x7fe2e06156e0
QUIT
<E-mails Edited by Host>

ICloud incoming mail server

Good day all,
For most of the day yesterday I and many others were having difficulty authenticating iOS mail and OS X mail clients to the Apple "appleid.apple.com" servers. It may have been a load issue or a configuration issue on the servers (which are used for both mobileme and icloud. By mid-evening on the east oast of the USA the occurences of password reject were diminishing and now seem to have stabilized.
Today I am having problems with the incoming server bank at "p02-imap.mail.me.com". It either does not connect or does not respond in adequate time to satisfy the Apple mail clients.
I have 4 ex-family MobileMe accounts converted to iCloud. Three of them were assigned "p99-imap.mail.me.com" for incoming mail. The fourth was assigned "p02-imap.mail.me.com". In all instances the incoming mail server was populated during account migration and is not editable.
As an issue of curiousity, does anyone know how the incoming mail server was assigned? Did the first 250,000 of us get one server and the next another, etc.?
I suspect "pXX-imap.mail.me.com" is a server bank with load balancing implemented across multiple servers. Or maybe (shudder) we are hard assigned one physical server (p99, p02, etc.).
It would be interesting to know how Apple's new improved data center(s) have been logically configured for redundancy, load balancing and fail over.
Sorry - it's the geek in me wondering why I can't get my email from a specific Apple resource ("p02-imap.mail.me.com").
Alex

Chris CA wrote:
CAP2010 wrote:
Unfortunately, no matter what I type into the incoming email server while attempting to recreate my account in Mail, the program always tries to connect to p99-imap.mail.me.com.
You don't have to type any server info for your iCloud account.
System prefs > Mail, Contacts & Calendars - New account and select iCloud.
Unfortunately, that was step 1 in the process of not being able to use my mail in iCloud. Also, I have tried changing my password to 8 numbers/letter, etc. in accordance with the new AppleID rules, but that did not work. I have also tried deleting and recreating my account multiple times. I am definitely willing to try any more suggestions.

Why is my Incoming mail server showing gray or "not active?"

I am having trouble receiving e-mails since changing my apple password. The password works fine in other regions but the Mail accounts section seems to be "rejecting" something I am providing as infor or username or Alias or what? and the box shows the correct information under incoming mail but in grayscale????

Hello DRMSBSR,
Welcome to the Apple Support Communities. If you are not able to receive email on your Mac, the next step to try is to remove the account and then add it back in.
Go to Apple menu > System Preferences > iCloud. Then sign out of the account and then sign back in.
iCloud: Set up iCloud Mail on your devices and computers
http://support.apple.com/kb/ph2621
Regards,
-Norm G.

Drop incoming mail from specific domain.

Is this possible and if so how do I configure?
I want to be able to drop incoming mail from, lets say, "@bigspammailer.com". Is there a way to do this? I have created an "Incoming Mail Policy" but don't know where to apply it.
What I've tried that has not worked ....
Incoming Content Filters, created a filter with Condition of "mail-from = = "@myemaildomain.com"$", and an action of "Drop".
HAT Overview, creating a Sender Group using Mail Flow Policy "BLOCKED" setting SBRS to various settings including "None".
I've grown exhausted reading through manuals. If you know of a document that directly addresses this issue (assuming it's possible) I'm not opposed to reading it.
Any help will be greatly appreciated!
Jim Mc.

Sender Groups can be used to block messages based on the hostname or IP of the sending machine. It does not look at who the message is "from." To block mail based on the envelope sender you need to use a Filter or the Sender Verification Exception Table.
Your example of a content filter seemed ok but after you create a filter you need to make sure that it is enabled for the incoming mail policy. Create your filter and then select Mail Policies -> Incoming Mail Policies. Under the column called Content Filters you will need to
1) turn content filters on (default is off)
2) enable the specific content filter that you just created
You can also enter it in the Sender Verficiation Exception Table. You need to enable it under your ACCEPTED policy under Mail Policies -> Mail Flow Policies. There is a radio button all the way at the bottom for the exception table. Once you have it enabled then you can select Mail Policies -> Exception Table and add @domain.com to always reject.

Specific incoming mail types block for further incoming mails??

Since upgrading my 3GS to iOS4, I have experienced a new strange phenomenon within mail-reception:
Now and then I am receiving a mail, which places itself at the bottom of the incoming mail list. Such mails are always WITHOUT any sender/WITHOUT any contents, and ALL of them dated 1.1.1970! I can't wipe them out, neither can I delete them/move them. The effect is further that upon reception of such mail types, any further reception of mails is BLOCKED - I only hear the sound when new mails are coming in, don't SEE them in the top of the list. The only immediate way of eliminating the problem is to make a COLD reboot of the phone - then the odd mail(s) at the bottom of the incoming mail list disappear(s), and new mails are coming freely in without obstructions. A new restore of the system appears to be without effect.
I would be grateful for any hints which might eliminate the problem, thanks!

CUCM takes decisions on called number, not calling. one all time favorite question a quick search on NetPro would have provided you the answer
Call Blocking Configuration Examples
http://www.cisco.com/en/US/customer/tech/tk652/tk90/technologies_configuration_example09186a00803f818a.shtml#con11
Reject Calls
http://www.cisco.com/en/US/partner/tech/tk652/tk90/technologies_tech_note09186a0080325e8e.shtml#reject
In case you ask, only h323 can do this.
MGCP can NOT do this
in case you want to block an outgoing call from the fax to a particular number create a route pattern with the exact number and block the call.
HTH
javalenc
if this helps, please rate

Sender Mail Adapter - Incoming Mail Validation

Hi Group,
I am using sender mail Adapter to read the incoming mails from mail server,I have couple of questions:
1.How we can configure adapter to read the mails from particular user.
2.after reading the mail I am only taking subject line in to the mapping,is there any way we can validate whether the incoming
subject line is in the right define form or not.
3.how we can archive once after reading mail.
4.Is there any performance affect on settling polling interval.
Could you please help .
Regards,
Rajiv

Hi,
Refer Michael's steps on similar requirement.
Picking mails from a particular sender using mail sender adapter
Regards
Krish

Incoming mail going to Archive, not Inbox

On Dec, 2 I submitted this question:
Dec 2, 2013 6:12 AM
My incoming mail now goes to the archive file instead of the inbox file. I have changed nothing and it still shows up in the inbox but allnew notifications go to the archive file. I am using OSX 10.9 Any ideas hoiw to fix this?
iMac, OS X Mountain Lion
It was suggested to delete the account and then add it anew. That seemed to work fine, but two weeks later it all began again. All the incoming mail goes to an Archive folder and no new notifications are shown in the new mail accopunt? I hate to have to delete and reopen the accoiunt every few weeks.
Any ideas? I see the same issue on other discussions but no explanations?

What email program are you using?

Incoming mail rejected

Similar Messages

Maybe you are looking for