/dev/spool/mail/_(randomalphanums)(servername) files (hundreds)

Thread View: comp.mail.misc

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Vasos Panagiotopoulos +1-917-287... Sat, 05 Aug 2000 00:00

#5800

Author: Vasos Panagiotopoulos +1-917-287...
Date: Sat, 05 Aug 2000 00:00

33 lines
2368 bytes

Hundreds of /dev/spool/mail/_(randomalphanums)(servername) files!
                         (eg: "_w2Q3srv", where "srv" is the mail server name)
             Only for one (curmudgeonly fogey) user. Very few for anyone else.

What causes such 0 or 1 bit files to be generated in BSD mailx?

Incoming mail (up to 100 messages per day)?

Disconnected hung jobs?                           (as in "mailx" "NO CARRIER")

Disconnected hung background jobs?   (as in "mailx" "ctl-z" "bg" "NO CARRIER")

Routing from old (long-gone) servers to new servers?
(eg: if id was a@b.c.com and it is now a@q.c.com and b.c.com is long-gone)

Massive "mailer daemon returned mail" miscreated local receipients?

Keeping old mail in /var/spool/mail/ after it's been long-read?

Huge LISTSERV digest messages?

Huge (unwanted) attachments?

Defining a superceding SENDMAIL which adds mail headers using SED then calls
regular SENDMAIL?

Maybe some particular, badly coded mail-list manager software out there
someone is using to send this user messages which end up crashing the system?

Is there some setting in BSD MAILX which failed to be set properly system-wide
(when this problem started a few months ago) which causes this?

I'm the "fogey" and my in-mail is causing the mail server to crash... WHY??!!

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads