From: sah@borf.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] smtpd crashing
Date: Wed, 23 Aug 2000 14:54:13 -0400 [thread overview]
Message-ID: <200008231854.OAA08632@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 97 bytes --]
Apologies,
clarification: it's large attachments that seem to be the killer.
tks,
sam
[-- Attachment #2: Type: message/rfc822, Size: 3117 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 111 bytes --]
I get email with attachments all the time.
Lots of plan9 stuff, for example, have attachments.
Brantley
[-- Attachment #2.1.2: Type: message/rfc822, Size: 1452 bytes --]
From: sah@borf.com
To: 9fans@cse.psu.edu
Subject: [9fans] smtpd crashing
Date: Wed, 23 Aug 2000 14:36:05 -0400
Message-ID: <200008231836.OAA07564@cse.psu.edu>
Greetings,
smptd seems to be crashing every time a message with an attachment
is sent to someone in our org. Any thoughts?
(subsequently the message is rejected to the author)
sam
next reply other threads:[~2000-08-23 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-23 18:54 sah [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-24 6:36 nigel
2000-08-23 18:40 bwc
2000-08-23 18:36 sah
2000-08-23 21:35 ` Scott Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200008231854.OAA08632@cse.psu.edu \
--to=sah@borf.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).