Author: halfgaar (Page 9 of 26)
Halfgaar is Wiebe. Wiebe is a contributing author on this weblog. He also has a lot of stuff (such as long, in-depth articles) on his personal website.
Wiebe's day job is as a senior software developer and system administrator at YTEC.
In his free time, he built the free, open-source FlashMQ software. Together with Jeroen and Rowan, he is now building a managed MQTT hosting business around his open masterpiece.
Mailscanner cut out on me, without errors in the log. It was only after turning on debug (which prevents backgrounding and it then only processes one batch) that it showed me.
I needed to change the first line of Mailscanner in /usr/sbin/Mailscanner:
#!/usr/bin/perl -I/usr/share/MailScanner/ -U
Of course, this is far from optimal and it bugs me that Debian didn’t fix this yet, because it’s an old issue.
I’ve had some issues with Xen crashing when I wanted to create a DomU for which the Dom0 had to shrink (see bug report). Therefore, it’s better to force a memory limit on the dom0. That is done with a kernel param.
Add this to /etc/default/grub:
# Start dom0 with less RAM GRUB_CMDLINE_XEN_DEFAULT="dom0_mem=512M"
And make sure you disabling ballooning of dom0 in /etc/xen/xend-config.sxp:
(enable-dom0-ballooning no)
Then run update-grub2 and reboot.
My Xen DomU’s that I upgraded to 11.4 no longer booted, because the xen-blkfront module is missing from the initramfs. To fix, do this when you get the initramfs prompt:
modprobe xen-blkfront
exit
Then after it’s booted:
root@ubuntu:~# echo "xen-blkfront" >> /etc/initramfs-tools/modules root@ubuntu:~# update-initramfs -u
Also look at this post.
When you use xen-create-image to bootstrap an ubuntu, it sets up a grub config file menu.lst. However, this boot config is not kept up-to-date with newer ubuntu’s because they use grub2 (which uses grub.cfg and not menu.lst). And Xen’s pygrub first looks at menu.lst, so if you have a stale file, it will always boot an old kernel.
I ‘Fixed’ it like this (a real fix I have yet to devise, but this works. Actually, I think it is a bug):
The grub hooks in Debian and Ubuntu don’t take the fact into account that the machine might be running as paravirtualized VM. Therefore, it can’t find /dev/xvda to install grub on, which it shouldn’t try. Bug reports exist about this, but it is not deemed important, it seems. The result is that the menu.lst that was created by xen-create-image is never updated and updates to the kernel are never booted.
Pygrub considers menu.lst over grub.cfg (which would give problems with upgrading to grub2). But you can also use it to your advantage. You can edit /etc/kernel-img.conf to look like this (do_symlinks = yes and no hooks):
do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = postrm_hook =
And then make /boot/grub/menu.lst with this:
default 0 timeout 2 title Marauder root (hd0,0) kernel /vmlinuz root=/dev/xvda2 ro initrd /initrd.img
Then uninstall grub. This way, you always boot the new kernel. (actually, I found that you can’t always uninstall grub. I now have machines with grub-pc and grub-common installed, but have an empty /boot/grub with only a menu.lst there. This will keep aptitude from complaining about grub-pc not being able to configure, because it’s unable to detect the bios device for /dev/xvda2 (or whatever)
My HP4050 has a million different drivers to choose from. Some don’t have the maximum DPI, some don’t have other options, like selecting paper output. The one that works the best seems to be “HP LaserJet 4050 Series Postscript (recommended) (grayscale, 2-sided printing)”. However, I have no idea anymore if that came from hplip, foomatic, gutenprint, or whatever.
mysqldump dbname > dbname_bak_before_messing_with_it.sql mysqldump --default-character-set=latin1 --skip-set-charset dbname > dump.sql sed -r 's/latin1/utf8/g' dump.sql > dump_utf.sql mysql --execute="DROP DATABASE dbname; CREATE DATABASE dbname CHARACTER SET utf8 COLLATE utf8_general_ci;" mysql --default-character-set=utf8 dbname < dump_utf.sql
These are some short stepts and pointers to setup a postfix fallback MX. It does not describe postfix basics, nor how to install Mailscanner (a necessisity, because spammers like sending spam to fallback MX’s because they’re usually not as well protected).
First, postfix has a special transport, called ‘relay’, which is the same as SMTP, except that it doesn’t send to the backup MX. In this case, that means it doesn’t send to itself, avoiding loops. The relay transport is the default for all the domains you specify in the relay_domains parameter.
Should the machine have a relayhost defined, you need to disable that for each of the domains you’re a backup MX for. You can do that with transport_maps. In my case, the transport_maps is hash:/etc/postfix/transport_maps. That is a key-value file on which you run ‘postmap’ after you’ve edited it. In it, specify this (the comments explain it):
# When you specify a transport without nexthop, it resets the relay to the # recipient domain (see man 5 transport). And, when the transport is relay, # postfix will not relay to the backup MX, to prevent loops back to itself. So, # because this host has a default relayhost, use the folowwing when you want to # specify a domain for which we are backup MX: # example.com relay
The next step you want to do is take measures to prevent mails to non-existent users piling up in the queue. Because spam is sent to the backup MX all the time, it will relay it to the primary, which rejects it. Your backup host will then bounce all kinds of spam mails…
To fix that, we instruct postfix to use recipient address verification. This causes it to probe the primary host to check the address exists (and caches that info) before relaying.
To enable it, do this:
smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination, reject_unknown_recipient_domain, reject_unverified_recipient unverified_recipient_reject_reason = Address lookup failed # Prevent caching non-existent users, to prevent delivery failures when new users are unknown still. address_verify_negative_cache = no # Setting to 550 to make a reject a fatal error, not a defer. unverified_recipient_reject_code = 550 # The point of a backup MX is to accept mail when the primary is down, so setting this prevents incoming mail being deferred when the address probe cannot be done. # TODO: find out how to actually implement it, because it doesn't work; permit it not a valid option here. #unverified_recipient_tempfail_action = permit
The reject_unknown_recipient_domain prevents probes to domains that don’t exist.
Some extra options, not strictly related to being a backup MX:
smtpd_sender_restrictions = reject_unknown_sender_domain, reject_unknown_helo_hostname unknown_address_reject_code = 550 # Override the default of 5 days, because the point of a backup MX is to keep it around for a while. maximal_queue_lifetime = 21d
I always seem to forget this, and the mailq command is not clear, so here it is:
when you type mailq on a postfix server, the first address listed is the sender, the second the recipient.
(Hmm, this suggests the python version might be better).
aptitude -P install postfix-policyd-spf-perl
Add this to master.cf (but perhaps change the path to the script):
policy unix - n n - - spawn user=nobody argv=/usr/bin/perl /usr/lib/postfix/policyd-spf-perl
Add this to main.cf, directly below/after reject_unauth_destination (if you do it before, you are an open relay):
check_policy_service unix:private/policy
So:
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, check_policy_service unix:private/policy reject_unauth_pipelining, reject_non_fqdn_recipient
The source article has stuff about testing.
Recent Comments