From: Rainer M Krug <r.m.krug@gmail.com>
To: wgreenhouse@riseup.net (W. Greenhouse)
Cc: info-gnus-english@gnu.org
Subject: Re: Can't send emails to this list via gmane?
Date: Fri, 29 Mar 2013 17:41:54 +0100 [thread overview]
Message-ID: <877gkqcg4t.fsf@gmail.com> (raw)
In-Reply-To: <878v56rz8p.fsf@riseup.net> (W. Greenhouse's message of "Fri, 29 Mar 2013 15:40:06 +0000")
wgreenhouse@riseup.net (W. Greenhouse) writes:
> Hi Rainer,
>
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> Nothing - the message with the following headers:
>>
>> From: Rainer M Krug <R.M.Krug@gmail.com>
>> Subject: Displaying all mail
>> Newsgroups: gmane.emacs.gnus.user
>> Date: Thu, 28 Mar 2013 20:57:31 +0100 (19 hours, 23 minutes, 20 seconds ago)
>> Fcc: /home/rkrug/Maildir/sent
>>
>> is copied into the nnfolder+archive.sent.2013-03 but does not go
>> through.
>>
>>> after sending an NNTP message for the first time to a particular Gmane
>>> newsgroup, you get a confirmation mail at the address you specified in
>>> "From:" which must be a valid email address. You must reply to that
>>
>> I did not receive any mail, and I can post to to the mailing from
>> thunderbird so I assume that I should be able from gnus as well.
>
> My hypothesis, then, is that Gmane does try to send you the confirmation
> message but that this ends up in your Gmail spam folder. Did you check
> there?
Yes - I checked there just now and nothing was in there. In addition, I
assume that the email would have been send via my (only) smtp account
which is gmail, and the mail should have been in the "Send Items" -
nothing there (checked via the web interface as well).
>
>> Same as above - I do not assume that I am blocked when using gnus but
>> not thunderbird.
>
> To clarify, are you posting directly to the mailing list with
> Thunderbird, or to Gmane?
via gmane on thunderbird.
> Being blocked from Gmane and blocked from the
> "upstream" mailing list are not the same thing; that's completely
> different machines, with different administrators, and potentially
> different lists of IPs suspected of spam.
Sure - two different receivers.
>
> Your description of the order of events, though, makes it sound like the
> message was delivered to Gmane but the required confirmation email was
> mislaid somehow.
I thought the same - but I did not see any.
Any suggestions how I can check this?
Rainer
>
> Best,
> Will
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
next prev parent reply other threads:[~2013-03-29 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 20:12 Rainer M Krug
2013-03-29 15:11 ` W. Greenhouse
2013-03-29 15:26 ` Rainer M Krug
2013-03-29 15:40 ` W. Greenhouse
2013-03-29 16:41 ` Rainer M Krug [this message]
2013-03-29 17:00 ` W. Greenhouse
2013-04-02 8:06 ` Rainer M. Krug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gkqcg4t.fsf@gmail.com \
--to=r.m.krug@gmail.com \
--cc=info-gnus-english@gnu.org \
--cc=wgreenhouse@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).