E-Mail errors Socket Logging and error message question

[Jim C]

I am using Version 9 and trying to send E-Mail. First, I got a message which states Socket Logging is enabled. Performance will suffer.

What is Socket logging and how do I disable it?

Second, when I tested the E-Mail function, I received the following error.

11/8/2004 5:36:00 PM <-- [00000123] 220 lakermmtao10.cox.net ESMTP server (InterMail vM.6.01.04.00 201-2131-117-20041022) ready Mon, 8 Nov 2004 18:35:12 -0500
11/8/2004 5:36:00 PM --> [00000018] EHLO DenComputer
11/8/2004 5:36:00 PM <-- [00000025] 250-lakermmtao10.cox.net
11/8/2004 5:36:00 PM <-- [00000009] 250-HELP
11/8/2004 5:36:00 PM <-- [00000017] 250-XREMOTEQUEUE
11/8/2004 5:36:00 PM <-- [00000009] 250-ETRN
11/8/2004 5:36:00 PM <-- [00000015] 250-PIPELINING
11/8/2004 5:36:00 PM <-- [00000008] 250-DSN
11/8/2004 5:36:00 PM <-- [00000013] 250-8BITMIME
11/8/2004 5:36:00 PM <-- [00000017] 250 SIZE 5242880
11/8/2004 5:36:00 PM --> [00000012] AUTH LOGIN
11/8/2004 5:36:00 PM <-- [00000032] 502 Command is locally disabled

I am sure this message means something to somebody but not to me. Does anyone know what error I made or how I can correct it.

Thanks, Jim

[Tracy]

I am using Version 9 and trying to send E-Mail. First, I got a message which states Socket Logging is enabled. Performance will suffer.

What is Socket logging and how do I disable it?

This is only on during the connection test. You will not have a problem with this when sending emails through PowerChurch.

Second, when I tested the E-Mail function, I received the following error.

11/8/2004 5:36:00 PM <-- [00000123] 220 lakermmtao10.cox.net ESMTP server (InterMail vM.6.01.04.00 201-2131-117-20041022) ready Mon, 8 Nov 2004 18:35:12 -0500
11/8/2004 5:36:00 PM --> [00000018] EHLO DenComputer
11/8/2004 5:36:00 PM <-- [00000025] 250-lakermmtao10.cox.net
11/8/2004 5:36:00 PM <-- [00000009] 250-HELP
11/8/2004 5:36:00 PM <-- [00000017] 250-XREMOTEQUEUE
11/8/2004 5:36:00 PM <-- [00000009] 250-ETRN
11/8/2004 5:36:00 PM <-- [00000015] 250-PIPELINING
11/8/2004 5:36:00 PM <-- [00000008] 250-DSN
11/8/2004 5:36:00 PM <-- [00000013] 250-8BITMIME
11/8/2004 5:36:00 PM <-- [00000017] 250 SIZE 5242880
11/8/2004 5:36:00 PM --> [00000012] AUTH LOGIN
11/8/2004 5:36:00 PM <-- [00000032] 502 Command is locally disabled

I am sure this message means something to somebody but not to me. Does anyone know what error I made or how I can correct it.

Thanks, Jim

This looks like your email server does not require authentication when sending an email. Some servers require pop (asking the server if emails exist, which requires a login) before allowing the send commands to go through. When this is the case, simply check your email before testing or sending emails.

[Jim C]

I tried not selecting Out going server requires authentication and it would not allow me to use my user name and password. Then I received the message that I could not long on.

I am sure I am making this more complicated than it is but neither method works for me.

Any ideas would be very much appreciated.

Thanks, Jim

[NeilZ]

I tried not selecting Out going server requires authentication and it would not allow me to use my user name and password. Then I received the message that I could not long on.

I am sure I am making this more complicated than it is but neither method works for me.

Any ideas would be very much appreciated.

Thanks, Jim

A few obvious things:

1. Insure that the userid and password you have in PC+ is the one authorized for use by the church to send/receive email. Check with your ISP to see if you need authentication at their servers, if so, you must use the same authentication as is used in your normal email program.

2. Make sure you have an internet connection.

3. Try the test again.


I know it sounds very elementary, but if 1 or 2 is not correct, I suspect you will get those errors.

[Jim C]

Thank you for your help. I was able to get this working and you were right I just did not have the correct settings.

It seems simple once you figure it out but like most things there is few ways to make it work and many ways to mess it up.

Jim

[NeilZ]

Thank you for your help. I was able to get this working and you were right I just did not have the correct settings.

It seems simple once you figure it out but like most things there is few ways to make it work and many ways to mess it up.

Jim

Glad to be of service.