Le 15/02/2011 20:23, Alex a écrit : > Hi, > > I have a sender that is trying to send mail to one of our recipients, > but it is being rejected because it is a message/partial content type: > > /^Content-(Disposition|Type):\s+.*?message\/partial\b/ REJECT >
can you find out (and report) how the sender sent his email (mail client, ...) to see why he uses /partial? The goal is to see if /partial has a real use case. > I pulled this from the jimsun antispam page. Is this still necessary? > well. the problem with /partial is that it may cause problems with filters. how would you scan this for viruses? > If so, how would I go about creating an exception for this specific > sender? you can't create an exception in header_checks. you can create another smtpd listener and get the send use it (different recipient domain with diferent MX OR sender relay config using a specific smtpd OR ...). but really, it's better to provide an http/ftp upload method. smtp isn't good for large file exchange, because it's multi-relay with store-and-forward (with sync queue to dis) at each relay. even (suboptimal) http is better. > This file is defined in my mime_header_checks file. Perhaps I > can create an entry in my regular header checks file that exempts this > user from further checks? > > I guess this is really a question about the ordering of how the checks > are done and how to construct such a rule to authorize this user to > send otherwise unauthorized content. > > Thanks, > Alex
