Hi Michael,
I think that what you're assuming sounds good, that you can pretend that
the mail server is there but not actually show any new mail. Problems
arise when you have IMAP clients (which regularly poll different folders
and want to download parts of mail that they already know about) and
POP3 clients that leave mail on the server.
With the POP3 clients that leave mail on the server, you will get a lot
of calls because when you turn the server back to non-maintenance mode,
the mail left on the server will be downloaded again to the client
(Outlook Express in particular is not very good in this situation). So
the clients will get duplicates and call you to find out what's wrong
with your server.
I think the best two options are:
1. Close the IMAP/POP3/SMTP ports while in maintenance mode. Clients
will timeout. You may get calls with this option.
2. Have scripts which run as fake IMAP/POP3/SMTP servers that return an
error that the client sees that states that the server is currently
under maintenance and to try again later. You will get less calls with
this option.
Either of the above methods would not require any changes to dbmail.
Regards,
Josh.
P.S. Just for interest's sake I wrote this really dodgy script. Put it
in inet for port 143. In Mozilla-thunderbird it gives no errors, just
nothing actually happens. Not sure what Outlook etc will do.
#!/bin/bash
echo "* OK imap maintenance ready"
sleep 2
echo "* CAPABILITY IMAP4REV1 IDLE NAMESPACE MAILBOX-REFERRALS SCAN SORT
THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS
AUTH=LOGIN"
echo "* OK CAPABILITY completed"
sleep 2
echo "* BAD Maintenance mode"
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
