[xmail] Re: Resend (mess/rsnd) list CTRL commands ...
Hello Davide, Tuesday, November 7, 2006, 1:35:50 AM, you wrote: How badly would be needed the ability to list in flight messages, with the ability to schedule now them? Kind of like a requeue? It would be nice, but so far I have lived without it... This coming from a die hard postfix user... :) Where you have to configure which domains you can requeue, or only requeue everything. (Not a good idea at 2 messages in the queue...) -- Best regards, Jornmailto:[EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Resend (mess/rsnd) list CTRL commands ...
I would agree that I would much rather wait than have Davide Burnout. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tracy Sent: Monday, November 06, 2006 20:04 To: xmail@xmailserver.org Subject: [xmail] Re: Resend (mess/rsnd) list CTRL commands ... I'd call it nice to have, rather than necessary. If it rides another version, I won't cry. Much...:) Davide Libenzi wrote: On Mon, 6 Nov 2006, Norbert Doeberlein wrote: Yes, I think that is very valuable! And please give Harald enough info so he can update XQM. ;-) Hmmm, ... this would require a quite substantial restructuring of the queue locking policies, and I'm currently thinking if to drop it, do it in 1.23, or keep it on hold till 1.24. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Copying messages
Em Segunda 06 Novembro 2006 20:12, Davide Libenzi escreveu: Then *every* message of a given user would be fed back to the mailing list. Not good. Just use the mailing list reply-to and ask the support dudes to do a reply-to-all when answering. Why *not good* if replying to the mailing list would be the same? How I said, support people can forget to reply to the mailing list and customers aren't members of that mailing list, so we're back to the main question: how to force XMail make a copy of messages being relayed by an user? Thanks, Helio - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Copying messages
Hello Helio, Tuesday, November 7, 2006, 2:16:46 PM, you wrote: Em Segunda 06 Novembro 2006 20:12, Davide Libenzi escreveu: Then *every* message of a given user would be fed back to the mailing list. Not good. Just use the mailing list reply-to and ask the support dudes to do a reply-to-all when answering. Why *not good* if replying to the mailing list would be the same? How I said, support people can forget to reply to the mailing list and customers aren't members of that mailing list, so we're back to the main question: how to force XMail make a copy of messages being relayed by an user? Not good, because PRIVATE mail from those users will also go back to the mailing list. This is not a functionality of any mail server, and no MTA will, or for that matter, should, ever do that, as it constitutes interception of email. You need to look at alternatives, like using a proper ticketing system for these type of things, which keeps record of activities and is auditable. Anybody looking at a ticket, will immediately see any previous activity and/or correspondence. It also understands the concept of owners to enable processes to be managed properly. You are expecting an MTA to do what a ticketing system is supposed to do, and what you cannot get into your users to do automatically. If you need a ticketing system, have a look at the RT system, which is free. URL is: http://bestpractical.com/rt. -- Best regards, Jornmailto:[EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Copying messages
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Helio Cavichiolo Jr Envoyé : lundi 6 novembre 2006 22:53 À : xmail@xmailserver.org Objet : [xmail] Re: Copying messages Em Segunda 06 Novembro 2006 18:08, Davide Libenzi escreveu: Ask CIA. This outta be documented somewhere in the Patriot Act ;) Seriously, a mailproc.tab with a redirect+mailbox should work just fine. Well, can I have a copy of relayed messages from a certain XMail user with this? I have a maillist called [EMAIL PROTECTED] All members are supposed to be of support staff who can answer support messages. Unfortunatelly support staff often forget to copy their answers back to [EMAIL PROTECTED], so everyone can see his/her answer, preventing double answers to customers. I was not planning to spy my secretary messages... at least it wasn't in my mind some minutes ago... :-) - If the 'support' response is made with '[EMAIL PROTECTED]' as the sender, you can create a filter that will catch up the [EMAIL PROTECTED] response mail then, after testing that '[EMAIL PROTECTED]' is not a destination (to avoid double post), will rewrite the mail and localy send it to xmail. Note that doing this, ANY mail send by [EMAIL PROTECTED] will go back to [EMAIL PROTECTED] . In case responses are not allways from [EMAIL PROTECTED], you will need to keep track of mails originaly send to [EMAIL PROTECTED] to filter any outgoing mails that correspond to the original mail (subject check, or special flag set by responder, ...) then do the same job as above. Complicated task as responder need not touch the subject or must add the 'special flag' (and it's really easy to omit to add the 'flag' as omit to clic on 'reply to all' or to not touch the subject ...) Note that some MUA have the possibility to automaticaly add a Cc or Bcc on any send mail (or some mails depending on folder or rules) Or with servers like Exchange or Notes (or some other ?), you can create 'recipient folders' with special macros/scripts on any message posted (so for example, on any response to a mail in the folder the system launch a script that can add/change the response) Same can also be done with xmail and filters (think about cmdalias). (For example, the cmdalias script could in fact write the mail in a database for a 'customer support web application', then supporters not directly use they mua but the app to reply, and the app software place the anwser in the database + send the mail to the original sender) Francis - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: 1.23-pre10 ...
On 6 Nov 2006, at 12:05, Davide Libenzi wrote: At this point, I really can't think of any reason why we shouldn't have a pre11 too :) Well I'm happy with 1.22 although last week had internet connection problems and for first time a requeue function would have been welcome. As it was I just rm'ed the one email that I needed to get out straight away from the queue and resend. Problem seemed to be that any load on outgoing traffic dropped the adsl connection so number in queue just built up. Whatever the problem was seemed to have been cleared ok as resend went straight through rather than after several hours. Remainder went on their next retry times. I've not been able to compile for NetBSD 3.1 same as with 3,0 but this time it's not just the new statvfs that replaces statfs but another error comes up afterwards. SysDepBSD.cpp: In function 'int SysNextFile(long unsigned int, char*)': SysDepBSD.cpp:2008:error: 'struct FileFindData' has no member named 'DE' It's too long ago since I compiled 1.22 that I can't remember if this came up but a diff of that SysDepBSD.cpp and my NetBSD one only picks up the couple of lines changed to statvfs. I think the possible out of memory error I had with 3.0 and on is still there in 3.1 but the crude fix of limiting number of connections by only allowing two of spamd or fprot filters to run has meant I've not had any further issue. I'll look at this futher if I get time but more likely for when you're starting on 1.24. David - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: GLST
On Mon, 6 Nov 2006, [EMAIL PROTECTED] wrote: I was looking for the changelog for glst - but most of the links in the glst documentation are dead, and I couldnt find a changelog anyway. It was a temp error I think. They work just fine now. Can anyone tell me what was changed from .23 to .24? Parsing of the REMOTEADDR and LOCALADDR [IP]:PORT format has been added. - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] 1.23-pre11 ...
Ok, I'll let this sit for a while before releasing 1.23 final:
http://www.xmailserver.org/xmail-1.23-pre11.tar.gz
http://www.xmailserver.org/xmail-1.23-pre11.win32bin.zip
I decided to hold the active queue handling to next releases.
ChangeLog:
- Changed the filter log to include the full exec string (separated by
semicolon).
- Fix CTRL poplnkadd and poplnkdel to accept local domains strings
starting with special characters.
- Added (finally!) a command line makefile (Makefile.win) to build the
whole XMail package without the usage of the MS VC++ IDE.
- Reject a CTRL domainadd command if an alias domain already exists with
the same name.
- Changed the CTRL usergetmproc command to allow the caller to specify
if it is the user or the domain one that is wanted. Or a merges of both,
if DU is specified in the optional 3th parameter.
- Changed the CTRL usersetmproc command to allow the caller to specify
if it is the user ('U') or the domain ('D') one that is wanted to be
set.
- Added complex/multiple macro substitution capabilities to external
programs argoument lists.
- Added strictier SMTP address validation.
- Check the mailbox size for every message coming into the mailbox (before
it was only done during the SMTP phase).
- Do not try to send to the 'A' record if the recipient domain does not
exist at all (NXDOMAIN). Bounce immediately instead, avoiding lengthy
retry policies.
- Added the wlex flag to filter lines (works for the SMTP ones only), to
exclude execution of the filter line in case the client IP is
white-listed inside the ipprop file.
- Added the post-RCPT SMTP filter, that is called before XMail acks the
client recipient. A new RCPT=EFILTER long entry is emitted in case a
recipient is rejected by a filter.
- Added @@CRCPT (current recipient) and @@FROM (sender email address)
macros to SMTP filter substitution.
- Allow cmdaliases to work on aliased domains. Before a cmdalias defined
on an alias-target domain was not working before the cmdalias check was
done before the alias domain resolution.
- Added the ability to bypass the SMTP.IPMAP.TAB inclusion using SMTP
authentication.
- Added a new SERVER.TAB variable SMTP-IpMapDropCode to control the drop
code to be used for IPs listed inside the SMTP.IPMAP.TAB. Like other
codes inside XMail, 1 means drop now, 0 means allow if auth, and -N
means add N seconds delay. An immediate drop will emit a SNDRIP=EIPBAN
log entry.
- Added a new SERVER.TAB variable SmtpMsgIPBan to control the SMTP
message returned in case of SMTP.IPMAP.TAB inclusion.
- Added log message when the maximum number of SMTP/POP3/CTRL threads is
hit.
- Fixed documentation about the spool info line and the SMTP filters info
line.
- Fixed a build problem on OpenBSD related to the lack of c_r (reentrant C
library) library.
- Fixed greetings message to be RFC2821 compliant (server host must be
first).
- Fixed a NAME_MAX build error ond *BSD and Solaris.
- Added a Pop3ScanCur USER.TAB variable to control the scan of the
Maildir's cur directory during POP3 message list build. Now XMail only
scans the new directory as default.
Test reports are, as usual, welcome ...
- Davide
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]
[xmail] Re: Copying messages
Em Terça 07 Novembro 2006 11:24, Jorn Hass escreveu: If you need a ticketing system, have a look at the RT system, which is free. URL is: http://bestpractical.com/rt. Thank you Jorn, I'm trying to install RT. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: Copying messages
Em Terça 07 Novembro 2006 16:11, John Kielkopf escreveu:
I have some users from the financial sector that are required to forward
all mail sent from and received on certain email accounts to a
regulatory service that checks their mail for regulatory compliance.
Probably a similar situation to what your looking to do.
If you're doing this under windows, you'll need to write a filter to
accomplish this, else you can look at what I use below for one of our
linux xmail servers.
For capturing the mail going out, I set a filter in filters.out.tab for
each user a want to capture, like:
[EMAIL PROTECTED]*0.0.0.0/00.0.0.0/0
regulatory_fwd.tab
My regulatory_fwd.tab (in the filers dir) looks like:
/mailfilters/copyin.sh@@FILE[EMAIL PROTECTED]
My copyin.sh file looks like:
#!/bin/sh
#
# Account to forward to
fwd_addr=$2
# XMail Root
xmail_root= /var/MailRoot
# Path of files
filter_path=/mailfilters/copyin
# Path that we'll copy temporary messages to
test_path=$filter_path/temp
# *
# *
testfile=`basename $1`
echo -ne mail from:$fwd_addr\r\n$test_path/$testfile.fwd
echo -ne rcpt to:$fwd_addr\r\n$test_path/$testfile.fwd
echo -ne \r\n$test_path/$testfile.fwd.evolve
sed -f $filter_path/removeheader.sed $1$test_path/$testfile.fwd
mv $test_path/$testfile.fwd.evolve $xmail_root/spool/local
My removeheader.sed looks like:
# removeheader.sed
# Strip out all of xmail's special headers.
1,/^MAIL-DATA/{
d
}
Thank you John,
With a few changes it's working perfectly. It's really what I was looking for.
-
To unsubscribe from this list: send the line unsubscribe xmail in
the body of a message to [EMAIL PROTECTED]
For general help: send the line help in the body of a message to
[EMAIL PROTECTED]
[xmail] Is there a way to turn off PLAIN TEXT authentication?
Hi I apologise if this isn't the correct forum, in which case please direct me. We have recently failed a one-sec security scan because XMail will authenticate using Plain Text. We need to disable this but I can't see anywhere obvious. I have looked at Mailusers.tab and SMPTAuth.tab but the documentation seems to suggest that I would have to place an entry here for every email address we use. regards David David Russell Web consultant and Technical Architect T101 Ltd tel: +44 (0)2077049888 mob: +44 (0)7973637175 - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
