Category the Archives: the Linux
Procmail + kdialog build the e-mail alert script
Mutt is really an artifact, the more you use more to feel cool. Unfortunately, the tools command line mode has drawbacks: the relatively weak ability to interact with X, such as Mutt wooden e-mail alerts. In Gnome2 the years before the mail-notification can deal with (this stuff is mad more system resources, it seems to remind monitor file changes), this tool after Gnome3 completely does not work, but there is no follow-up version . Frogs abandon Gnome, replaced by KDE, but also did not find the mail to remind tool for KDE and so has been brewing write your own. E-mail alerts, nothing more than monitor the mailbox to change, you can check at several points: directly using POP / IMAP protocol to check the server-side monitor MTA action monitoring MDA action monitoring MUA action to monitor the mailbox file / directory to change the direct access server is the most direct way However, since the MTA regarded e-mail is down again, and again to monitor the server a bit around the Proton, this method of monitoring gmail / hotmail and the like mailbox is still very good. Monitor MUA's action, adam8157 students to do so, monitor the Mutt startusbar special string through Mutt filter to send notify messages. Monitor the mailbox file / directory change is the practice of mail-notification, but if you do not want polling about the kernel open inotify support. Monitor the MTA action, the frog did not carefully studied, it seems that some of the behavior management needs of MDA, so the frog directly in MDA Add to remind script. Monitor the MDA action, which is the practice of the frog, using the nested the block of the procmail mail pipe to a script to extract e-mail sender, title and content, then send the notify. Message to remind the script has been done: the http://blargasm.com/post/7980037487/evolution-new-mail-notifier frog take over modified, the remove pynotify, direct calls to the kdialog command to send messages. The modified script here: http://code.google.com/p/gfrog/source/browse/mail/mail-notifier.py script there, and then modify the ~ /. Procmailrc filter rules which need to monitor joined: 0 # Some filter rule {: 0 c | /. mail,-notifier.py: 0 # Here is your the inbox ... Continue reading
Configuration wordpress mail
Frog continue to shift the vps Today's theme is tuned wordpress send a message. Before the in Dreamhost above, the mail system has been configured, wordpress does not require any settings you can directly send a message. Vps on the frog in order to save resources, is not installed on the mail server, so I want to send a message, you also need their own torment. Frog is first of all think of a lightweight MTA configuration, for example msmtp and the like, and then modify the php.ini the sendmail_path parameter, so that it points to the msmtp. So that the php program has the capacity of mail, but such problems is the mail-sending server is fixed, and need to configure an account to do the login server, if a user want to use their own server to send certain messages, such a configuration can not be achieved. In order to achieve the perfect solution, the frog they found in a circle, found that wordpress has been integrated one PHPMailer [1] class, and provides a wp_mail function [2] to send mail, set the SMTP plug-in [3] to facilitate We configure the SMTP server and outgoing mail account information. Frogs chose the WP Mail SMTP plugin is very simple, fill out all the parameters, wordpress, you can send mail. References: [1] PHPMailer http://phpmailer.worxware.com/ [2] the Function Reference for / wp_mail http://codex.wordpress.org/Function_Reference/wp_mail [3] allow WordPress to send mail via SMTP http:// goto8848.net/2008/04/wordpress-mail-via-smtp /
Install Xmind in Fedora with deb package
The original file location: http://www.xmind.net/share/gfrog1/install-xmind-in-fedora-with-deb-package/
The NGINX on open https
The frog of the new VPS is based on nginx, just because of the rumors nginx small memory pressure when performance is good. Of course, in order to obtain this benefit, we still have to pay a price, such as nginx apache htaccess control on each directory need to write the nginx configuration file, this is very inconvenient for ordinary users. Oh, a little beside the point, continue to say that the https issue is not complicated, in fact, to the nginx configuration https online ready-made templates, change your own domain name and directory location like. The following is a complete example [1] [2]: (from here) upstream test.com, {the server 192.168.1.2:80;} server {the server_name test.com,; the include port.conf; ssl on; ssl_certificate server.crt ; # $ {nginx_install_dir} / conf / server.crt ssl_certificate_key server.key; # $ {nginx_install_dir} / conf / server.key error_page 497 "https:// $ host $ uri? $ args"; location / {proxy_pass http: / / test.com,; the include proxy.conf; # auth_basic "status"; auth_basic_user_file trac.passwd;} ... Continue reading
A bunch of Tips (4)
Today's Tip is about virtualization. The cause of the problem is the network configuration of the frog was used VirtualBox inconvenient, not the network connection type after the start of the guset system (later version made improvements, but not enough comfortable), NAT mode can not be directly linked with Host system communication. So the frog pain determined to learn the use of Linux tap and br equipment, write a feet would have to get the virtual machine network. This script also can be used in a KVM virtual machine. According to the configuration file, this script will establish a series of tap devices, and then Bridge Street up to several br device, and then set the IP on the br, if you need the NAT function is to configure iptables rules. Script file here: http://gfrog.googlecode.com/hg/script/vnet.sh configuration file as follows: USER = gfrog # specify the user name when you create the tap device VNET_NUM = 2 # need to create a virtual network EXITIF = eth0 # SNAT egress interface # The following is the configuration of each virtual network vnet1] = 4 # virtual network contains VETH_NUM tap device the number VNET_IP = 11.11.1.1/24 # virtual network br device configured ip address DONAT = no # need to do nat [vnet2 VETH_NUM = 4 VNET_IP = 11.11.2.1/24 DONAT = the yes EXITIF = wlan0 # specified for this virtual network special SNAT export the configuration script needs a confget program parse the configuration file, the procedures in the debian / ubuntu source, the fedora Department need to look for. Also note that, because every time you create the tap device MAC address will change when using a KVM virtual machine needs to start the virtual machine to the network card specified MAC address, to prevent the card name in the guest system.
