[risto@dallas lists]$ dig mx tulsapulse.com

; <<>> DiG 9.2.1 <<>> mx tulsapulse.com

;; global options: printcmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35908

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 1

;; QUESTION SECTION:

;tulsapulse.com. IN MX

;; ANSWER SECTION:

tulsapulse.com. 86331 IN MX 10 tulsapulse.com.

;; AUTHORITY SECTION:

tulsapulse.com. 259124 IN NS ns1.mydomain.com.

tulsapulse.com. 259124 IN NS ns2.mydomain.com.

tulsapulse.com. 259124 IN NS ns3.mydomain.com.

tulsapulse.com. 259124 IN NS ns4.mydomain.com.

;; ADDITIONAL SECTION:

tulsapulse.com. 86324 IN A 69.56.173.162

;; Query time: 14 msec

;; SERVER: 127.0.0.1#53(127.0.0.1)

;; WHEN: Wed Oct 8 18:16:13 2003

;; MSG SIZE rcvd: 145

[risto@dallas lists]$ telnet 69.56.173.162 25

Trying 69.56.173.162…

telnet: connect to address 69.56.173.162: Connection refused

[risto@dallas lists]$

–

You don't have anything listening on port 25 and can't receive inbound emails.

Risto

It's always the obvious things that are easiest to fix.

Of course, now that I have figured out why the smtpd script wasn't working I'm still not getting mail.

And just what does this mean?

[root@li2-162]# qmailctl stat

/service/qmail-send: up (pid 30384) 1 seconds

/service/qmail-send/log: up (pid 29861) 390 seconds

/service/qmail-smtpd: up (pid 29865) 390 seconds

/service/qmail-smtpd/log: up (pid 29864) 390 seconds

****messages in queue: 3

messages in queue but not yet preprocessed: 3**** [root@li2-162]#

@HeadachesAbound:

It's always the obvious things that are easiest to fix.

Of course, now that I have figured out why the smtpd script wasn't working I'm still not getting mail.

And just what does this mean?

[root@li2-162]# qmailctl stat

/service/qmail-send: up (pid 30384) 1 seconds

/service/qmail-send/log: up (pid 29861) 390 seconds

/service/qmail-smtpd: up (pid 29865) 390 seconds

/service/qmail-smtpd/log: up (pid 29864) 390 seconds

****messages in queue: 3

messages in queue but not yet preprocessed: 3**** [root@li2-162]#

Have you checked /var/log/maillog?

checked /var/log/qmail/qmail-send/current

Nothing odd that I could see directly. Some errors from last night and earlier this morning when the smptd service wasn't listening.

Then I had a thought…I tried this last night and it failed but I thought why not, let's see what happens. I opened up pine and sent a message from the root account on my linode. I received the email within seconds.

I'm gonna try to put the smtpd service onto a different port so that I can connect to it directly (…stupid cox…) and see if that makes a difference or not.

My first assumption is that maybe the domain isn't resolving somewhere down the line…but then I would expect to get a bounce saying that the mail couldn't be sent. Not sure what is going on at the moment. Any more ideas?

I have confirmed that I can receive mail locally but not externally. This means that I can login to my linode as root and send a message with pine that I can then receive but if I send a message to myself from my email client then it doesn't get delivered.

I have been able to telnet to port 2525 which is where I moved the qmail-smtpd service to but it doesn't work. I never get a 2XX response.

I've looked at everything I can think of but maybe I'm missing something. Ideas?

I never get the greeting from your smtpd. Is your DNS resolution working?

Risto

–-

[root@dallas]# telnet 69.56.173.162 2525

Trying 69.56.173.162…

Connected to 69.56.173.162.

Escape character is '^]'.

As near as I can tell the DNS resolution is working. How would I determine if it is not? I able to ping, tracert, etc. to the domain and when i run dig or host it returns the proper nameserver / ip data. To me, this says that DNS resolution is working.

Hi,

What IP have you set the smtp server to listen, the one listed in the DNS records does not respond to anything on port 25, thus why mail is not been delivered.

Do you have a firewall or anything like that?

Adam

@HeadachesAbound:

…I have been able to telnet to port 2525 which is where I moved the qmail-smtpd service to but it doesn't work. I never get a 2XX response…

I think that I will be refreshing the linode sometime today with a clean image and starting over. It appears that the smtpd service is being finicky and refusing to answer. I keep getting timeout errors.

Why did you put the qmail on to 2525, if it is there the other smtp server across the world will not be able to find it.

Adam

Did this so that I could test it. I can't even telnet to it which concerns me. My ISP (…stupid cox…) blocks port 25 because they are too lazy to hunt down spammers on their own network and simply assume that a spammer will always use port 25. I remember seeing something late last week when I started this that explained how to make it run on 2 different ports but I can't find it now. I'm planning on having it run on 2 different ports at some point in the future so that I can get around my ISP's restrictions.

Well something answers on port 2525

So something is listening on it.

So it would point to a set-up problem with qmail.

Adam

@adamgent:

So it would point to a set-up problem with qmail.

Agreed. But what? I've tried checking all of the setup scripts that control smtpd and I can find nothing that would indicate what the problem is. It is this lack of something that is making me consider just dumping a new linode image on there and starting over.

I've got the smtpd server to listen. It appears as though I had a syntax error in of the script files that wasn't be detected anywhere. Used ' instead of `.

So, now I can get to this point.

[root@li2-162 dloads]# telnet tulsapulse.com 25

Trying 69.56.173.162…

Connected to tulsapulse.com.

Escape character is '^]'.

220 mail.snowprods.com ESMTP

helo tulsapulse.com

250 mail.snowprods.com

mail from:jdale@tulsapulse.com

250 ok

rcpt to: jdale@tulsapulse.com

250 ok

data

354 go ahead

subject:test

test

.

451 qq trouble creating files in queue (#4.3.0)

And I can't do anything to get the messages out of the queue..

[root@li2-162 dloads]# qmailctl stat

/service/qmail-send: up (pid 3751) 2157 seconds

/service/qmail-send/log: up (pid 3753) 2157 seconds

/service/qmail-smtpd: up (pid 3758) 2157 seconds

/service/qmail-smtpd/log: up (pid 3763) 2157 seconds

messages in queue: 6

messages in queue but not yet preprocessed: 0

I have tried to download and compile queue-fix with no luck. I'm getting linker errors stating that there is an undefined reference to errno. Ideas?

Well, it's over now. I've put the linode to rest and cloned a new one.

I think that the whole problem was the thing with using ' instead of `. We'll see if I'm right within a few minutes I hope.

Not sure what I did to it the first time but whatever I did it wasn't happy. It being my linode. I've just spent the last 3 or 4 hours doing a complete re-install of apache / mysql / and qmail. So far so good. I'm able to send and receive and none of the problems I had earlier are there.

I'm thinking that the script syntax errors caused some kind of permission setting to get messed up on the queue but I also think that I may have installed a package that caused an error with my compilers which messed up a whole lot of things. I'm really liking my linode right now.

@HeadachesAbound:

451 qq trouble creating files in queue (#4.3.0)
"make setup" from the qmail source directory should rebuild your mail queue, fixing any permission or other problems.
@HeadachesAbound:

I have tried to download and compile queue-fix with no luck. I'm getting linker errors stating that there is an undefined reference to errno. Ideas?
I've never used with queue-fix, but odds are that you'll find

extern int errno;

somewhere in the source, replace it with

include If you do end up reinstalled, I'd highly suggest using the directions at lifewithqmail.org. These directions are "newbie proof" and if you ever want to get support from the qmail mailing list, this is almost a requirement.