Re: [exim] exim3 amavis - preserve message id

Pàgina inicial
Delete this message
Reply to this message
Autor: M.A.
Data:  
A: exim-users
Assumpte: Re: [exim] exim3 amavis - preserve message id
Hi!



yes, i know its nonsense to use exim3, but now it is not allowed for me to
change for anything else.



Heiko, i couldnt do exim to listen on 25 and 10025 port too.

exim3.36 dont understand the : 127.0.0.1.25 : 127.0.0.1.10025

it doesnt matter, now amavis send back on 25



back to the goal:

you are right, thats what i want... the ID

and yes i can follow the message way but only at night, when comes 2 mail /
minute.

during the day, we have a lot of mail, so there are 20-30 lines between one
message delivery lines.



arggh, thanks lot



M





-- Eredeti üzenet --

Feladó: Heiko Schlittermann <hs@???>

Címzett: exim-users@???

Elküldve: 19:07

Téma: Re: [exim] exim3 amavis - preserve message id



M.A. melcsia@???> (Sa 28 Okt 2006 15:25:40 CEST):



> Hi!



> i have to use exim3. i cant change to exim4.



> now i installed amavis.



> works almost good, exim send every incoming mail to amavis over smtp c
onnec



> tion, which has no amavis header.







> localhost : 10024



> i've read exim3 can work only on port 25, so amavis send back the mess
age o



> ver an other smtp connection to exim3.







AFAIR exim3 could listen on some other port than 25 too.







> localhost : 25



> Thats ok, but in the log every message will be 2 message and 2 message
id.



>



> The goal is to use the same message, i wanna tell to exim, if the send
er ho



> st is amavis and there is a scanned header, than use the message id ak
a pre



> serve it.







This behaviour is even in exim4, from exims POV it's a totally new



message, so it gets a new ID assigned. (Your are talking about the IDs



exim uses for identifying the messages in spool, logs, ..., not about



the Message-ID-Header.)







The current exim(4) logs the Message-ID-Header, this can be used to



track a message in the logs, but I'm not sure if it's true for exim3



already:







pu:~# exigrep c69cd11a4ac7.4ac7c69cd11a@??? /var/log/exim4/mainl
og



2006-10-28 06:36:42 1Gdfvu-0006al-0O hs@??? R=amavis T=am
avis H=eth1.tigger.schlittermann.de [212.80.235.129]



2006-10-28 06:36:51 1Gdfvu-0006al-0O Completed







2006-10-28 06:36:51 1GdfwB-0006av-PH heiko hs@???> R=cyr
us T=cyrus_lmtp



2006-10-28 06:36:52 1GdfwB-0006av-PH Completed







But you see, the exims "internal" id changes as stated above.







You need to scan the message from inside exim to see it as one ID per



message. But with exim3 it's not possible, in exim4 it should, using the



acls.









Best regards from Dresden

Viele GrüĂ�e aus Dresden

Heiko Schlittermann



--

SCHLITTERMANN.de ---------------------------- internet & unix support -

Heiko Schlittermann HS12-RIPE -----------------------------------------

gnupg encrypted messages are welcome - key ID: 48D0359B ---------------

gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B -



--



## List details at http://www.exim.org/mailman/listinfo/exim-users



## Exim details at http://www.exim.org/



## Please use the Wiki with this list - http://www.exim.org/eximwiki/



_________________________________________

Hírkereső TOP50 hír - Bulvárhírek, sztárpletykák és a nap t
örténései itt: KLIKK IDE! - http://www.hirkereso.hu/top50