On Sat, 15 Nov 2003 20:27, Roman Medina wrote:
in that case maildrop should put the mail in the queue and set it to
"temproary unavailable" as it was done with all mails in earlier
versions.
Is it due to the version we are using? Do new versions correct the
problem? Perhaps the solution is to upgrade... or perhaps hack the
source?
i'm using version 1.6.3 - the last recent one.
before i compiled the deb-package by myself, i had a maildrop-mysql
package (version 1.3.?). there, maildrop didn't bounce the mails. every
not deliverable mail was in the queue afterwards. this is also not a
very good solution because the queue is filled up and the senders which
probably misspelled some emailadresses doesn't get an immediate answer.
maybe after some time (default 5 days?) postfix is giving up.
another missing thing is a "catchall" address. the postfix-mysql
extension supports an emailadress @domain.ch, which fetches all mail.
i don't know how much interests there are with the recent spam attacks.
i had to disable catchall functions for some domains because some
spamers abused randomly selected senderadresses. because all sender
addresses were valid, these domains got flooded by mailerdaemon answers
:)
-tom
12 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] MySQL support for mai...
