On 2013-07-12 Fri 11:55 AM |, J Gao wrote:
Now I would like your advises on my system so I can improve it more.
- Postfix 2.6.6
Old.
- Courier(Support virtual domain)
Dovecot instead of Courier?
- Mailman maillist
Look at mlmmj instead of Mailman - no web interface needed.
Am 13.07.2013 20:11, schrieb Craig R. Skinner:
I appreciate if you can give me advise so I can further improve my system.
No Apache, PHP or webmail. HTTP was designed to transfer hyperlinked
text files, not do dynmaic stuff with root access to the whole box.
Beware!
in case of root
On 2013-07-13 Sat 20:50 PM |, li...@rhsoft.net wrote:
but what has the protocol HTTP to do with the underlying
application?
OK then, shove every frigging thing down port 80's throat.
Why bother with Postfix, IMAP, ftp, ssh, ping, traceroute,
Just have 1 port on the box that does it
On 07/13/2013 11:15 AM, J Gao wrote:
http://vault.centos.org/6.4/os/Source/SPackages/postfix-2.6.6-2.2.el6_1.src.rpm
And patched with quota patch.
That's brilliant, now you can't get support for it anywhere.
You don't need to patch postfix to get quotas, dovecot 2 has a policy
daemon that
I'm trying to get check_policy_service working right by returning an error
on a full mailbox to avoid back scatter. The check_policy_service works
fine, except when it comes to virtual alias mappings. When running the
check_policy_service on the virtual alias user my
smtpd_recipient_restrictions
Cassidy Larson:
I'm trying to get check_policy_service working right by returning an error
on a full mailbox to avoid back scatter. The check_policy_service works
fine, except when it comes to virtual alias mappings. When running the
check_policy_service on the virtual alias user my
Figured it out. Returning a DUNNO from the policy service for valid
under-quota and unknown users causes postfix to proceed to the checking of
aliases/users. This allows the mailbox over-quota rejection to work
successfully for valid users, and allows virtual aliases to be accepted
while denying
What setting determines how long postfix should attempt to deliver an
email if target server is not available?
Will this setting work with smart host configuration where smart host
is temporarily unavailable?
Thanks in advance
