You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Steve Brewin <sb...@synsys.com> on 2003/06/09 21:35:42 UTC

[PATCH] Fetchmail

Hi,

Patches for fetchmail. I hope I have attached everything in the required
formats, if not, please let me know. I had to zip them up to get around
Apache's mail server message size limitation of 100K.

Changes are summarised below. Read the patched james-config.xml and the
class comments, particularly for MessageProcessor for full details...

1) Increased robustness. Some exceptions were being swallowed, others were
not handled causing the task to silently fail.

2) Greater flexibility. In brief...
	a) It is now possible to reject mail based on the intended recipient being
remote, not a James user,
or on a blacklist.

	b) What happens to the mail on the fetched from server after delivery or
rejection in each of the above states
can be specified in the config.xml.

	c) X-Headers are added to the envelope of messages injected into the input
spool so that mailet/matchers can     detect these states and process them
if so wished.

	d) Fetchmail can optionally fetch mail for all James users (with a suitable
POP3 server account) so no changes to config.xml are required. New and
deleted users are discovered each time the task is run.

	e) (d) can be combined with the ability to leave messages on the server for
which an intended recipient cannot
be found to allow configurations in which mail is always delivered to the
intended recipient. The patched james-config.xml explains this.

3) Corrects an originator address with a user part but no domain part so
that it can be injected into the James input spool.

Any questions, please ask.

-- Steve