From: "Jens Knoell" <jens@ing.twinwave.net>
To: Linux Admin ML <linux-admin@vger.kernel.org>
Subject: Re: Proper procedure for bounced mails?
Date: Mon, 22 Jul 2002 16:45:37 -0600 [thread overview]
Message-ID: <036f01c231d1$92843920$0264a8c0@wombie> (raw)
In-Reply-To: 15676.29971.791712.488355@cerise.nosuchdomain.co.uk
From: "Glynn Clements" <glynn.clements@virgin.net>
> Whereabouts in the message delivery chain does the script sit? Does it
> process the message as it comes in, or is it fed the message after the
> SMTP server has acknowledged its acceptance?
It uses the Mlocal part of sendmail's config, so it is possible to use the
exit code, as far as I know. But to the best of my knowledge, it's not
possible to return some custom string to indicate the reason for failure, is
there?
> For the former (e.g. if the script is registered as a mailer in
> sendmail.cf, or called from a procmail rule), it should simply report
> a failure via its exit code, so that the SMTP server indicates an
> error immediately. This eliminates the need to construct a bounce
> message.
Absolutely - IF I can somehow return a custom error message like "Message
appears to be spam - look at http://blah.blubb.bleh/spampolicy.html" or some
such...?
> For the latter, then it needs to send a bounce message to the
> *envelope* sender address; sending bounces to any other address may
> result in your domain being blacklisted by mailing lists.
That's what I currently do, I think.
Good point about mimicking sendmail's generic error messages... I hadn't
thought of doing it that way.
Thanks a lot
Jens
next prev parent reply other threads:[~2002-07-22 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 8:29 Proper procedure for bounced mails? Jens Knoell
2002-07-22 12:28 ` James
2002-07-22 19:24 ` Jens Knoell
2002-07-22 21:11 ` Glynn Clements
2002-07-22 22:45 ` Jens Knoell [this message]
2002-07-23 1:01 ` Glynn Clements
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='036f01c231d1$92843920$0264a8c0@wombie' \
--to=jens@ing.twinwave.net \
--cc=linux-admin@vger.kernel.org \
/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).