Question on attachment striping  and url replacing Hi to all,
there are any tools that implements attachment striping  and url 
replacing in postfix as described below:

Observation:
Users have no concept of email file attachment size limits or bandwidth 
usage.

Observation:
Users are unwilling to learn to do something new unless it is faster or 
easier than their current methods.

Proposal:
Strip email attachments at the SMTP server and insert an FTP/HTTP link.

Setting:
Mail server on site.
User David
Company Fluffy Bunny Amalgamated
Domain fluffybunny.com
User email xlicq@fluffybunny.com 

Scene:
David creates an email to his good friends Carl, Billy and Larry.
Davidâs three friends work at Happy Squirrel Enterprises
Carl receives email as epre@happysquirrel.com 
.
Bill receives email as hmspj@happysquirrel.com 
.
Larry receives email as ykyvx@happysquirrel.com 
.
David attaches a 15MB file to his very work-related email.
The name of the attachment is naughty.wmv.
David sends the email.

In a traditional SMTP environment there are two things that would 
possibly occur.
1. The email is delivered to each of the three recipients generating 
45MB of outbound email at one moment.
2. The email is bounced to David indicating the attachment is too large 
and David is now confused and there is a potential that it generated an 
even larger load if the attachment remains on the inbound message.

Programming to the rescue:
When the outgoing mail hits Davidâs SMTP server it is checked for file 
attachments.
If there is an attachment and it is greater than some threshold the 
attachment is removed.
The server creates a directory with a randomly generated name and places 
that folder in a publicly accessible location (FTP/HTTP). It puts the 
attachment in that read-only folder. It password protects the folder. 
After a period of time (hours, days, weeks, etc) it expunges the folder 
and its contents.

The outgoing email would continue to its destination but without the 
attachment. Instead, the email would contain a link, username and 
password such as:

ftp://ftp.fluffybunny.com/ldic$4239/naughty.wmv
Username: david (derived from sender email or generated if desired)
Password: 918dfkfJ4 (generated)

Include a second link with the path embedded such as:

ftp://david: 816afgtx9@ftp.fluffybunny.com 
/ ldic$4239/naughty.wmv

Include a text string in the email body telling the recipient how to get 
his file.

Result:
Users donât have to learn to do anything.
Immediate reduction in SMTP traffic by 45MB in this example.
Future FTP/HTTP traffic for each user likely to occur non-concurrently 
smoothing out demand cycles.
Possibility to incorporate Bittorrent technology for file distribution.
Recipient email filters are less likely to reject the mail based on size 
limits.
Failed/rejected email will not generate inbound and outbound load.
Mobile users will not be delayed with large attachments over unreliable 
connections.

Perform the same procedure as above for an on-site POP3 server so that 
all inbound mail is processed before delivery.

Can this be done in Postfix as it sits or do I need to hire a 
programmer? Know any good programmers?


