Displaying 20 results from an estimated 3000 matches similar to: "Mailing list address harvested for spamming"
2018 Dec 02
2
Mailing list address harvested for spamming
On Sun, Dec 02, 2018 at 03:58:53AM +0100, Bernd Petrovitsch wrote:
> On 02/12/2018 03:05, Michael A. Peters wrote:
> [...]
> > But - I would wager that over 95% of the time when someone hits the
> > reply button on a list post, their intent is to reply to the list.
>
> Even if it's 99%: What is the lesser risk if someone get's it wrong?
>
> Apart from the
2018 Dec 02
3
Mailing list address harvested for spamming
On 12/01/2018 05:49 PM, Ralph Seichter wrote:
> * Michael A. Peters:
>
>> Netiquette posts are just someone's opinion, and they often don't take
>> into account the vastly different way different types of minds work.
>
> Mailing list netiquette has been around for decades, for good reasons.
> If Joe User's mind "works differently", Joe needs to
2018 Dec 02
0
Mailing list address harvested for spamming
On Sun, Dec 02, 2018 at 04:22:52PM +0100, Ralph Seichter wrote:
> * Ruben Safir:
>
> > On Sun, Dec 02, 2018 at 03:58:53AM +0100, Bernd Petrovitsch wrote:
> >
> >> Let's hope that people who do not know how to use a tool - e.g.
> >> like a hammer - doesn't use that tool in the first place ....
> >
> > that is pretty unrealistic and I
2018 Dec 02
6
Mailing list address harvested for spamming
On 02/12/2018 05:31, M. Balridge wrote:
> Quoting dovecot-e51 at deemzed.uk:
>
>> Not to stir the pot, but I notice my email address has recently been
>> harvested from this list for spamming purposes. This email address is
>> unique and not used for anything else.
>>
>> I'd distinguish this from spam sent to the mailing list itself, which is
>>
2018 Dec 02
2
Mailing list address harvested for spamming
On 02/12/2018 11:00, Hendrik Boom wrote:
> There's an extensive email etiquette post somewhere on the net
> explaining why setting 'reply-to' to the list is a bad idea.
Lots of posts around about this, all self serving :)
There may of course be an RFC floating around, but I admit to never
having bothered to look, because good netizens reply to list, lists are
public, they
2018 Dec 02
2
Mailing list address harvested for spamming
On 12/01/2018 05:00 PM, Hendrik Boom wrote:
>
> There's an extensive email etiquette post somewhere on the net
> explaining why setting 'reply-to' to the list is a bad idea.
>
> Reply-to is intended for the sender to explain that replies shouldn't
> be sent to the obvious sending address, but to another address.
> This is essential if, say, the sender is
2018 Dec 02
0
Mailing list address harvested for spamming
On 02/12/2018 03:05, Michael A. Peters wrote:
[...]
> But - I would wager that over 95% of the time when someone hits the
> reply button on a list post, their intent is to reply to the list.
Even if it's 99%: What is the lesser risk if someone get's it wrong?
Apart from the situation that people send mails over the mailing list
with "for X.Y." in the subject and no one
2017 Aug 11
1
is a self signed certificate always invalid the first time?
On 08/10/2017 04:41 PM, Frank-Ulrich Sommer wrote:
> I can't see any security advantages of a self signed cert. I
then you fail to understand the history, like when Microsoft's certs
were undermined because the third party authentication agency gave the
keys to 2 guys that knocked on the door and asked for them...
--
So many immigrant groups have swept through our town
that
2017 Dec 11
2
hosting emails at home
thatis not secure and you might as well use gmail
It is not so hard to just get a static IP and put a mail server up.
fit/pc has perfect boxes for this, run on about 15w/h power
On Sun, Dec 10, 2017 at 02:42:36PM -0800, Kenneth Porter wrote:
> On 12/10/2017 12:39 PM, Stephan H wrote:
> >I have dovecot postfix setup on my home server as well. I use a virtual
> >server in the
2017 Jul 30
2
dovecot auth errors for a new user
I've been running dovecott without trouble for quite a why and now when
I added a new user, it is not accepting the user and I can not track the
problem. It says find more information in the server log, but it is not
in /var/log/messages or /var/log/mail.err and nothing with lsof
dovecot|grep log show anything to tail
www:~ # dovecot -n
# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux
2018 Dec 01
0
Mailing list address harvested for spamming
Quoting dovecot-e51 at deemzed.uk:
> Not to stir the pot, but I notice my email address has recently been
> harvested from this list for spamming purposes. This email address is
> unique and not used for anything else.
>
> I'd distinguish this from spam sent to the mailing list itself, which is
> obviously different.
>
> Is there anything further that could be done
2017 Jul 30
2
dovecot auth errors for a new user
Am 30.07.2017 um 21:49 schrieb Ruben Safir:
> 2017-07-30T15:47:23.113000-04:00 www dovecot: pop3(facebook): Error:
> user facebook: Initialization failed: Namespace '': Mail storage
> autodetection failed with home=/home/facebook
> 2017-07-30T15:47:23.116805-04:00 www dovecot: pop3(facebook): Error:
> Invalid user settings. Refer to server log for more information.
Define
2018 Dec 02
0
Mailing list address harvested for spamming
On 12/01/2018 04:09 PM, Noel Butler wrote:
>
> Which is why it annoys me that some people on mailing lists feel the
> need to reply directly, rather than through mailing list.
Sometimes it is the MUA that is poorly designed that causes this.
Also, some lists set the "reply to" with the sender rather than the list.
Further, some user agents have a separate "reply"
2018 Dec 02
1
Mailing list address harvested for spamming
On 02/12/2018 10:16, Michael A. Peters wrote:
> On 12/01/2018 04:09 PM, Noel Butler wrote:
>
>> Which is why it annoys me that some people on mailing lists feel the need to reply directly, rather than through mailing list.
>
> Sometimes it is the MUA that is poorly designed that causes this.
I could have sworn I said that, oh yes, I see I did
> Also, some lists set the
2018 Dec 02
0
Mailing list address harvested for spamming
* Michael A. Peters:
> Netiquette posts are just someone's opinion, and they often don't take
> into account the vastly different way different types of minds work.
Mailing list netiquette has been around for decades, for good reasons.
If Joe User's mind "works differently", Joe needs to make the effort to
adapt to existing conventions instead of expecting conventions
2018 Dec 02
0
Mailing list address harvested for spamming
On Sun, Dec 02, 2018 at 10:09:02AM +1000, Noel Butler wrote:
> On 02/12/2018 05:31, M. Balridge wrote:
>
> > Quoting dovecot-e51 at deemzed.uk:
> >
> >> Not to stir the pot, but I notice my email address has recently been
> >> harvested from this list for spamming purposes. This email address is
> >> unique and not used for anything else.
>
2018 Dec 01
3
Mailing list address harvested for spamming
Not to stir the pot, but I notice my email address has recently been
harvested from this list for spamming purposes. This email address is
unique and not used for anything else.
I'd distinguish this from spam sent to the mailing list itself, which is
obviously different.
Is there anything further that could be done to prevent this?
--
Dave
2017 Sep 07
1
password reset
On Sep 7, 2017, at 2:33 PM, Ruben Safir <ruben at mrbrklyn.com> wrote:
> On 09/07/2017 02:24 PM, @lbutlr wrote:
>> sudo passed <user>
>
> su -
> password username
No difference.
No difference when logging in to the console as root.
--
Apple broke AppleScripting signatures in Mail.app, so no random signatures.
2018 Sep 04
1
Best way to move mail from one server to another
On 9/4/18 12:27 PM, Sami Ketola wrote:
>
>
>> On 4 Sep 2018, at 18.38, Robert Schetterer <rs at sys4.de> wrote:
>>
>> Sorry i migrated terrabytes of mail with imapsync and never had a
>> problem, it works as designed, also with maildir rsync did a good job,
>> what never worked as it should was dsync ,cause of bugs ,that may
>> changed now
>>
2018 Nov 29
1
Best way of merging mbox files
aside from cat?
On Thu, Nov 29, 2018 at 03:07:58PM -0800, Joseph Tam wrote:
> On Thu, 29 Nov 2018, Marc Roos wrote:
>
> >When concatenating mbox files like described here
> >https://xaizek.github.io/2013-03-30/merge-mbox-mailboxes/. You will end
> >up with an 'unsorted' mbox file. Is this going to be a problem
> >esspecially when they are large >2GB's