"Bo Berglund" <bo.berglund@telia.com> wrote in message
news:phdo52hjms5ev3l952hsjtq56kur2f5b1k@4ax.com...
> Problem is that the destination company has an incoming inspection
> policy that forbids encrypted files! It requires all attachments to be
> valid and open so it can inspect them inbound. So even if I found one
> way to get around the stupid outbound filter that solution is stopped
> in the other end....
Sounds like you are out of luck then. You will just have to warn your users
about the restrictions that the ISPs are imposing on your system, and tell
them not to use such restrictive services. The alternative is to not email
the files to begin with. Put them online somewhere that the user can
download them instead.
> How else?
Making your own server won't solve your problem. It will only cause more
problems, for the reasons I already stated. If you can't get around the
restrictions using standard email clients, then you will just have to write
your own client so that you have full access to customize the email content.
But then, if the servers are analyzing the content anyway, then no amount of
tweaking the headers is going to get around that. You may have to write
your own receiving software as well as your own sending software, so that
you have full control of the messages on both ends.
> I downloaded an SMTP application from "SoftStack" called
> "Advanced SMTP server" and tested it. It did get past the ISP:s
> outbound filter and reached my test destinations (myself at various
> mail accounts).
Did it go through your ISP's server, though? Or did it try to connect to
each recipient's SMTP server(s) directly? If connecting directly, then you
are going to run into increasing connection problems down the line, if you
are not already.
Gambit
