sendmail に特化した話ではないのですが、 MTA 総合スレッドが見つからなかったのでここに書き込みさせてください。
RFC2822では Message-ID の満たす要件として、
The message identifier (msg-id) itself MUST be a globally unique identifier for a message. The generator of the message identifier MUST guarantee that the msg-id is unique.
>>595 蛇足だとはおもいますが、RFC 2822 から該当箇所を引用しておきます。 There are several algorithms that can be used to accomplish this. Since the msg-id has a similar syntax to angle-addr (identical except that comments and folding white space are not allowed), a good method is to put the domain name (or a domain literal IP address) of the host on which the message identifier was created on the right hand side of the "@", and put a combination of the current absolute date and time along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number) on the left hand side. Using a date on the left hand side and a domain name or domain literal on the right hand side makes it possible to guarantee uniqueness since no two hosts use the same domain name or IP address at the same time. Though other algorithms will work, it is RECOMMENDED that the right hand side contain some domain identifier (either of the host itself or otherwise) such that the generator of the message identifier can guarantee the uniqueness of the left hand side within the scope of that domain.
virtusertableを使ってバーチャルドメイン管理してますが 一部のドメインだけ pop before smtp にする、 なんて事できますか？ xxxx@ssss.jp はユーザー名チェックだけでSMTP利用可能 xxxx@bbbb.jp は pop before smtp でないとSMTP利用できない みたいなの
sendmail-8.12.5使用してphp4.2.3からメール送信しています。 すると、最初のReceivedにapache@localhostというのが付いて しまいますが、これをwebmaster@my_domain.jpのようにする ことはできないでしょうか。あと、fオプション付けてメール送信すると、 X-Authentication-Warning: www.my_domain.jp: apache set sender to webmaster@my_domain.jp using -f というものがヘッダに付いてしまいます。/etc/mail/trusted-users にはちゃんとapacheを登録してあるんだけどどうしてでしょう？
This vulnerability is message-oriented as opposed to connection-oriented. That means that the vulnerability is triggered by the contents of a specially-crafted email message rather than by lower-level network traffic. This is important because an MTA that does not contain the vulnerability will pass the malicious message along to other MTAs that may be protected at the network level. In other words, vulnerable sendmail servers on the interior of a network are still at risk, even if the site's border MTA uses software other than sendmail. Also, messages capable of exploiting this vulnerability may pass undetected through many common packet filters or firewalls.