<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Arial; font-size: 10pt; color: #000000'>Hi<br><br>I think this looks great, and it would be fantastic to get it integrated into MailScanner code!<br><br>/Markus<br><br><hr id="zwchr"><div style="color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>Från: </b>"--[ UxBoD ]--" <uxbod@splatnix.net><br><b>Till: </b>"MailScanner discussion" <mailscanner@lists.mailscanner.info><br><b>Skickat: </b>tisdag, 18 okt 2011 19:15:46<br><b>Ämne: </b>Re: MailScanner and ZendTo Integration<br><br>Have made quite a large change to how the drop message appears in the email. If anybody would like to see it in action then please mail me offlist.<br>--<br>Thanks, Phil<br><br>----- Original Message -----<br>> Markus,<br>><br>> it looks like the pertinent code is within PFDiskStore.pm as that<br>> performs the re-queuing of the messages. It does appear to<br>> re-calculate the size so am surprised that it is not being written<br>> back.<br>><br>> Jules, this is a major issue for us so any help gratefully received.<br>> --<br>> Thanks, Phil<br>><br>> ----- Original Message -----<br>><br>> > Hi Phil,<br>><br>> > I did something similar awhile ago, and had problems with the<br>> > message<br>> > size parameter in Postifx.<br>><br>> > The size in the queue file written to the postfix queue is not<br>> > updated when attachments are stripped, this means that postifx will<br>> > report the old size to the next mailserver, even though the message<br>> > now is smaller. The fix I did for this was to modify the size<br>> > parameter in the MailScanner structure, and update that field in<br>> > the<br>> > queue file.<br>><br>> > I was lazy however, and my fix is approximate (good enough for me),<br>> > and should probably be improved to be exact.<br>><br>> > http://lists.mailscanner.info/pipermail/mailscanner/2010-March/095339.html<br>><br>> > Great work!<br>><br>> > /Markus<br>><br>> > ----- Original Message -----<br>><br>> > Från: "--[ UxBoD ]--" <uxbod@splatnix.net><br>> > Till: "ZendTo Users" <zendto@zend.to>,<br>> > mailscanner@lists.mailscanner.info<br>> > Skickat: torsdag, 13 okt 2011 11:39:36<br>> > Ämne: MailScanner and ZendTo Integration<br>><br>> > Just a quick follow up as I have now integrated MailScanner with<br>> > ZendTo. I am in the process of taking the latest versions of the<br>> > two<br>> > packages, applying my changes, and then producing diffs for Jules<br>> > to<br>> > review. The new options, if my changes are accepted, in MailScanner<br>> > will be:<br>><br>> > ZendTo Integration = %rules-dir%/zend.to.rules<br>> > ZendTo URL = https://www.somedomain.com/dropoff.php<br>> > ZendTo Access Key = 123456789ABCDEFGHI<br>> > ZendTo Min Message Size = -1<br>> > ZendTo Min Attachment Size = -1<br>> > ZendTo Strip All = yes<br>><br>> > Hopefully they are all explanatory and I have attempted to make it<br>> > as<br>> > configurable as possible. If an email matches the<br>> > message/attachment<br>> > size criteria it is passed of to the ZendTo URL. That will verify<br>> > the access key against the ZendTo configuration and if all okay it<br>> > will accept the attachments for processing. If a drop-off ClaimID<br>> > is<br>> > created then that will be returned to MailScanner where an HTML<br>> > in-line attachment will be added to the original message and all<br>> > attachments process by ZendTo will be removed. The result will<br>> > either be the following text appearing in-line or as a html<br>> > attachment with the name <claimid>.html.<br>><br>> > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>> > This first paragraph is an automatic message from our email system.<br>> > The original attachments were too large to safely send via email.<br>> > They have been removed to a separate server, and replaced with the<br>> > attached link, from where the originals may be downloaded via your<br>> > web browser.<br>><br>> > https://www.somedomain.com/pickup.php?claimID=12345678&claimPasscode=ABCDEFG<br>><br>> > This file will expire on 26 October 2011 12:09:54 PM.<br>> > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------<br>><br>> > The message is driven from a ZendTo template so easily<br>> > configurable.<br>> > If for any reason the message cannot be processed ie. files to big<br>> > then an NDR will be sent back to the sender. Again that message is<br>> > templated.<br>> > --<br>> > Thanks, Phil<br>><br>> > ----- Original Message -----<br>> > > It's possible, yes. But I don't have any immediate plans to do<br>> > > so,<br>> > > I'm<br>> > > afraid.<br>> > ><br>> > > I'm trying to keep ZendTo as simple as possible while doing what<br>> > > most<br>> > > people need it to.<br>> > ><br>> > > Jules.<br>> > ><br>> > > On 06/06/2011 16:29, --[ UxBoD ]-- wrote:<br>> > > > Hi Jules,<br>> > > ><br>> > > > How possible do you think it would be to integrate the two<br>> > > > products? When a user sends an email, with an attachment,<br>> > > > MailScanner would replace it with a ZendTo link and remove the<br>> > > > attachment.<br>> > ><br>> > > Jules<br>> > ><br>> > > --<br>> > > Julian Field MEng CITP CEng<br>> > > www.Zend.To<br>> > ><br>> > > Follow me at twitter.com/JulesFM<br>> > > PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654<br>> > ><br>> > > 'All programs have a desire to be useful' - Tron, 1982<br>> > ><br>> > > _______________________________________________<br>> > > ZendTo mailing list<br>> > > ZendTo@zend.to<br>> > > http://mailman.ecs.soton.ac.uk/mailman/listinfo/zendto<br>> > ><br>> > --<br>> > MailScanner mailing list<br>> > mailscanner@lists.mailscanner.info<br>> > http://lists.mailscanner.info/mailman/listinfo/mailscanner<br>><br>> > Before posting, read http://wiki.mailscanner.info/posting<br>><br>> > Support MailScanner development - buy the book off the website!<br>><br>> > --<br>> > MailScanner mailing list<br>> > mailscanner@lists.mailscanner.info<br>> > http://lists.mailscanner.info/mailman/listinfo/mailscanner<br>><br>> > Before posting, read http://wiki.mailscanner.info/posting<br>><br>> > Support MailScanner development - buy the book off the website!<br>> --<br>> MailScanner mailing list<br>> mailscanner@lists.mailscanner.info<br>> http://lists.mailscanner.info/mailman/listinfo/mailscanner<br>><br>> Before posting, read http://wiki.mailscanner.info/posting<br>><br>> Support MailScanner development - buy the book off the website!<br>><br>--<br>MailScanner mailing list<br>mailscanner@lists.mailscanner.info<br>http://lists.mailscanner.info/mailman/listinfo/mailscanner<br><br>Before posting, read http://wiki.mailscanner.info/posting<br><br>Support MailScanner development - buy the book off the website!<br><br></div><br></div></body></html>