SMTP Problem

I don't know wtf I've done, but my SMTP port is closed and I don't know how
to open it.

I tried to send an email this morning and got an error message telling me
that Thunderbird couldn't reach smtp port for mail.isp.com, so I thought my
isp might be having problems.

When this didn't clear up after several hours I tried Evolution, same
problem. I tried my Earthlink account, same problem, so I nmapped
mail.isp.com -p 25 -P0 and it told me their port was open. So I nmapped
myself and saw my port 25 was closed.

I went into Mutt and saw I had lots of emails from one particular account in
my inbox, old stuff, not deleted from my server. It's my wife's email
account and I have Kmail set up for her to check on my Linux box, but it
leaves them on the server until she downloads them on her laptop.

Anyway, all her email is there in Mutt, and it never used to be. I am
trying to learn Mutt and have it set up to use POP for one of my accounts,
but all our isp accounts use mail.isp.com for both incoming and outgoing.
Not sure what's going on there, but her account is the only one with mail
currently on the server.

Anyway, I have also been playing with Gnus under XEmacs, and I saw that the
last email I sent was two days ago under XEmacs, and it worked fine.

I tried more email with XEmacs and it doesn't work now either, but it says
"starting sendmail" or something like that. I think XEmacs may have set my
sendmail protocal to sendmail rather than SMTP and closed that port, but
that doesn't make any sense to me.

I killed sendmail and tried again, but my SMTP port is still closed. I'm
just a home user, a refugee from Monopoly Crapware who doesn't have much
knowledge of protocols.

Any ideas what's going on here? I can get email, but not send it, and have
no clue how to open my SMTP port.

Thanks,

--
(E-Mail Removed) is valid, but for a faster reply replace usenet with vcg3rd.
"Some things don't need the thought people give them." -Hobbes

On 2004-09-21, Bo Grimes <(E-Mail Removed)> wrote:
> I don't know wtf I've done, but my SMTP port is closed and I don't know how
> to open it.
<snipping very long rambling story>

If you are using a firewall, try to turn it off and try if you can
reach port 25 of your ISP mail server. If it does work, you have to
debug your firewall settings, otherwise is your ISP problem.

Davide

--
"If a camel flies, no one laughs if it doesn't get very far."
-- Paul White

On 21 Sep 2004 07:30:42 GMT, Davide Bianchi <(E-Mail Removed)>
wrote:

><snipping very long rambling story>

I'm sorry to have annoyed you. When one doesn't know what the problem is he
doesn't know what information will be crucial to someone who may be able to
solve it.

>
> If you are using a firewall, try to turn it off and try if you can
> reach port 25 of your ISP mail server. If it does work, you have to
> debug your firewall settings, otherwise is your ISP problem.

I didn't touch my firewall, so why would it suddenly decide that accessing
port 25 is verboten? What makes you think it's my ISP's problem when their
port 25 is open and mine is shut?

I tried again this morning with the same error message. Decided the hell
with my 15 day uptime, booted into Windows and had no problems. Rebooted
into Fedora and it works.

Two possibilities, as I see it. Either my ISP fixed the problem in the five
minutes it took me reboot into Windows or the rebooting itself fixed/reset
something.

I sure hate to think Linux required a reboot to resolve an issue.

--
(E-Mail Removed) is valid, but for a faster reply replace usenet with vcg3rd.
"If we wanted more leisure, we'd invent machines that do things less
efficiently." -Calvin's dad

On 2004-09-21, Bo Grimes <(E-Mail Removed)> wrote:
> What makes you think it's my ISP's problem when their
> port 25 is open and mine is shut?

If you want to debug a problem you have to isolate one possible cause
at a time and check it. If you don't start from one side, you'll never
know. Unless you have a crystal ball of course. Mine, the batteries are
low.

> I sure hate to think Linux required a reboot to resolve an issue.

It doesn't if you don't screw up the configuration without saving it.
Davide

--
Mustgo, n.:
Any item of food that has been sitting in the refrigerator so
long it has become a science project.
-- Sniglets, "Rich Hall & Friends"

On 21 Sep 2004 10:51:37 GMT, Davide Bianchi <(E-Mail Removed)>
wrote:

> On 2004-09-21, Bo Grimes <(E-Mail Removed)> wrote:
>> What makes you think it's my ISP's problem when their
>> port 25 is open and mine is shut?
>
> If you want to debug a problem you have to isolate one possible cause
> at a time and check it. If you don't start from one side, you'll never
> know. Unless you have a crystal ball of course. Mine, the batteries are
> low.

Which is what I spent a lot of time doing, trying to isolate the cause,
reading man pages and nmaping ports. All of this was in that rambling story
if you had bothered reading it.

>
>> I sure hate to think Linux required a reboot to resolve an issue.
>
> It doesn't if you don't screw up the configuration without saving it.

I didn't change a single thing. For some reason you want to blame me even
though I did nothing different. You seem to be looking for an argument,
treating me like a troll, but since my problem is solved I'll just
unsubscribe from this group.

--
(E-Mail Removed) is valid, but for a faster reply replace usenet with vcg3rd.
"When life gives you a lemon, make lemonade." -Susie "I say, when life gives
you a lemon, wing it right back and add some lemons of your own!" -Calvin

Bo Grimes <(E-Mail Removed)> wrote:
> On 21 Sep 2004 07:30:42 GMT, Davide Bianchi <(E-Mail Removed)>
> wrote:

> ><snipping very long rambling story>

> I'm sorry to have annoyed you. When one doesn't know what the problem is he
> doesn't know what information will be crucial to someone who may be able to
> solve it.

> >
> > If you are using a firewall, try to turn it off and try if you can
> > reach port 25 of your ISP mail server. If it does work, you have to
> > debug your firewall settings, otherwise is your ISP problem.

> I didn't touch my firewall, so why would it suddenly decide that accessing
> port 25 is verboten?

It may or it may not, but in any case that's irrelevant. But if you
want a real answer, doing other things on your computer may affect your
firewall settings, like upgrading applications - you may upgrade a
security setting ...

> What makes you think it's my ISP's problem when their
> port 25 is open and mine is shut?

It's irrelevant - you are not mailing to your port 25, but to your
ISPs. It's unusual for your port 25 to be closed to enquiries from
localhost, but it may simply reflect the fact that you don't have a
sendmail daemon running, so that there is "no answer" when someone
calls.

> I tried again this morning with the same error message. Decided the hell

So what?

> with my 15 day uptime, booted into Windows and had no problems. Rebooted
> into Fedora and it works.

Well, it sounds highly likely that your sendmail daemon died. simply
LOOKING would have todl you! Why don't you look?

> Two possibilities, as I see it. Either my ISP fixed the problem in the five
> minutes it took me reboot into Windows or the rebooting itself fixed/reset
> something.

Complete random bullshit.

> I sure hate to think Linux required a reboot to resolve an issue.

It didn't - and you didn't resolve it. Instead you panicked, started
thinking like a lunatic, instead of rationally and linearly, and pulled
the button on the system. I would guess that your /var partition is
full up with log files or tmpfile dross, and sendmail ceased running
for lack of space. Reading your logs or looking around would have told
you so. On reboot, stuff got cleaned.


Peter

Bo Grimes <(E-Mail Removed)> wrote:
> On 21 Sep 2004 10:51:37 GMT, Davide Bianchi <(E-Mail Removed)>
> wrote:

> > On 2004-09-21, Bo Grimes <(E-Mail Removed)> wrote:
> >> What makes you think it's my ISP's problem when their
> >> port 25 is open and mine is shut?
> >
> > If you want to debug a problem you have to isolate one possible cause
> > at a time and check it. If you don't start from one side, you'll never
> > know. Unless you have a crystal ball of course. Mine, the batteries are
> > low.

> Which is what I spent a lot of time doing, trying to isolate the cause,
> reading man pages and nmaping ports. All of this was in that rambling story
> if you had bothered reading it.

That is not debugging. Debugging consists of looking. You identified a
port 25 on your machine as closed (irrelevant though that is), so you
next have to look at why it is closed (if it interests you). It may
be that there is no daemon listening there, or it may be that you have
blocked that port via a firewall or tcp wrappers. Look at your firewall
rules and hosts.allow/.deny, etc.

You did none of that.

Peter

Bo Grimes <(E-Mail Removed)> wrote:
<long story about how he found his wife's e-mail when trying to send
e-mail with various clients>

What is your problem?
Is it that you cannot send e-mail?
Is the problem still there?

You got me confused.

Please be short and specific. If somebody thinks he/she can solve your
problem with additional information, he/she will ask you for that
information.

A good rule how to describe problems:
- Tell what commands you typed/clicked.
- Tell what happened, including all relevant error messages.
- Tell what you wanted to happen.
- Tell what version of the software you are using.

Yours,
Laurenz Albe

On Tue, 21 Sep 2004 11:41:00 GMT, P.T. Breuer <(E-Mail Removed)> wrote:

>> I didn't touch my firewall, so why would it suddenly decide that accessing
>> port 25 is verboten?
>
> It may or it may not, but in any case that's irrelevant. But if you
> want a real answer, doing other things on your computer may affect your
> firewall settings, like upgrading applications - you may upgrade a
> security setting ...
>
>> What makes you think it's my ISP's problem when their
>> port 25 is open and mine is shut?
>
> It's irrelevant - you are not mailing to your port 25, but to your
> ISPs. It's unusual for your port 25 to be closed to enquiries from
> localhost, but it may simply reflect the fact that you don't have a
> sendmail daemon running, so that there is "no answer" when someone
> calls.
>
>> I tried again this morning with the same error message. Decided the hell
>
> So what?
>
>> with my 15 day uptime, booted into Windows and had no problems. Rebooted
>> into Fedora and it works.
>
> Well, it sounds highly likely that your sendmail daemon died. simply
> LOOKING would have todl you! Why don't you look?
>
>> Two possibilities, as I see it. Either my ISP fixed the problem in the five
>> minutes it took me reboot into Windows or the rebooting itself fixed/reset
>> something.
>
> Complete random bullshit.
>
>> I sure hate to think Linux required a reboot to resolve an issue.
>
> It didn't - and you didn't resolve it. Instead you panicked, started
> thinking like a lunatic, instead of rationally and linearly, and pulled
> the button on the system. I would guess that your /var partition is
> full up with log files or tmpfile dross, and sendmail ceased running
> for lack of space. Reading your logs or looking around would have told
> you so. On reboot, stuff got cleaned.

What a load of arrogant bullshit. I resubscribed out of a sense of
obligation to inform everyone that I am an idiot. I have no problems
admitting when I make mistakes and no problems apologizing. I do it in
COL.advocacy all the time.

I knew the problem had to be something simple, and it was. However, you
didn't even come close with all your self-important, gobbledy-geek.

One of my kids changed KPPP to connect via Earthlink, an account I no longer
use and is set to expire any day now. Of course ISP.com's smtp wouldn't
work via Earthlink. When I rebooted KPPP reset to my default connection.

Now, I can admit I'm stupid. Can you admit you're an ass? Everything I
know of Linux is self taught after over a decade using Windows. I have no
education or training in computers. I am just an average home user; yet, I
use slrn under Fedora and tried to RTFM and help myself before asking for
help.

Doesn't matter. Usenet hasn't changed in the 13 years I've been posting.
Ask a question, bend over, grab your ankles and get ready to be reamed.
Everyone doesn't know how to debug firewalls, sift through logs and such.

However, what you called complete random bullshit was in fact correct.
Rebooting reset something. Now, you can go give yourself a cronjob.

--
(E-Mail Removed) is valid, but for a faster reply replace usenet with vcg3rd.
Nothing I do is my fault.
-- Calvin

Bo Grimes <(E-Mail Removed)> wrote:
> On Tue, 21 Sep 2004 11:41:00 GMT, P.T. Breuer <(E-Mail Removed)> wrote:
> >> I didn't touch my firewall, so why would it suddenly decide that accessing
> >> port 25 is verboten?
> >
> > It may or it may not, but in any case that's irrelevant. But if you
> > want a real answer, doing other things on your computer may affect your
> > firewall settings, like upgrading applications - you may upgrade a
> > security setting ...
> >
> > It's irrelevant - you are not mailing to your port 25, but to your
> > ISPs. It's unusual for your port 25 to be closed to enquiries from
> > localhost, but it may simply reflect the fact that you don't have a
> > sendmail daemon running, so that there is "no answer" when someone
> > calls.

> > Well, it sounds highly likely that your sendmail daemon died. simply
> > LOOKING would have todl you! Why don't you look?
> >
> >> I sure hate to think Linux required a reboot to resolve an issue.
> >
> > It didn't - and you didn't resolve it. Instead you panicked, started
> > thinking like a lunatic, instead of rationally and linearly, and pulled
> > the button on the system. I would guess that your /var partition is
> > full up with log files or tmpfile dross, and sendmail ceased running
> > for lack of space. Reading your logs or looking around would have told
> > you so. On reboot, stuff got cleaned.

> What a load of arrogant bullshit.

It's completely accurate. Keep your insults to yourself, please!

> I resubscribed out of a sense of
> obligation to inform everyone that I am an idiot. I have no problems
> admitting when I make mistakes and no problems apologizing.

Then do so.

> I do it in
> COL.advocacy all the time.

???

> I knew the problem had to be something simple, and it was.

The problem is you. You lied, you bullshitted, you dissed people who
tried to help you.

> However, you
> didn't even come close with all your self-important, gobbledy-geek.

There is nothing there except an accurate guess at what your problem
might be given your arrogant silly half-assed description of what your
"problem" "was". If that is your way of saying thank you to people who
try and help you correct your bad vision and tunnel syndrome, then you
can go and find a lake and and a concrete block, and connect yourself
somehow between the two.

> One of my kids changed KPPP to connect via Earthlink, an account I no longer

So that affects the fact that your "port 25 is closed" HOW? Answer, it
doesn't. Therefre either you lied, or AS I SAID, you don't have a
sendmail running. And it appears you never did. But whatever, it
certainly is IRRELEVANT, AS I SAID.

> use and is set to expire any day now. Of course ISP.com's smtp wouldn't
> work via Earthlink. When I rebooted KPPP reset to my default connection.

What on earth do you mean? Kppp does not "reset". It is as it is.


> Now, I can admit I'm stupid. Can you admit you're an ass? Everything I

You are a double-assed windbag with a head full of arrogant stupidity,
is what you are. You give false reports about nothing in particular,
and when told that your reports are irrelevant and fictitious you go
off and reboot your machine. You are a danger to the computing world.
When you discover your own lies you don't even notice them for what
they are but instead spout arrogant windage about other irrelevancies.
Instead of saying thanks to people who actually gave your evidently
silly reports even a bit of credence, taking you seriously enough to
bother guessing what the real facts may be behind your ignorant and
malobserved ramting ramblings, you slag them off for not having the
same level of stupidity that you possess.

> know of Linux is self taught after over a decade using Windows. I have no
> education or training in computers.

You apparently have no education or training FULL STOP. Your head is a
mess. Fix it.

> I am just an average home user;

No, you are a computing idiot. *I* am an average home user.

> yet, I
> use slrn under Fedora

Is this supposed to be some sort of marvel? Are we supposed to oooh and
aah? What IS slrn anyway? Some sort of news client (says he, scratching
his TIN affectionately)?

> and tried to RTFM and help myself before asking for

No you didn't. Helping yourself starts with looking. Not looking at
manuals or whatever your evidently fuzzy and administrative or
commercial mindset thinks is the relevant authority figure in your
life, but looking at THINGS. That's right. You. Looking. Not scrambling
to mummy or daddy or the chief technician, but you, looking at your
machine.

> help.


> Doesn't matter. Usenet hasn't changed in the 13 years I've been posting.

It's you that's the problem.

> Ask a question, bend over, grab your ankles and get ready to be reamed.
> Everyone doesn't know how to debug firewalls, sift through logs and such.

Yes they do. Everyone does, because everyone can THINK.


> However, what you called complete random bullshit was in fact correct.

It was complete and utter nonsense. Name a single correct fact in
there.

> Rebooting reset something.

No it didn't. According to your latest description (oh, shoot me for
being so silly as to give you even a faint bit of credence AGAIN!), you
changed the settings in kppp. They stay changed. They do not go away.
What I GUESS your offspring (are you ALLOWED to reproduce, oh, please
save us ...) did, was ADD another entry to kppp and leave the tab open
at that entry, and then you come in and stab in your blind unobservant
way at that tab, instead of noticing that its not your tab.

Nothing has changed. Closing kppp would also have "reset" it (in your
terms!) to show you the default connecton tab, which is YOURS. No need
to reboot. Your lack of looking caused your problem.


"Now, you can go give yourself a cronjob".

Unquote.

Peter