I guess you could, by changing/setting
#$inet_socket_port = 10024;
to port 25 in the amavis.conf
and the forward target
#$forward_method = 'smtp:[127.0.0.1]:10025'; # where to forward checked mail
to whereever your target SMTP server runs
BUT BE WARNED
I WOULD NOT EXPECT AMAVIS TO BE AS ROB
I guess you could, by changing/setting
#$inet_socket_port = 10024;
to port 25 in the amavis.conf
and the forward target
#$forward_method = 'smtp:[127.0.0.1]:10025'; # where to forward checked mail
to whereever your target SMTP server runs
BUT BE WARNED
I WOULD NOT EXPECT AMAVIS TO BE AS ROB
I do use SquirrelMail, but still AFAIK it's only a web interface to email,
i.e. it displays on a Web UI what's in my mail folders (via IMAP). No idea
if/how you could get SquirrelMail to move your mail items to different
folders. Isn't that an LDA (e.g. procmail) job ?
Regards
Jochen
>
> Quoting
AFAIK sqwebmail is just a web interface to your mail folders.
But somehting like
:0:
* ^Delivered-To: .+\+\/(amavis|spam)
.$MATCH/
in your .procmailrc (if you use procmail as LDA) should do what you want.
The above moves my mails into an amavis folder (if the address is
[EMAIL PROTECTED]) and a
On Mo, 22.08.2005, 16:29, Noel Jones sagte:
> At 06:42 AM 8/22/2005, Jochen Seifarth wrote:
>>I am currently setting up a Postfix dual-SMTPD configuration with AMaViS
>>in between in the SMTPDs. In this configuration I would like to implement
>>restrictions in the second
Mark,
thanks for your reply
>
> What problem are you trying to solve? The main purpose of XCLIENT is to
present a client identity to Postfix in order to let its
> restrictions see the presented id instead of the natural one.
> Since in the normal situation the first MTA is supposed to
> check all
With Amavisd-new, Postfix and SpamAssassin on Debian, using a BEFORE-QUEUE
setup (i.e. dual SMTPD) I would like to achieve the following:
1. If (spam score <= tag2_level)
Then Deliver mail to the 2nd SMTPD (localhost:10025) immediately
2. If (tag2_level <= spam score <= kill_level)
Then Del
Are there any plans or patches to support the Postfix XCLIENT in AMaViS ?
In a dual SMTPD setup with AMaViS (2.3.2) I would like the first Postfix
SMTPD to forward client MTA details via the XCLIENT to the second SMTPD
through AMaViS. XFORWARD works fine... but it's not quite the same as
XCLIENT.
