masqmail-0.2
view NEWS @ 52:c80a5730bcc5
next release will be 0.2.23
| author | meillo@marmaro.de |
|---|---|
| date | Thu, 27 May 2010 13:33:14 +0200 |
| parents | 03817f849106 |
| children | b067916f7256 |
line source
1 This NEWS file lists changes which may be important for you, especially
2 in regard to compatiblity in upgrades.
4 See ChangeLog file for more details and technical changes that don't
5 affect users directly.
7 The manual pages describe newly added options. Take them for reference.
10 0.2.22
12 - Hello, I'm meillo, the new maintainer and developer of masqmail. Oku
13 handed masqmail over to me, because he wasn't active anymore.
15 - This release includes various fixes for problems in 0.2.21, mainly
16 based on bugs from Debian.
18 - Distribution specific data has been excluded from the distribution,
19 but is separately available on the project's website.
21 - Man pages will not be generated from xml sources in future, but the
22 nroff sources will be maintained directly.
24 - The default online status file is now
25 /var/run/masqmail/masqmail-route, as it already was in the Debian
26 package.
29 0.2.21
31 - Retrospective: Probably, this version was not published in the usual
32 way by oku. I (meillo) grabbed it from Debian's package archive. It does
33 not introduce new functions but fixes security problems, such as writing
34 log files as user `mail'. It also changes the location for pid files;
35 they are stored in /var/run/masqmail/ now.
38 0.2.18
40 - delivery warnings and failures are now also implemented if the
41 connection to a server fails. Because masqmail is designed for dialup
42 networks, a connection failure will merely generate a warning by default.
43 If you deliver in a local network and use the default local_net route,
44 this would generte a failure. You can change this behaviour by setting
45 'connect_error_fail' to either true or false in the route configurations.
47 0.2.17
49 - delivery warnings have been finally implemented: if delivery of a mail
50 fails temporarily, warning mail will be generated, informing the sender
51 of the problem. After some time, the mail will be handled as failing
52 permanently, and be bounced. New options: 'warn_intervals',
53 'max_defer_time' and 'warnmsg_file'.
55 - the message templates for failures and warnings will now be installed
56 into /usr/share/masqmail/tpl/, and no longer to /etc/masqmail/tpl/. The
57 default for the search path (options 'errmsg_file' and 'warnmsg_file'
58 has been changed accordingly.
60 - new option 'last_route'. See man 5 masqmail.route.
62 0.2.12
63 two new options have been added:
64 - do_pipelining will be used only in broken mail setups. Actually, I
65 implemented it only to test such a setup.
67 - helo_name for routes sets the helo_name. This may be useful for
68 eg. ssh tunneling, or if do_correcthelo does not work, because you are
69 behind a firewall.
71 - the old 'remote_port' option should not be used any more. Set the
72 port with mail_host="foo.bar.com:1234" in the route file instead.
74 0.2.11
76 - two new options have been added: do_save_envelope_to for the main
77 configuration and map_h_mail_followup_to_addresses for the route
78 files. See the man pages on purpose and usage.
80 - the route files can now be mode 0400, owned by root. Previous
81 versions had problems when sendmail was called directly by a
82 non-priviledged user, because the route files could not be read.
84 0.2.10
86 - this version should work on FreeBSD. At least I care now if it does not.
88 - masqmail now writes pid files to /var/run/, one for the smtp/queue
89 daemon and one for the get daemon. So you now know whom to kill ;-)
91 - much effort has been put into the Debian package, which now uses debconf.
93 0.2.7
95 - sorry for my reluctany in the last months...
96 - my email address is oku@masqmail.cx. I hope that I keep this for the rest
97 of my life...
99 0.2.6
101 - you can configure the prefered local delivery mechanism for each user. See
102 man page masqmail.conf (5), options mbox_default, mbox_users, mda_users and
103 maildir_users. BIT FAT NOTE: if you used an mda, set mbox_default = "mda"
104 (or use the mda_users option). Just setting mda is not enough any more.
106 - there are the allowed_return_paths and not_allowed_return_paths for the
107 route configurations, this enables better checking for return path addresses
108 than allowed_mail_locals. You can also use this to enable or disable messages
109 from null sender addresses (<>) using "<>".
110 note: this option has been there for quite a time... I just forgot to document it.
112 0.2.5
114 - simple relay checking: if you set do_relay=false in masqmail.conf, users
115 with a return path that is not local will get a 550 reply if they try to
116 deliver to a not local address. This is for users to force them to have a
117 proper configuration. It is _not_ to prevent spammers from using your MTA
118 as a relay, it can be easily forged! masqmail is not designed to be an always
119 accessible MTA for an internet site.
121 - added Maildir support. To use it, add --enable-maildir as ./configure
122 optiom. Currently, if enabled, all local deliveries are to Maildir
123 (in ~user/Maildir), and none to mailbox. This is preliminary, future versions
124 will be configurable (probably together with mda delivery).
126 0.2.4
128 - added -v option, this logs to stdout, so you see what happens when
129 calling masqmail from command line. This is not yet finished, and only
130 for fetching mails completed.
132 0.2.3
134 - new option lock_dir where locks will be put to. Defaults to the spool
135 dir with '/lock/' appended (if spool_dir is /var/spool/masqmail/, lock_dir
136 is /var/spool/masqmail/lock/).
138 - You can use the 'do_uidl_dele' option more reliably. The uidl list
139 will be written immediately after a message was fetched, so if you use the
140 do_uidl and do_uidl_dele option you can safely interrupt masqmail when it is
141 getting mail via pop3, and do not get the message again next time.
143 - there are a lot of new options for ./configure to customize masqmail
144 to your needs. See INSTALL.
146 - Uli Funcke sent a patch with the new options 'local_addresses' and
147 'not_local_addresses' for masqmail.conf. With these, you can declare single
148 email addresses as local, though they normally are not, and vice versa,
149 declare addresses as not local though normally they are (determined with
150 local_hosts). These options are not yet documented.
152 0.2.2
153 - with -go5m you can now run a get daemon, the command 'masqmail -go5m' will fetch
154 mail every five minutes, using the detected online configuration.
156 0.2.1
158 - there is a new option for the main conf: online_gets. Using this option,
159 you can retrieve mail with just calling masqmail -go, masqmail will detect
160 whether it is online (similar to connect_routes (which is now called
161 online_routes)).
163 0.2.0
165 This is the first release of he development branch of masqmail
167 - the default configuration is now /etc/masqmail/masqmail.conf
168 (as it already was for the debian package). The --with-conffile
169 option for configure has been replaced by the --with-confdir option.
171 - added delivery failure notices:
172 o you can customize your own delivery failure report, its
173 default location is /etc/masqmail/tpl/failmsg.tpl
174 o if a delivery via a route fails permanently (the server replied with a 5xx status)
175 the message will be bounced, if it is bounced, no further delivery will be attempted.
176 This is different to previous versions, where failed messages were kept in the queue until
177 it was finally delivered, deleted or forever.
179 - there is a new online detection method: pipe. This allows you more
180 flexibility to detect the current online status, eg. the DHCP status on notebooks.
182 This method will once replace the 'mserver' option,
183 you can already use the program mservdetect to use it:
185 online_method=pipe
186 online_pipe="/usr/bin/mservdetect localhost 222"
188 instead of
190 online_detect=mserver
191 mserver_iface="localhost:222"
193 0.1.9
195 - you can use pipes in routes to implement gateways to uucp, fax, sms etc.
196 The setup is similar to mda transport. See man pages.
198 - for each connection (connect_routes), you can now give a list of
199 route files, which will be used in the order given. You can use the
200 filter rules (allowed_* and not_allowed_* rules) within each route.
202 0.1.8
204 - for pop retrieval and smtp sending you can use a wrapper for eg. ssl
205 tunneling. See man pages.
207 - a user can delete his mail from the spool with -Mrm if received
208 locally, and if you configure with --enable-ident and set
209 ident_trusted_nets also if received via smtp.
211 - a backslash now works to escape characters in the configuration, so
212 you can now use quotes inside quotes. All other characters with a
213 leading backslash will be converted to itself (\a becomes a, \\
214 becomes \).
216 - you can now use an mda for local mails. The mda will be called
217 *after* alias expansion. See documentation for more.
219 0.1.0
220 - masqmail can now retrieve mail with pop3. See the manual on how to do that.
221 - supports now ESMTP AUTH as a client.
222 - when called with -qo (without a connection name), the online status
223 will be checked with the configured method.
225 0.0.10
226 - there is now alias support. Give the location of the alias file (usually /etc/aliases) with eg.
227 alias_file = "/etc/aliases"
228 - delivery to pipes is now possible, but only if it appears in an alias file. Example:
229 pipe: |/usr/bin/command
230 will expand the address pipe to "|/usr/bin/command" which invokes '/usr/bin/command'
231 as the user and group masqmail is running as.
232 - entries starting with '\' in alias files will not be exanded further
234 - changed permissions for queue runs again: got to be root, mail or in group trusted.
236 - some configuration parameters can be read from files, these are
237 allowed_mail_locals, not_allowed_mail_locals, allowed_rcpt_domains, not_allowed_rcpt_domains,
238 map_return_path_addresses, map_h_from_addresses, map_h_reply_to_addresses
239 any entry in these list beginning with a '/' are regarded as
240 filenames, the content of these will be put at that location. Entries
241 in these files are separated by new lines. Example:
242 in the route file you have:
243 map_h_from_addresses = "/etc/masqmail/hfrom.map"
244 and hfrom.map contains:
246 john: John Smith <jsmith@mail.academic.edu>
247 cmiller: "Charlie Miller" <cmiller@foo.com>
249 UPDATE (Jan 2000): The new home location of MasqMail is
250 http://www.innominate.org/~oku/masqmail/, the new email adress of the
251 author is Oliver Kurth <kurth@innominate.de>.
253 0.0.9
254 - see ChangeLog.
256 NOTE: The home location of MasqMail at
257 http://merlin.uni-sw.gwdg.de/~okurth/masqmail/ is uncertain from the
258 beginning of Nov. 1999! See http://www.freshmeat.net for new
259 announcements. I leave the university and begin a new job on Nov. 1st 1999
260 in Berlin :-).
262 0.0.8:
263 - there is now a FAQ page. See docs/faq.html.
264 - added allowed_rcpt_domains option for routes.
265 - added allowed_mail_locals and not_allowed_mail_locals options for routes.
266 - mailq now gives information about the time mails spent in the queue,
267 the message size and the received host.
269 0.0.7:
270 -bug fix release: for statements in two adjacent lines, the second was not recognized.
272 0.0.6:
273 - bug fix release: some MUAs (cucipop) saw the locally delivered mails
274 concatenated. (cucipop is not a MUA but a pop server, but it has to read the
275 mails).
277 0.0.5:
278 - fixed a bug that caused the headers to be lost under some circumstances.
279 - added expand_h_sender_domain option for routes.
280 - rewrote the libresolv part in configure. Should work better now.
282 0.0.4:
283 - MM should now recognize whether libresolv should be linked.
284 - added --with-logdir=LOGDIR and --with-spooldir=SPOOLDIR to set directories.
285 These will be created if not already existent.
286 - added --with-user=USER, --with-group=GROUP options to set user and group id
287 for MasqMail.
289 0.0.3:
290 - MasqMail can now deliver mails that are received at online
291 time immediately to the internet. See the options detect_online,
292 mserver_iface and online_file.
293 - You can define a route configuration for the local net. See option
294 local_net_route.