 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] some observations| From | Sent On | Attachments |
|---|---|---|
| Anand Buddhdev | May 16, 2000 4:13 am | |
| Anand Buddhdev | May 16, 2000 5:39 am | |
| Anand Buddhdev | May 17, 2000 4:29 pm | |
| Anand Buddhdev | May 18, 2000 9:59 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [courier-users] some observations | Actions... |
|---|---|---|
| From: | Anand Buddhdev (ar...@anand.org) | |
| Date: | May 17, 2000 4:29:49 pm | |
| List: | net.sourceforge.lists.courier-users | |
On Tue, May 16, 2000 at 12:29:32PM -0400, Sam Varshavchik wrote:
DJB's serialmail package reads the first line for return-path: and the second line for Delivered-To:. Would you consider reversing the order?
Why do you need serialmail? Why does anyone need serialmail? I still don't understand why anyone needs that. I got along fine for a long time, without it, while being intermittently connected through a dialup.
Well, where I used to work before, we had a lot of M$ Exchange customers, who needed to use ETRN-type of solutions. One can, of course, use POP-based or UUCP-based systems with Exchange, but that was Africa, where there's a lack of skills. Serialmail worked well. Since you're not going to support ETRN, serialmail might be useful to some people. Also, it would help sites that are converting from qmail, for example. I don't need this feature now, but this is just something for you to consider.
I don't remember now. qmail-smtpd <= 1.02 used to return multiline responses even to HELO. Then, around April/May of 1998, there was some discussion on the qmail list. One of these weird clients, Lotus, I think, was having trouble with the multi-line response to a HELO; it was expecting a single line. Bad program, I know, but that's what it did.
My general philosophy is to avoid encouraging sloppy programming by tolerating blatant flaws, like that.
Yes. Good point. DJB also had the same attitude. After being hassled numerous times by many users, he changed his code, with a 'sigh' noted in his changelog :-)
I had another question about courier's handling of virtual users. I currently have this in my laptop's qmail configuration:
control/virtualdomains: @anand.org:arb ram...@anand.org: tri...@anand.org:
control/locals: localhost
This causes all mail for @anand.org to be delivered to me, with the exception of 2 addresses, which are delivered to another server; the MX records for anand.org point to that other server. The mail there is put into a common POP mailbox, and my sister's computer downloads it, and uses a filter to sort the mail out for herself and my dad. I've looked in courier's aliases documentation (which handles virtual addressing), and there apears to be no support for this feature of qmail's virtual address handling. Any way round it, or have I missed something?
PS. I tried to use the aliases machanism to forward mail for my sister and dad to the POP mailbox account at the remote server, but that changes the envelope recipient information, and breaks the filters.
-- See complete headers for more info