On 2013-07-09 08:08, Benny Kurniawan C wrote: > Noted pak, dan untuk cara kerja email di ERP mereka seperti ini mail > message tidak terkirim secara langsung ke ERP SMTP server/service ke > Mail Server kami, tetapi emailnya harus routing dari Messagelabs ke > mail server kami. Jadi mereka tidak mau merubah pak dan kita harus > mengikuti yang mereka minta, apakah ada saran yang terbaik pak?
Jangan hanya "dicatat", tetapi "dilakukan":-) Kalau pakai MDaemon yang ada di tautan tadi maka bisa menggunakan content filter untuk mengubah return-path <address> atau direct delivery melalui peering connection tidak perlu lewat internet. Rincian setting lainnya misalkan saja seperti ini http://mdaemon.dutaint.co.id/13.5/index.html?domain_manager_host_name_ip.htm Domain name: erp.itochu.co.id atau erp.itochu.com SMTP host name: itcovsint.itochu.com http://mdaemon.dutaint.co.id/13.5/index.html?default_domain_and_servers_delivery.htm [x] Send all email directly first, and then to smart hosts if there are problems Default smart host: smtp.messagelabs.com [x] Use SMTP authentication User name: {sesuai yang diberikan messagelabs.com} Password: {sesuai akun diatas} http://mdaemon.dutaint.co.id/13.5/index.html?default_domain_and_servers_dns.htm klik "Edit MX cache file" dan isikan di baris kosong terbawah dari kolom paling kiri jkt.itochu.co.id 10 jkt.itochu.co.id klik Edit hosts file isikan di baris kosong terbawah dari kolom paling kiri 165.108.159.10 jkt.itochu.co.id Ubahan return-path itu tidak perlu smtpauth dan memastikan tidak bermasalah dengan pengiriman (delivery) mail. http://support.tigertech.net/return-path ---[mulai kutipan]--> Is the "Return-Path" the same as the "From" address on a message? One thing that often confuses people is the difference between the "Return-Path" address and the "From:" header address. These are two different things, and our servers only care about the Return-Path ("envelope sender"). Your script can set a "From:" address to be anything you want, although in practice they'll usually be the same. Why is this necessary? Our servers enforce the "Return-Path" rule for two main reasons, both of which make sure you don't have problems delivering mail. First of all, if you sent messages using other domain names, many receiving servers would think your messages were spam that "forged" someone else's address, particularly if the receiving mail server uses SPF. This makes sense if you think about it: for example, only AOL's servers should be sending mail from addresses that end in "@aol.com". Many servers will reject mail claiming to be from a certain address if the message isn't sent by a server that usually handles that address. The second reason is that it helps us minimize spam sent from our network. Occasionally, spammers try to take advantage of insecure software that customers have installed on our servers to send thousands of spam messages. When they do this, they almost always use forged "Return-Path" addresses. Our outgoing mail filters detect the invalid Return-Path and stop the mail before it leaves our network, making sure that other ISPs don't block our mail servers (and your legitimate mail). <--[akhir kutipan]--- -- syafril ------- Syafril Hermansyah MDaemon-L Moderators, running MDaemon 13.5.1 SecurityPlus 4.1.5 Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon. -- --[MDaemon-L]------------------------------------------------ Milis ini untuk Diskusi antar pengguna MDaemon Mail Server. Netiket: http://www.netmeister.org/news/learn2quote Arsip: http://mdaemon-l.dutaint.com Dokumentasi : http://mdaemon.dutaint.co.id Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com Versi terakhir MD 13.5.1, SP 4.1.5, BES 2.0.2, OC 2.3.2, SG 2.1.2, PP 2.0.1
