Quoting Joseph Brennan <[EMAIL PROTECTED]>:
>
> Matus UHLAR - fantomas <[EMAIL PROTECTED]> wrote:
>
>> . . . Be sure to add some tracking informations if you want to be able
>> to find out e.g. who spammed through your webmail (we've had some nigerian
>> spammers hacking accounts and spamming las
Well we technically can't directly do it either. But since the ID
administrator is part of the same department as central mail services
all it takes is a phone call and the ID goes bye bye (actually it
gets suspended... not eliminated).
K
On 18-Dec-07, at 8:33 AM, Liam Hoekenga wrote:
Zitat von Kevin Konowalec <[EMAIL PROTECTED]>:
> This is exactly what we did. Since you can change your "from" and
> "reply-to" fields in your identities it became necessary to embed the
> user's actual login ID in an X-header so that we can identify the
> source of spam. We also took it one ste
>
> We just went the simple route - if we find a spammer, we disable the
> ID. We can look to see the account information and can tell with
> pretty much 100% accuracy if the user passes the smell test. 99% of
> the time the IP address comes from Nigeria (though we have seen a few
> others..
On 18-Dec-07, at 8:20 AM, Liam Hoekenga wrote:
>
>> We've had IMP abuse as well, for what purports to be a British Lotto,
>> and we've been on the receiving end of the same kind of spam from
>> other
>> IMP and Squirrelmail installations.
>>
> I'm glad to know we're not the only ones seeing thi
> Im curious as to how they are able to do this? What kind of
> authentication backend to you have configured? How are spammers able
> to use your install for spam if they dont have a user account to do so?
>
The transfer logs on our campus SSO and webmail servers, and the Horde
prefere
Quoting Liam Hoekenga <[EMAIL PROTECTED]>:
>
>> We've had IMP abuse as well, for what purports to be a British Lotto,
>> and we've been on the receiving end of the same kind of spam from other
>> IMP and Squirrelmail installations.
>>
> I'm glad to know we're not the only ones seeing this.
>
> W
This is exactly what we did. Since you can change your "from" and
"reply-to" fields in your identities it became necessary to embed the
user's actual login ID in an X-header so that we can identify the
source of spam. We also took it one step further and added a bit of
code that keeps a r
> We've had IMP abuse as well, for what purports to be a British Lotto,
> and we've been on the receiving end of the same kind of spam from other
> IMP and Squirrelmail installations.
>
I'm glad to know we're not the only ones seeing this.
We've had a dramatic increase of spam coming from comp
Quoting Bjørn Mork <[EMAIL PROTECTED]>:
> I fully agree with you that you encoding is the only way to ensure that
> a message can be delivered without any relay or gateway MTA altering the
> body, and that such altering really should be a no-no. But the fact is
> that RFC 2822 does allow you to s
Matus UHLAR - fantomas <[EMAIL PROTECTED]> wrote:
> . . . Be sure to add some tracking informations if you want to be able
> to find out e.g. who spammed through your webmail (we've had some nigerian
> spammers hacking accounts and spamming last month)
This is an important topic for IMP users.
Michael M Slusarz <[EMAIL PROTECTED]> writes:
> RFC 1652 deals with SMTP servers. This is irrelevant for IMP. You
> need to look at RFC 2822 which defines the format for a valid e-mail
> message and, more specifically, Section 2.1 which states:
>
> 2.1. General Description
>
> At the mos
> --On Friday, November 30, 2007 10:41 +0100 ValiDOM <[EMAIL PROTECTED]>
> wrote:
>
> > for privacy reasons, I'd like to not include the IP-Address of the
> > client in headers of mails sent via IMP.
⇧On 30.11.07 08:02, Joseph Brennan wrote:
> For security reasons, we don't like to *get* mail wi
13 matches
Mail list logo
