SMTP/Sending issues

[c0ur7n3y]

OK, Anne, I'm really making you earn that $5 this month. ;)

I reformatted tonight and copied every little detail down except my mail settings (D'oh!) because I was 99.9% sure that the incoming and outgoing were both mail.expresslyerrands.com.

Verizon is my ISP and I'm positive that they weren't listed as my outgoing mail server.

Yet I can't send. I'm getting socket errors.

Should authentication be checked or no? I remember it being checked. But I (obviously) could be wrong.
Should SSL be checked?

I remembered it being pretty basic/straight forward yet no matter what combo I try (including outgoing.verizon.net) I'm erroring out (not timing out - it's pretty instantaneous).

I'm afraid if I call Verizon they'll tell me to ask you and I'll be bounced around like a pinball for all eternity, never being able to send mail again. lol. I don't have an e-mail account through verizon, so I can't test it that way.

Help?

[12Wonder]

POP3 (incoming): mail.yourdomain.com
SMTP (outgoing): mail.yourdomain.com

Do not check the authentication box


Anne

[c0ur7n3y]

Nothing seems to be working. I've trashed the account and recreated. I've even set them up in Netscape to see if I was missing something (trying both mail.mydomain.com and outgoing.verizon.net).

Incoming and outgoing are mail.expresslyerrands.com
Auth isn't checked
SSL isn't checked for outgoing
SPA isn't checked

Incoming is working smashingly.

I'm going to reset them, reboot, go to bed, and maybe in the morning it'll all, by some technological miracle, be working. In the meantime, if ya got any brilliant ideas, I'll take 'em. :-)

[c0ur7n3y]

A ha! I figured it out. (I know you were losing sleep over this, Anne. ;) )

It was my firewall.

I shut down zone alarm and voila, I could send. Even though I (thought I) had OE set up correctly within the firewall. So at least I'm not going completely nuts. Now I have to reconfigure zone alarm, but that's a lot easier than beating my head against a wall like I was last night. LOL.

:D

[12Wonder]

Users' firewalls are one of the most common causes of not being able to get through to one thing or another - anything from cpanel to email. Sometimes an automatic update (eg Windows or Norton) can reconfigure stuff without any warning, so it's always one of the things you should check.

Glad you got it worked out.

Anne

[telron]

550 Connection denied after dictionary attack
????? this is what i get when sending

[Brandon]

Your IP is probably blacklisted. It's one of many ways Anne blocks spam attacks. Please open a support ticket with Anne, she'll fix it.

[telron]

Thanks Brandon
but why after 2yrs this get blacklisted
i can still recieve mail

[Brandon]

There's probably some setting on the server that if somebody sends email from your domain to x number of non-existent addresses within y amount of time, the server will stop outgoing mails for a given period.
Spammers must have recently tried the "dictionary attack" method, which the server has detected and stoppped.

[12Wonder]

Telron, what smtp setting are you using? Your own isp's smtp or your domain's smtp?

Also, try to send an email to the same address you tried before, but via your domain webmail instead of via pop and see if you get the same reject message.

Anne

[telron]

I am using my domain smtp
i sent mail from web mail ok

[telron]

you know what i just realize it started when i got the warning about email space quoter on my webmail so i clean them out from then i cant send mail from outlook

[12Wonder]

Hang on let me look into a couple of things.

[12Wonder]

Telron, someone using the IP of your ISP --comcast, roadrunner, earthlink or whoever your ISP is, has sent dictionary spam to the server.

Has nothing to do with your account on darrion, as evidenced by the fact that you are able to send mail just fine straight from the server itself via webmail.

It is your ISP's IP that is blocked. When mail is sent via your domain it contains your ISP's IP address in the header and that is allowed to relay mail through the darrion server.

That IP is temporarily blocked and is now not allowed to relay mail. These blocks are usually run by a Dictionary Attack ACL on the ISP's server, and are usually cronned to clear the blocked IP list every hour or two. If you are still not able to send mail via Outlook/OE by now, contact your ISP and ask them to clear their ACL list if possible.

Anne

[telron]

Ok I Call They Did Not Know What I Was Talking About But
They Walked Me Through Setting Up A Pop Email And I Sent A Test From My Outlook And It Went So I Tried From My Domain Again And It Will No Send

[12Wonder]

Are you saying now the problem is completely reversed and you are now able to send from Outlook but not webmail? :confused:

Both I and one of Monte's crews have done tests from your domain's email account, using Outlook, Outlook Express, and also using your hosting account's webmail via browser. Every single test worked for all of us and there was no problem with either sending or receiving.

Bottom line: this is not a server issue and there is absolutely nothing on the server preventing you from either sending or receiving mail by any method. If you get no assistance from your ISP's first-line tech support, you need to ask to speak to a tech support supervisor at your ISP.

Anne