|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
[BUG?] .forward vs Mailbox
Patrik Rak (patrik
ein.cz)
Tue, 23 Nov 1999 17:10:50 +0100 (CET)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Wietse Venema: "Re: missing lhs causes local mailer failure"
- Previous message: Wietse Venema: "Re: Which is better? Postfix, qmail, exim or zmailer ?"
- Next in thread: Wietse Venema: "Re: [BUG?] .forward vs Mailbox"
- Reply: Wietse Venema: "Re: [BUG?] .forward vs Mailbox"
Hi!
Assume I have /etc/aliases like this:
fork: address1,indirect
indirect: address2
address1: patrik
address2: patrik
And that there is valid ~patrik/.forward - content doesn't really matter,
but let's say it's but let's say it's patrik
some.other.host.
If I send mail to fork, If I send mail to fork, patrik
some.other.host gets one copy, but there is
also second copy which ends in ~patrik/Maildir/ (assuming we use Maildir/).
I don't think this is the expected behavior - once I have a .forward
set to forward mail to another host, I don't expect anything coming into
my mailbox, regardless how complicated aliases the system uses.
I checked the source code and found out that the problem is caused by the
been_here() dupe checking, as I expected. The original intention was too
protect the .forward files which contain self referencing aliases, but it
also causes the unfortunate behavior described above.
Any comments, anybody?
Patrik
- Next message: Wietse Venema: "Re: missing lhs causes local mailer failure"
- Previous message: Wietse Venema: "Re: Which is better? Postfix, qmail, exim or zmailer ?"
- Next in thread: Wietse Venema: "Re: [BUG?] .forward vs Mailbox"
- Reply: Wietse Venema: "Re: [BUG?] .forward vs Mailbox"
This archive was generated by hypermail 2.0b3 on Tue Nov 23 1999 - 10:12:07 CST