> I'm assuming that you want to use a dated envelope sender so that
> bounces come through anyhow, even if you don't accept the empty
> sender.
Correct.
> A workaround is to accept mail from 'mailer-daemon@*', which is
> usually the From: field on bounces.
I currently accept that, too. However this isn't universal, and isn't
defined in any RFC as far as I can recall, so <> is safer. Besides,
if everyone gets round the <> spammers by checking for MAILER-DAEMON
instead, the spammers will just start using that, too.
> Try this:
>
> from * tag
> from bare=append
> envelope dated
Should have thought to try that, works great (though it wasn't 100%
obvious from the doc that you can do that).
However, one further comment, and one problem/feature request:
First off, this was my first time trying to use tagged addresses, and
I got caught out by the fact that tagged addresses are only recognized
if they don't match any filter rules. I haven't seen this aspect
clearly documented anywhere (I ended up reading the source to figure
out how it worked :) It's also not entirely clear to me that this is
necessarily what one would want or expect, so I can see there may be
cases where it is useful.
My second problem/feature request is this:
I have two domains, gnomon.org.uk which is registered to me, and
dirac.demon.co.uk, which is a POP account that I pull in by multi-drop
fetchmail [1]. Although gnomon.org.uk is my prefered domain, it
currently just points to a mail forwarding service where I have set up
forwards from all the mail accounts I have to corresponding mail
accounts at dirac.demon.co.uk. There are reasons why I do this, but
there probably not of interest here [2].
The upshot, however, is that whilst the two domains are largely
equivalent, tagged addresses only work under the dirac.demon.co.uk
domain, and I need to force that domain to be used for all tagged
addresses. An attempt to send mail to a tagged address at
gnomon.org.uk will simply be bounced by my mail-forwarding service,
since I have not set up a forward for that address in advance.
Currently I've simply hacked make_dated_address to always use
dirac.demon.co.uk when constructing dated addresses -- and I will
obviously need to do the same for other kinds of tagged addresses.
Any chance of a configuration variable to accomplish this?
-roy
[1] Notably, Demon -- a UK ISP -- is one of the few ISP's where
multi-drop fetchmail can be made to work properly -- ie one can
reliably determine the envelope addresses (sender and recipient) of
the messages, even when a message is transmitted to multiple
recipients in a single transaction. I also happen to have a dial-up
account with them which I need to keep for the foreseable future
because many people know that address...
[2] In case you haven't guessed, it's because I'm on a dynamically
addressed cable modem connection. Whilst I can (and do) use a dynamic
DNS service, running an SMTP listener on a dynamicly addressed machine
is somewhat dangerous. In the event of the IP addresses changing,
there is a period of time when a sending machine might attempt to
connect to my old address, and if that has been allocated to someone
who also runs an MTA, things could go horribly wrong.
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
