| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
> > On Nov 16, 2007, at 9:19 AM, Noel Jones wrote: > >> Cengiz Vural wrote: >>> On Nov 15, 2007, at 1:33 PM, Noel Jones wrote: >>>> Cengiz Vural wrote: >>> Nov 15 15:52:58 mail postfix/smtpd[5598]: NOQUEUE: reject: RCPT from >>> ironman.mail.utexas.edu[128.83.32.51]: 553 5.7.1 >>> <_user <mailto:vuralc>>: Sender address >>> rejected: not logged in; from=<_user >>> <mailto:vuralc>> to=<_user >>> <mailto:vuralc>> proto=ESMTP >>> helo=<ironman.mail.utexas.edu> >> >> You've specified reject_sender_login_mismatch in your main.cf, and the >> mail claims to be from a local user that is not logged in. So postfix >> rejects the mail. > > What does that have anything to do with reject_sender_login_mismatch? > Nobody is trying to send an email without login in! An email is being > forwarded from @mail2.edu to @mail1.edu. To be forwarded, a message must be sent. >Why would a forwarding server need to login? postfix does what you configure it to do. if you require login for senders (via reject_sender_login_mismatch or so), it will require it. if you don't, it won't. For more help, please show complete complete output of 'postconf -n'. >> >> Maybe you need to whitelist 128.83.32.51 or stop using >> reject_sender_login_mismatch, depending on what you want to accomplish. > > You are not seriously suggesting that I should whitelist every email > server that my users may forward from! > remove reject_sender_login_mismatch. if your goal is to enforce this for inbound mail only, then use a check_client_access to return the check only for your networks. better yet, setup a submission service (port 587) and use it for mail submission. This may or may not be simple, depending on the size and skills of your user base...
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
© 2004-2008 readlist.com