Qumana and WordPress rock … 3rd post without having to cope with browser pitfalls while using the wordpress admin interface.
  Powered by Qumana
Share
Shared Maildir anlegen
maildirmake -S /home/shared/Maildir/
/etc/courier/maildirshared
public /home/shared/Maildir/
Shared Mailfolder mit Namen crons auf dem Mailserver anlegen.
maildirmake -s write -f crons /home/shared/Maildir/
Dateisystemberechtigungen fuer Ordner new unterhalb von .crons anpassen, da dieser Ordner standardmässig ignoriert wird.
cd /home/shared/Maildir/.crons/
chmod o-t new/
ACLs für den neuen Folder anzeigen lassen, mit den bereits erstellten vergleichen und entsprechend korrigieren.
maildiracl -list /home/shared/Maildir/ INBOX.crons
maildiracl -list /home/shared/Maildir/ INBOX.shared1
maildiracl -set /home/shared/Maildir/ INBOX.crons anyone -aex
Die Berechtigungen sollten folgendermassen festgelegt sein:
owner aceilrstwx
anyone cilrstw
Exim Router anpassen, indem die local_parts erweitert werden.
# This router handles special mail addresses to be
# delivered directly into Maildir format shared folders.
# Separate addresses by colons.
# It is after system_aliases so that the aliases file can group things
# to fewer folders here.
shared_folders:
debug_print = "R: shared_folders for $local_part@$domain"
local_parts = "crons:shared1:shared2"
driver = accept
transport = maildir_shared_folder
Exim Config neu laden und Router überprüfen.
/etc/init.d/exim4 reload
exim4 -bt crons@domain.de
Die Ausgabe sollte wie folgt lauten:
R: shared_folders for crons@domain.de
crons@domain.de
router = shared_folders, transport = maildir_shared_folder
Exim Transport
# This transport saves messages in shared folders for special mail
# addresses defined in the 'shared_folders' router - to allow workgroup
# style mail handling with Courier IMAP server (and clients which
# support shared folders)
maildir_shared_folder:
driver = appendfile
maildir_format = true
directory = /home/shared/Maildir/.${local_part}/
create_directory = true
check_string = ""
escape_string = ""
delivery_date_add
envelope_to_add
return_path_add
mode = 0777
no_mode_fail_narrower
user = mail
group = 10000
Share
This is a technique to retrieve a resource out of a ant-based Maven2 Plugin:
<!-- get xsl file -->
<property name="temp.dir" value="./target/maven-propsgen-plugin" />
<mkdir dir="${temp.dir}" />
<whichresource resource="/oids2log4j.xsl" property="xsl.url" />
<get src="${xsl.url}" dest="${temp.dir}/oids2log4j.xsl"/>
<!-- use it -->
<xslt in="${oids.src.dir}/oids.xml" out="${oids.target.dir}/${project.prefix}-appender_snmp_clover.log4j.xml" style="${temp.dir}/oids2log4j.xsl">
<param name="env-name" expression="clover"/>
</xslt>
Share
we had some problems while deploying files to a maven repository. some got it working, some could not authenticate against the repo on windows machines although they were able to connect via ssh command line (cygwin).
if you get sth like
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from repo The authenticity of host 'shell.sourceforge.net' can't be established. DSA key fingerprint is 4c:68:03:d4:5c:58:a6:1d:9d:17:13:24:14:48:ba:99.
Are you sure you want to continue connecting? (yes/no): y
The authenticity of host 'shell.sourceforge.net' can't be established.
DSA key fingerprint is 4c:68:03:d4:5c:58:a6:1d:9d:17:13:24:14:48:ba:99.
Are you sure you want to continue connecting? (yes/no): yes
Password for [EMAIL PROTECTED]:
[WARNING] repository metadata for: 'snapshot foo:bar:4.0.2-SNAPSHOT' could not be retrieved from repository: repo due to an error: Authentication failed: Cannot connect. Reason: Auth fail
[INFO] Repository 'repo' will be blacklisted The authenticity of host 'shell.sourceforge.net' can't be established. DSA key fingerprint is 4c:68:03:d4:5c:58:a6:1d:9d:17:13:24:14:48:ba:99.
Are you sure you want to continue connecting? (yes/no): no [INFO]
while deploying a file to a maven repository, you get 2 options to resolve this:
- switch from scp protocol to scpexe in order to use an external ssh command (e. g. cygwin on windows)
- copy your .ssh directory into your user directory in “Dokumente und Einstellungen”/”Documents and Settings”
the internal ssh representation requires to find a .ssh directory in “Documents and Settings” as this is their ‘home directory’ on windows. by switching to an external ssh your *nix home directory (/home/user/.ssh) is used.
Share
Wir haben den Geschäftsbrief von Michael Lenzen um folgende Anweisungen erweitert:
…Â Â
Ustidnr {DE123456789}Â Â
Steuernummer {12345-67890}Â
…
Â
| Ustidnr |
Einblenden der Umsatzsteuer-Identifikationsnummer im Footer. |
| Steuernummer |
Einblenden der Steuernummer im Footer. |
Zur Verdeutlichung haben wir ein kleines Beispiel zusammengestellt:Â
Aus der Datei g-brief-jit.tex wird das PDF-Formular g-brief-jit.pdf generiert.
Sie müssen hierzu die Dateien g-brief-jit.sty und g-brief-jit.cls in Ihre LaTex-Distribution einbinden.Â
Vergessen Sie nicht, einen texhash durchzuführen
Share