Today I learned through discussions about bisections that there is a script called debsnap. This tool can list versions of a package that are available on snapshot.debian.net, and it can also download a specific .deb for you if you know the desired version.

This tool would have saved me some time during the process of debugging the video driver for X as jotted down in this article: no need to add the source to your apt/sources.list.d/ anymore with this.

The debsnap script is part of the devscripts package.

I am on archlinux, and as you pointed out back in 2013, a lot is outdated.. including our wikis I think. I just want to say a big thank you.. not because I have yet done your tutorial, nor because I have everything working because of it but because thanks to just going through it, you made me understand far more of this mail stack beast I have been contending with.

I could instantly now hack away on stuff and even if it won't work quite yet I now know more what I am doing and what things are.

Thank you very much for this!!!

Kind regards,

@arch.

@Anarcat : oh hey just a quick note after reading your blog post: don't forget to grab all files and to drop them in the appropriate directories (I currently have the habbit of just dropping attachments in dirs named the same as articles, but I guess one could go at this differently)

Also for the article contents, well since I really had very few articles on Drupal, instead of scripting it I just copied contents manually into a bunch of different .md files. What really helped me was that I was already using Markdown in Drupal, so the only changes to the contents that were necessary were for links pointing to images and for embedded videos.

Good luck on the migration! The efforts are really worth it

p.s.: on and wrt that last line in my post: I do indeed receive NO comment spam since I migrated over to ikiwiki. I guess needing to "login" with the cgi script is deterring those pesky pollution generators. (that or the fact that there aren't that many ikiwiki sites out there...)

so far my experience with views_data_export has been less than satisfactory. i would need to create multiple views for comments, tags, nodes, etc, and fiddle with the Web UI until it does what i want.

considering i know the MySQL schema behind all this stuff, it seems simpler to me to tap directly in the database in the back. it certainly feels better than parsing ill-formatted XML spewed by Views 2.x in D6... whee...

i'm documenting my migration work here: http://anarc.at/services/wiki/drupal/

so far my experience with views_data_export has been less than satisfactory. i would need to create multiple views for comments, tags, nodes, etc, and fiddle with the Web UI until it does what i want.

considering i know the MySQL schema behind all this stuff, it seems simpler to me to tap directly in the database in the back. it certainly feels better than parsing ill-formatted XML spewed by Views 2.x in D6... whee...

i'm documenting my migration work here: http://anarc.at/services/wiki/drupal/

@John_Nginx: ah! good to know for the cc/bcc. I was thinking about it for the last couple of days and just couldn't come up with any reason why mail sent via CC: and Bcc: headers wouldn't work if To: was working. After all they are all sent the exact same way, except for the Bcc: ones which get set as one exclusive mail for each Bcc destination and get stripped out of all other emails so that only the concerned destination knows that it was sent a copy.

As for the clamav, greylist and spamassassin not working, maybe one of them is erroring out, which because of the configuration milter_default_action = accept would cause postfix to deliver the mail instead of just loosing it.

I'd suggest you take a look at your logs in /var/log/mail.log (and maybe mail.err): there's probably some error messages when you're receiving mail that could point to the issue at hand.

If you're really not able to find the issue that way, or if you don't know where to look, I suggest then to tear out all milters from option smtpd_milter and add them back in one by one (or only one at a time would make things even more obvious) and run the associated tests from each milter's section in the howto.

You could also paste some error lines in a comment here if you want me to help you out (not too much text at once please.. maybe just the lines that would correspond to one mail being received by your server).

Hope that helps!

Hello, I used your tutorial with success on a Nginx server, thank you for a great job of simplifying and explaining things. I never thought that setting up a mail server would be so complicated ! I have several things which do not work: I am using Thunderbird to log to the mail server and I can send and receive mails OK, but cannot use the "Cc" or "Bcc"... Only the mails sent to the "To" are effectively sent. Is there something I am missing ? On an other hand, clamAV, Spamassassin and greylist do not appear to work. "Corrupted" mails go through untouched. I reverified the step by step from the tuto but couldn't find anything. Any ideas ?