前ほど「pixiv Sketch 描きづらいなぁ」とは思わなくなりました。同人誌制作で Krita を使っていたんですが、以前より線が引きやすくなった気がします。あと、ショートカットを覚えたからですね。どこかで説明されてるのかもしれませんが消しゴムモード切り替えが Eで出来るんですよね。消しゴムはキーを離すと自動的にブラシに戻るんですが、戻らないときは Bで切り替わります。この辺のキーバインドが Krita と一緒だったのですんなり慣れました（他のソフトはどうなってるんだろ）。この辺の切り替えがスムーズに出来るようになったことで修正がしやすくなったのでちょっと時間をかけて品質を上げようと思うようになりました。
smtp_sasl_auth_enable (default: no)
Enable SASL authentication in the Postfix SMTP client. By default,
the Postfix SMTP client uses no authentication.
Example:
smtp_sasl_auth_enable = yes
smtp_sasl_mechanism_filter (default: empty)
If non-empty, a Postfix SMTP client filter for the remote SMTP
server's list of offered SASL mechanisms. Different client and server
implementations may support different mechanism lists; by default, the
Postfix SMTP client will use the intersection of the two.
smtp_sasl_mechanism_filter specifies an optional third mechanism list
to intersect with.
Specify mechanism names, "/file/name" patterns or "type:table" lookup
tables. The right-hand side result from "type:table" lookups is
ignored. Specify "!pattern" to exclude a mechanism name from the list.
The form "!/file/name" is supported only in Postfix version 2.4 and
later.
This feature is available in Postfix 2.2 and later.
Examples:
smtp_sasl_mechanism_filter = plain, login
smtp_sasl_mechanism_filter = /etc/postfix/smtp_mechs
smtp_sasl_mechanism_filter = !gssapi, !login, static:rest
smtp_sasl_password_maps (default: empty)
Optional Postfix SMTP client lookup tables with one username:password
entry per sender, remote hostname or next-hop domain. Per-sender
lookup is done only when sender-dependent authentication is enabled.
If no username:password entry is found, then the Postfix SMTP client
will not attempt to authenticate to the remote host.
The Postfix SMTP client opens the lookup table before going to chroot
jail, so you can leave the password file in /etc/postfix.
Specify zero or more "type:name" lookup tables, separated by white‐
space or comma. Tables will be searched in the specified order until a
match is found.
smtp_sasl_security_options (default: noplaintext, noanonymous)
Postfix SMTP client SASL security options; as of Postfix 2.3 the list
of available features depends on the SASL client implementation that
is selected with smtp_sasl_type.
The following security features are defined for the cyrus client SASL
implementation:
Specify zero or more of the following:
noplaintext
Disallow methods that use plaintext passwords.
noactive
Disallow methods subject to active (non-dictionary) attack.
nodictionary
Disallow methods subject to passive (dictionary) attack.
noanonymous
Disallow methods that allow anonymous authentication.
mutual_auth
Only allow methods that provide mutual authentication (not
available with SASL version 1).
Example:
smtp_sasl_security_options = noplaintext
smtp_sasl_tls_security_options (default: $smtp_sasl_security_options)
The SASL authentication security options that the Postfix SMTP client
uses for TLS encrypted SMTP sessions.
This feature is available in Postfix 2.2 and later.
smtp_tls_security_level (default: empty)
The default SMTP TLS security level for the Postfix SMTP client; when a
non-empty value is specified, this overrides the obsolete parameters
smtp_use_tls, smtp_enforce_tls, and smtp_tls_enforce_peername.
Specify one of the following security levels:
none
No TLS. TLS will not be used unless enabled for specific desti‐
nations via smtp_tls_policy_maps.
may
Opportunistic TLS. Use TLS if this is supported by the remote
SMTP server, otherwise use plaintext. Since sending in the clear
is acceptable, demanding stronger than default TLS security
merely reduces interoperability. The "smtp_tls_ciphers" and
"smtp_tls_protocols" (Postfix >= 2.6) configuration parameters
provide control over the protocols and cipher grade used with
opportunistic TLS. With earlier releases the opportunistic TLS
cipher grade is always "export" and no protocols are disabled.
When TLS handshakes fail, the connection is retried with TLS
disabled. This allows mail delivery to sites with non-interop‐
erable TLS implementations.
encrypt
Mandatory TLS encryption. Since a minimum level of security is
intended, it is reasonable to be specific about sufficiently
secure protocol versions and ciphers. At this security level and
higher, the main.cf parameters smtp_tls_mandatory_protocols and
smtp_tls_mandatory_ciphers specify the TLS protocols and minimum
cipher grade which the administrator considers secure enough for
mandatory encrypted sessions. This security level is not an
appropriate default for systems delivering mail to the Internet.
dane
省略
dane-only
省略
fingerprint
省略
verify
省略
secure
省略
Examples:
# No TLS. Formerly: smtp_use_tls=no and smtp_enforce_tls=no.
smtp_tls_security_level = none
# Opportunistic TLS.
smtp_tls_security_level = may
# Postfix >= 2.6:
# Do not tweak opportunistic ciphers or protocol unless it is essential
# to do so (if a security vulnerability is found in the SSL library that
# can be mitigated by disabling a particular protocol or raising the
# cipher grade from "export" to "low" or "medium").
smtp_tls_ciphers = export
smtp_tls_protocols = !SSLv2, !SSLv3
# Mandatory (high-grade) TLS encryption.
smtp_tls_security_level = encrypt
smtp_tls_mandatory_ciphers = high
以下略
Nov 16 08:04:32 debianpostfix/smtp[5265]: warning: SASL authentication failure: No worthy mechs found
Nov 16 08:04:32 debianpostfix/smtp[5265]: 6D638409F6: SASL authentication failed; cannot authenticate to server smtp.gmail.com[108.177.97.108]: no mechanism available
Nov 16 08:04:32 debianpostfix/smtp[5265]: connect to smtp.gmail.com[2404:6800:4008:c00::6c]:587: Network is unreachable
デフォルトが emptyなので Must issue a STARTTLS command first.で失敗する。encryptではなく mayでも動くがこちらは TLS接続に失敗した時にプレーンテキストを使うようなので encryptにした。
Nov 16 08:12:56 debianpostfix/smtp[6109]: 991C44085B: to=foo@gmail.com, relay=smtp.gmail.com[74.125.204.108]:587, delay=0.65, delays=0.05/0.01/0.41/0.17, dsn=5.7.0, status=bounced (host smtp.gmail.com[74.125.204.108] said: 530 5.7.0 Must issue a STARTTLS command first. y6sm12524933pfm.12 - gsmtp (in reply to MAIL FROM command))
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.14.6
BuildVersion: 18G1012
$ xcode-select -p
/Applications/Xcode_10.3/Xcode.app/Contents/Developer
Terminal
curl -O https://github.com/ccache/ccache/releases/download/v3.7.6/ccache-3.7.6.tar.gz
tar xf ccache-3.7.6.tar.gz
cd ccache-3.7.6CFLAGS="-arch i386 -arch x86_64"\LDFLAGS="-arch i386 -arch x86_64"\
./configure --prefix=/usr/local--disable-man
make V=1
make install
pixivFANBOX にアップロード可能な形式で汎用性が高い形式は「ZIP」だと思います。ZIP には分割する機能があるのでこれを用いるのが簡単なのですが、分割された ZIP ファイルは最初のファイル以外はヘッダの違いからか pixiv 側で ZIP ファイルだと認められないことがあります（分割方法によります）。
set-eset-uPATH=/usr/bin:/bin
limit=$((10**6*300-1024))split_and_zip(){
split -b${limit}-a1"${1}""${1}".
for p in"${1}".?
do
zip -q-0-m-T"${p}".zip "${p}"done}for f
dobasename=$(basename "${f}")dirname=$(dirname "${f}")type=$(stat -f %T "${f}")cd"${dirname}"case${type}in
/)
zip -q-r-y"${basename}".zip "${basename}"
split_and_zip "${basename}".zip
;;'')
split_and_zip "${basename}";;esacdone
zipsplitコマンドに ZIP ファイルを渡すことで分割された ZIP ファイルを作成することもできます。このコマンドでは ZIP ファイルの中身を上手くやりくりして最大サイズに収まるように分けて個別の ZIP ファイルとして生成してくれるようです。この仕組の都合上、圧縮ファイル内に最大サイズを超えるファイルが存在する場合は ZIP を分割することは出来ません。また、2 GB を超えるファイルをサポートしていません。
