Hi sanuri and others who follow this thread,
On Wed, 25 Apr 2001 at 09:11:15 GMT +0700 (25/04/2001 9:11 where you
think I live) "sanuri"=[s] told to the list :
>> Dalam hal parsing addressnya salah, errornya adalah "parsing error"
>> (bukan failure notice...ini bukan default errornya Mdaemon, kecuali
>> jika sudah di customize oleh postmasternya, tp saya meragukan hal
>> itu).
s> Kalau salah parsing setahu saya masuk direktori bad message.
Dan copy ke postmaster (ke-2 nya hanya jika dikehendaki).
s> Di sini mungkin bukan salah parsing. Tapi proses parsing
s> menempatkan email pada kategori remote recipient. Ini saya quote
s> dokumentasi DomainPOP.
s> "This feature works by using the POP protocol to download all the
s> mail found in the ISP�s POP mailbox associated with the specified
s> logon. Once collected, the messages are parsed according to the
s> settings provided on this dialog and then placed in user mailboxes
s> or the remote mail queue for MDaemon to deliver, just as if the
s> messages had arrived at the server using conventional SMTP
s> transactions."
s> - Ada istilah JUST AS IF
s> - Ada kalimat OR THE REMOTE MAIL QUEUE ...
s> Kalau langsung ditempatkan ke remote mail queue kan artinya tidak
s> melewati ketentuan relay, bukannya pemeriksaan hak relay terjadi
s> saat transaksi SMTP (sebelum message benar-benar diterima server)?
Ya dan tidak.
Saat DomainPOP engine download mail, dia belum melakukan parsing dll,
baru saat message di parsing oleh SMTP Service dilakukan parsing (plus
semua restriction yg diset, termasuk Anti Relay), saat itu SMTP
service berlaku sama halnya dg SMTP di full online connection.
s> Memang kalau tidak bisa ditempatkan ke salah satu mailbox lokal
s> bukan berarti otomatis masuk remote queue.
Tidak harus.
s> Mungkin tergantung setting. Ini saya quote lagi.
s> "When MDaemon downloads a message from a remote POP source it
s> immediately parses all the relevant headers within that message and
s> builds a collection of potential recipients. Every email address
s> found in the headers that MDaemon inspects is included in the
s> collection. Once this process is complete, MDaemon�s collection of
s> recipients is divided into local and remote sets. Further, all
s> addresses that are parsed and placed into the collection of
s> potential recipients are processed through the Address Alias
s> translator before being divided into local and remote sets. Every
s> member of the local set (addresses with a domain that matches
s> either MDaemon�s Primary domain or one of the Secondary domains)
s> will receive a copy of the message.
s> WHAT HAPPENS TO THE REMOTE SET is governed by the settings in this
s> dialog. You can elect to simply ignore these addresses, forward a
s> summary listing of them to the postmaster, OR HONOR THEM�in which
s> case MDaemon will actually deliver a copy of the message to the
s> remote recipient. Only under rare circumstances would the need to
s> deliver these messages to remote recipients be warranted."
s> Jadi dugaan saya, kasus ini secara tidak sengaja masuk _rare
s> circumstances_ ini, karena meng-HONOR message dari milis yang
s> karena kharakter email dari milis menyebabkan dia dikategorikan
s> remore recipient.
Tidak. Jika itu yg terjadi, maka tetap saja postmaster akan terima
"unknown user error".
s> Mengenai kemungkinan looping mail ini dokumentasi mengatakan.
s> "Care must be taken to prevent duplicate messages or endlessly
s> looping mail delivery cycles. A common problem that results from
s> the loss of the SMTP envelope manifests itself with mailing list
s> mail. Typically, messages distributed by a mailing list do not
s> contain within the message body any reference to the addresses of
s> the recipients. Rather, the list engine simply inserts the name of
s> the mailing list into the TO: field. This presents an immediate
s> problem: if the TO: field contains the name of the mailing list
s> then the potential exists for MDaemon to download this message,
s> parse the TO: field (which will yield the name of the mailing
s> list), and then dispatch the message right back to the same list.
s> This would in turn deliver another copy of the same message back to
s> the POP mailbox from which MDaemon downloaded the original
s> message�thus starting the whole cycle over again. To cope with such
s> problems mail administrators must take care to use the tools and
s> settings that MDaemon provides to either delete mailing list mail
s> or perhaps alias it in such a way that it will be delivered to the
s> proper local recipient(s). You could also utilize the Routing Rules
s> or Content Filters to deliver the message to the correct
s> recipient(s)."
s> Paragraf di atas tidak menyebut relaying security system untuk
s> menghindari looping. Tapi alias, routing rules dan filter.
Memang, karena Anda seharusnya mencari dibagian Relaying :-)
s> Dalam kasus ini kan looping tidak sampai terjadi seperti ilustrasi
s> di atas, karena qmail di pau-mikro bisa mencegah looping dari
s> deteksi header mail.
Dalam kasus Open Relay, yg terjadi biasanya bukan hanya looping
(looping terjadi jika dan hanya jika utk mailing list), akan tetapi
message duplicate untuk si recipient.
BTW. Bisa test kok (kalau mau) kirim mail ke someone@@lp3ipg.net dg
cc: atau to: ke banyak address, maka other address (yg ada di TO: atau
CC:) akan menerima duplicate message (message double), satu dari Anda
dan yg lain dari MDaemonnya lp3ipg.net :-)
--
Salam,
- Syafril - mailto:<[EMAIL PROTECTED]>
[List Owner/Moderator of [EMAIL PROTECTED] ]
Dibuat : Rabu 25 April 2001, 11:13:02 GMT +0700
Saya menggunakan MDaemon 4.0.0 Publish di W2K SP1
--
--MDaemon-L----------------------------------------------------------
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.
Untuk menghubungi moderator/List Owner double click link dibawah ini:
<mailto:[EMAIL PROTECTED]>
Untuk Unsubscribe, double click link dibawah ini langsung kirim
<mailto:[EMAIL PROTECTED]>
Untuk Subscribe, double click link dibawah ini langsung kirim
<mailto:[EMAIL PROTECTED]>
--POWERED BY MDAEMON!------------------------------------------------
Anda terdaftar di List ini dg alamat : [email protected]
