Help, smail wont deliver mail!

Help, smail wont deliver mail!

Post by Matthew Mill » Thu, 10 Sep 1998 04:00:00



Hello,

I am having trouble with mail messages being left undelivered in
/var/spool/smail/input. I use fetchmail to get my mail and run
Slackware. Why does this happen? I used to login all the time
as root and occasionly messages would be left undelivered in
smail input directory. Now having switched over to being a
regular user my mail is never delivered. I have read both man
pages for smail and the mail how-to without any help. I have
struggled with this problem for months.

If you have any suggestions please post and CC it to me as
well (watch the spam fooler), as c.m.s has a quick turn over
I may not see it.

Thank you, Matthew

______________________________________________________________________
The idea that every single thing in the universe should be usable by
the untrained, the uncaring and the uninterested is a fallacy.  There
is nothing wrong with having something that works well when used by the
expert.

- John W. M. Stevens posting in comp.os.linux.advocacy, June 15 1998

 
 
 

Help, smail wont deliver mail!

Post by Mark Carro » Thu, 10 Sep 1998 04:00:00




>Hello,

>I am having trouble with mail messages being left undelivered in
>/var/spool/smail/input. I use fetchmail to get my mail and run

(snip)

Which version of smail are you running? What does smail's log file say
about the undelivered messages on each queue run when you're on-line?

Quote:>If you have any suggestions please post and CC it to me as
>well (watch the spam fooler), as c.m.s has a quick turn over
>I may not see it.

! You must read some very quiet groups, then.

-- Mark

 
 
 

Help, smail wont deliver mail!

Post by Matthew Mill » Thu, 10 Sep 1998 04:00:00






>Which version of smail are you running? What does smail's log file say
>about the undelivered messages on each queue run when you're on-line?

Hi, Mark thanks for the reply. I'm using version Smail 3.1.29.0

Quote:>>If you have any suggestions please post and CC it to me as
>>well (watch the spam fooler), as c.m.s has a quick turn over
>>I may not see it.

>! You must read some very quiet groups, then.

Well, about 20 messages are norm in c.m.s at my feed. It's almost
2pm and the orginal post that I sent at 9:30am is now removed
off the server.

Below is part of smails log from four messages that I recieved
a moment ago. Thanks for your help.

09/09/98 13:36:56: [m0zGoAp-000mhkC] received

|        host: namille2 [127.0.0.1]
|    protocol: smtp
|     program: sendmail

|        size: 2313 bytes

09/09/98 13:36:59: [m0zGoAr-000mhlC] received

|        host: namille2 [127.0.0.1]
|    protocol: smtp
|     program: sendmail

|        size: 2127 bytes

09/09/98 13:37:01: [m0zGoAv-000mhmC] received

|        host: namille2 [127.0.0.1]
|    protocol: smtp
|     program: sendmail

|        size: 2728 bytes

09/09/98 13:37:03: [m0zGoAx-000mhnC] received

|        host: namille2 [127.0.0.1]
|    protocol: smtp
|     program: sendmail

|        size: 2444 bytes


 (ERR_134) transport local: failed to lock mailbox

09/09/98 13:37:09: open_spool: /var/spool/smail/input/0zGoAp-000mhkC:
 lock failed: Bad file number

09/09/98 13:37:10: open_spool: /var/spool/smail/input/0zGoAr-000mhlC:
 lock failed: Bad file number

09/09/98 13:37:10: open_spool: /var/spool/smail/input/0zGoAv-000mhmC:
 lock failed: Bad file number

______________________________________________________________________
The idea that every single thing in the universe should be usable by
the untrained, the uncaring and the uninterested is a fallacy.  There
is nothing wrong with having something that works well when used by the
expert.

- John W. M. Stevens posting in comp.os.linux.advocacy, June 15 1998

 
 
 

Help, smail wont deliver mail!

Post by Bill Cleav » Sat, 12 Sep 1998 04:00:00



>Hi, Mark thanks for the reply. I'm using version Smail 3.1.29.0

>Below is part of smails log from four messages that I recieved
>a moment ago. Thanks for your help.
[snip]

> (ERR_134) transport local: failed to lock mailbox

>09/09/98 13:37:09: open_spool: /var/spool/smail/input/0zGoAp-000mhkC:
> lock failed: Bad file number

[more logs of the same]

I can't specifically tell you what's causing your problem, but I know how to
sidestep it.
Look through man 5 smail and search on 'lock'. There's an option in the smail
config file to use a file-based locking system - use it.
I've got the same version of smail, obtained as a binary compiled for Linux
and had the same problem. Whatever default file-locking method it uses didn't
work for me, and it looks like you've got the same problem.

Good Luck -
Bill

 
 
 

1. SMAIL wont deliver locally

I found that I had to use "deliver" when I installed smail on my
slackware machine.  However, I have since switched to RedHat 2.0 and
therefore now use "procmail" to do my local smail delivery.  Here is my
local driver:

# local - deliver mail to procmail
#
local:  return_path, local, from, driver=pipe; user=root,
        cmd="/usr/bin/procmail -d $($user$)"

--
Tom Cross                        Voice: 612-253-1020    FAX: 612-253-6956

Kendeco Industrial Supply      http://www.cloudnet.com/~tomc/kendeco.html

2. newfs under SUNOS4.1.1

3. SMAIL problem: Doesn't deliver mail-forward problem.

4. SCSI too much data (130)????

5. smail won't deliver my mail

6. Clone Disk under VM 3.1.1

7. Mail delivered by sender gets "failure to deliver"

8. Problems with GDBM, PHP/FI and Apache under FreeBSD

9. Local Mail (using "mail") Does Not Get Delivered?

10. Returned mail: Unable to deliver mail

11. /usr/bin/mail won't deliver mail locally!

12. Returned mail: Unable to deliver mail