Re: Email Footer
On Wednesday 14 February 2001 1:19 pm, Andrew McMorris wrote: Hi could someone please point me in the right direction for information on how to add a footer to all emails that our company send please. In our organisation all inbound and outbound SMTP traffic is routed through a NT server running MIMESweeper. This has the ability to add footers to outbound email. (As you'll see below when this gets to you...) It also runs some basic content filtering checks, and checks all mail that passes through it with Sophos Anti-virus. I'm told that it works reliably and rarely has any problems. I used to have a patch to qmail that inserted footers onto the end of every mail. However, it didn't work with mail containing MIME attachments. As I didn't think my limited C hacking skills would get this working reliably, we stuck with the MIMESweeper solution. I am also interested in not having the footer for emails sent to our own company can anyone please point me in the right way. The MUAs we use are configured to use our main mail server for SMTP and POP. qmail then handles any SMTP routing. Internal mail is handled locally by the mail server, with outbound mail routed through the NT server. This lets us get away with not having the disclaimer stamped on internal mail. (Of course, it also means that internal mail is not virus checked. We're looking into using Amavis to do this.) Hope this helps. -- Andrew Bold Unix Systems Administrator -- This message is confidential. It may also be legally privileged. It is intended solely for the stated addressee(s) and access to it by anyone else is unauthorised. If you have received this message in error, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this message. Such unauthorised use may be unlawful. If you have received this message in error, please delete it immediately and advise us by return e-mail to the above address.
Re: Email Footer [slightly OT]
Excellent - my first flame from Mr. Socha. I suddenly feel privileged. Apologies to everyone else for the spam. This is the first and last time I will reply to anything like this. On Wednesday 14 February 2001 2:24 pm, you wrote: Well, great. So you're acutally sending the following to public mailing lists? I'm sorry I have to ask but what does braindamaged translate to in your language? In my language, "acutally" is spelled "actually", and "braindamaged" is actually "brain damaged". Your comments speak for themselves. I feel sad that I have to correct you on simple spelling issues. This message is confidential. It may also be legally privileged. It is intended solely for the stated addressee(s) and access to it by anyone else is unauthorised. [blablabla] 8 lines of nothing. "legally privileged", huh? More like "intellectually differently abled". If I could remove the footer, I would. However this is out of my control and is a requirement of our internal audit department. Not a lot I can do about it. Sorry. "Reliable" and "rarely" don't mix well in a binary world. I know. Why do you think I run Unix boxes instead of NT? As I said before, the box is out of my control. (Maybe the expression "I'm told that..." was a little too vague for you...) Sure, I could set up my own little mail server to bypass the NT box, but I like having a job to get up for in the morning. Welcome to Unix, Andrew - our tools either work, or they don't. Thanks. About 15 years too late for the welcome, but thanks anyway. I've been doing this for a while Exchange *does* *not* *work* and neither does NT. Tell me something I don't know, then you might be able to contribute something useful instead of just fanning the flames. Your solution is not a solution. It is a system that works for us, and that is all that I was trying to say. It's a viable way of creating a security hole the size of Redmond. If I had a choice, all the NT boxes would be dropped off the edge of the nearest cliff. Go away. No. Unix Systems Administrator You wish, mouse pusher. Minix, Xenix, Linux, Risc/OS, SCO UnixWare, ICL DRS/NX, Solaris 2.x/7/8, AIX. All versions of Unix I've administered over the last 15 years. Replies such as the one Robin has posted do nothing to help the image of qmail or open source products in general. Let's try and keep it to the point and keep the flames down. Maybe some people who are usually the first to cry "netiquette" should go and look up the term themselves. Again, sorry to all for feeding to the flame. Apologies for wasting your bandwidth. -- Andrew Bold Unix Systems Administrator -- This message is confidential. It may also be legally privileged. It is intended solely for the stated addressee(s) and access to it by anyone else is unauthorised. If you have received this message in error, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this message. Such unauthorised use may be unlawful. If you have received this message in error, please delete it immediately and advise us by return e-mail to the above address.
Re: HTML Emails Garbled when sent with qmail+ezmlm
On Monday 12 February 2001 4:05 pm, Jeremy Suo-Anttila wrote: I have been having a problem with HTML based emails getting garlbled when i send them out via qmail+ezmlm-idx Neither qmail nor ezmlm will be touching the content of your message. The problem is more likely to be with the end user's mail client. However, looking at some of the error messages you quoted, you really need to get moved across to the new server. There is a *very small* possibility that system problems are messing with the mail files in memory as they are being processed. The main problem, though, is that you are sending HTML mail. E-mail is a medium used for transmitting textual information, and you are using it as a layout medium. E-mail isn't print. If you want to send out a formatted newsletter, hire a print bureaux... Why don't you consider sending the mail as a plain text summary, with a link to the web page detailed within it? Most modern GUI based web clients will grep http references out of a text based mail and convert them to a clickable link to make it easy for the end users... (I'm guessing that the majority use Outlook/Outlook Express, and they need all the help they can get ;^) I think this may be a better long term solution. Just my 0.02. -- Andrew Bold Unix Systems Administrator [EMAIL PROTECTED] -- This message is confidential. It may also be legally privileged. It is intended solely for the stated addressee(s) and access to it by anyone else is unauthorised. If you have received this message in error, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this message. Such unauthorised use may be unlawful. If you have received this message in error, please delete it immediately and advise us by return e-mail to the above address.
Re: How to remove a email from a mailbox
On Thursday 18 January 2001 05:34, you wrote: it will delete the rest of the emails after the attachemetn, if the attachement is in some part between the mailbox? Are you using Maildir format mailboxes? Or /var/spool/mail? I think the assumption has been made that you are using Maildir. It sounds to me like you have just the one mbox format file that contains somewhere within it the offending email. The "best" solution I can think of, that doesn't require a text editor that needs lot of RAM or temporary disk space, is to actually load the file your mail program. For example, run "mail" or "mailx" and use the option to specify a mail file to open. eg, "mail -f /var/spool/mail/username" Best done as root or the actual owner of the mailbox. Any other user will not have the required permissions for saving the file. The next step is to sit back and wait while your chosen program loads the 12Mb+ mbox file Next, identify the problem message and delete it, then exit the mail program. Finally, convert all of your mail users to Maildir format, as this is much more robust and would have made this while process as simple as this: cd ~username/Maildir/new ls -l identify big mail message rm big mail message Hope this helps. -- Andrew Bold Unix Systems Administrator [EMAIL PROTECTED] -- This message is confidential. It may also be legally privileged. It is intended solely for the stated addressee(s) and access to it by anyone else is unauthorised. If you have received this message in error, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this message. Such unauthorised use may be unlawful. If you have received this message in error, please delete it immediately and advise us by return e-mail to the above address.
Re: remote mail server
On Thursday 18 January 2001 08:00, Raymond Orchison wrote: How do I set the remote server up to forward all smtp traffic to the main mail server? On the remote server, create an smtproutes file: echo ":main.mail.server.fqdn" /var/qmail/control/smtproutes This will cause the remote mail server to forward all SMTP mail the the main mail server. Hope this helps. Andy -- Andrew Bold Unix Systems Administrator [EMAIL PROTECTED] -- This message is confidential. It may also be legally privileged. It is intended solely for the stated addressee(s) and access to it by anyone else is unauthorised. If you have received this message in error, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this message. Such unauthorised use may be unlawful. If you have received this message in error, please delete it immediately and advise us by return e-mail to the above address.
Re: qmail list reply-to
On Tuesday 16 January 2001 13:04, you wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* Please check your system I have recieved this attachment "Emanuel.exe" from your addres six times It contains the "win32.Navidad.b" virus thanks I was just about to send the same warning when your mail arrived via the list. It's a good job we all use "mutt" and *nix OSes isn't it? ;^) -- Andrew Bold Unix Systems Administrator [EMAIL PROTECTED] -- This message is confidential. It may also be legally privileged. It is intended solely for the stated addressee(s) and access to it by anyone else is unauthorised. If you have received this message in error, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this message. Such unauthorised use may be unlawful. If you have received this message in error, please delete it immediately and advise us by return e-mail to the above address.
