John Morrissey wrote: > > Andre mentioned that he was interested in local patches that people used at > their qmail-ldap sites, for possible inclusion in future releases. Here are > my outstanding patches: > > * Count messages in the Trash toward quota (compile-time option) > qmail-quota-include-trash.patch
In our opinion Trash should not be counted but periodically emptied with a cron job and find -delete. > * Add the remote IP address to the relay-denied error message (very helpful > - instead of having our helpdesk try to get the user's IP address out of > them, they usually get it when the user calls in with the error message). > qmail-add-remoteip-to-relaydenied.patch Smart. I've added that. > * Add the local machine's hostname to message acceptance message. This is > really useful when you have multiple machines behind a layer 4 switch, > when the same "remote hostname" might be a dozen machines. Most MTAs log > the acknowledgement message, so it's much easier to track down what host a > message hit. > qmail-smtpd-ackmessage-hostname.patch Good. Added that too. > * Latest moreipme patch - almost a requirement for operating behind a layer > 4 switch. > http://www.suspectclass.com/~sgifford/qmail/ > * Latest qmail-0.0.0.0 patch with loopback support - Linux (for example) > will answer all requests on 127/8 if the loopback interface has a /8 mask. > Some spammers have MX records that return IP addresses within 127/8, > causing massive mail loops. > http://www.suspectclass.com/~sgifford/qmail/ Agreed about 127/8. We will make a patch that simply rejects any address that starts with 127.x.x.x or 0.x.x.x in qmail-remote mx lookup. I don't think the moreipme patch is the right way to solve the looping problem. I'd say qmail-remote should detect 'itself' by some cookie in the smtp greeting. All smtp accepting and speaking hosts would have a common random cookie string they will check for. SMTP server is saying "220 blabla cookie123" and qmail-remote will check for that. If it finds it boom. Other than that you can reject messages from the same cluster via smtp tcpserver. Put the ip addresses of local sender there. > * IP-based POP3 virtual hosts > qmail-ldap-virtualpop3-20020901.patch We don't think one should have one ip address per domain. However everyone is free to apply this patch themselfes. > * Add a Status: header to messages retrieved via POP. I don't know who wrote > this, but googling for it will probably turn it up. If not, I can always > post a copy. > qmail-pop3d-status.patch What is the advantage of this? > * Sync file metadata along with the file itself (by syncing the directory). > I believe this is required when running qmail on Linux due to differing > file semantics as compared to the *BSDs. > http://www.emptybox.org/collections/daemons/qmail/qmail-link-sync.patch Depends on the filesystem. We don't add that because it's Linux and mostly ext2 specific. -- Andre
